« first day (4056 days earlier)      last day (1196 days later) » 

08:24
@JeffSchaller I did! I even packed up my computer and took it back where it came from ;-)
 
6 hours later…
14:33
@terdon same for <localecode> tag which is closed with <locale> 😁
or as pointed a missing space is also applicable for this tag too
@JeffSchaller how did you eat without parsing it properly first. :D
@αғsнιη yeah I think it’s more likely a missing space, otherwise the = wouldn’t make sense either
@αғsнιη teeth, saliva and stomach acid are very forgiving parsers ;-)
mental note: don't bring a cake designer to /dev/chat ;)
@αғsнιη indeed, the fork had no problem parsing the cake (in theory) :)
14:50
@αғsнιη No, silly. First you eat it, then you pass it!
would I eat a cake that had ls | grep foo on it? Hmm
cat cake > /dev/full ?
what is /dev/full anyway?
@JeffSchaller you ate a very problematic cake
@terdon a device that fails writes with ENOSPC, IIRC
the real issue with cake is when you do cat /dev/zero > /dev/null
or if your tty line discipline isn’t cooked
😂 😂 😂
15:00
@StephenKitt Oh. So just for testing/debugging?
$ echo aa > /dev/full
bash: echo: write error: No space left on device
huh
@terdon pretty much, yes
man full:
> This can be used to test how a program handles disk-full errors.
Reading from it is the same as reading from /dev/zero.
Huh. I see. Neat, never knew this existed.
I only found it because I was looking through ls /dev/ for a bad joke.
there’s no /dev/joke yet, there’s opportunity for a startup there!
dev-joke.io, here come the $$$
15:27
Oh, yes. Here's a business pitch that is bound to work: "Step 1: create a new Linux kernel device file called 'joke'. Step 2: profit!"
15:49
If I am untaring an archive to a destination that already exists, files with the same name are overwritten, but files present at the destination but not from incoming tar are left unchanged, is that right?
16:00
@hello that’s right, in particular they won’t be deleted just because they’re not in the archive
@StephenKitt Thanks. Thought I should ask before I do something stupid. :)
@αғsнιη tell me about it! :D
 
4 hours later…
19:55
I think the full path of a file normally includes the filename. Is there a term for the path excluding the filename? I.e. the full path of the directory containing the file?
LEEEEEEEEEEEEROOOOOOOOOOOY JENKINS
@jesse_b That's not it.
dirname?
@jesse_b Um. Perhaps. But isn't that just short for file directory name?
I thought that was what you were looking for although the dirname command doesn't necessarily provide the full path but usually only a relative path so not what you are looking for
20:42
@jesse_b you can always feed the result through realpath to get the canonical absolute path
Yeah I think Faheem is looking for the term to describe a "full dirpath" and I'm not sure there is one
although saying "full dirpath" would probably be enough for most people to understand what you mean
s/dirpath/dirname
"absolute dirname" is probably what I'd use, although "absolute path to the file's containing directory", while much more of a mouthful, is also clearer
Knowing the context might help.
 
1 hour later…
22:08
@FaheemMitha A pathname can be said to consist of a filename at the end of a directory path, where the directory path is itself a pathname (or empty).
The "filename component" of a pathname is the last slash-delimited bit of the pathname.
The name for the pathname of the parent directory of a file is "the pathname of the parent directory of the file".

« first day (4056 days earlier)      last day (1196 days later) »