Search
1000 results for “DrHyde”
-
Re prev toots, hypothetically, if I were to write a library called libextextglob that would grovel over an array of strings (like, say, #argv) and do horrible things to it if it sees globby characters that the shell didn't expand, would you think it was ...
(updated to allow multiple choices, because the best crimes are in B♭ minor)
-
So my earlier #VagueToot about #bash #globbing ... I want to be able to specify something like "all the directories which don't contain a file called wibble.yml". #extglob can find files that don't match a `!(pattern)`, but I want to match the absence of such files in a directory. eg, if foo/bar, baz/bar and barf/ exist I want to be able to `ls -ld [magic goes here]` to get info about directory barf/ only.
Yes, I know other ways of doing this. I want to do it using globbing.
Because I do.
-
I wish #bash supported programmable globbing like what it does with #TabCompletion.
-
I wish #bash supported programmable globbing like what it does with #TabCompletion.
-
I wish #bash supported programmable globbing like what it does with #TabCompletion.
-
I wish #bash supported programmable globbing like what it does with #TabCompletion.
-
I wish #bash supported programmable globbing like what it does with #TabCompletion.
-
Go home #Github, you're drunk
#WorldAltTextChampionshipEntry #ElectricFish #Egyptian #Hieroglyphs
-
This is a proper banger: https://www.bbc.co.uk/sounds/play/m002tbpz
-
I'm just going to assume that the geezer who won the #LondonMarathon was off his tits on #speed.
-
CW: spoiler
I think that `CAL XCHGI` should assemble to `206 015 002`.
OK, I can't read #octal as easily as #hexadecimal, so I didn't check that the 206 is correct. But that address in the 2nd/3rd bytes looks proper dodgy.
-
CW: spoiler
I think that `CAL XCHGI` should assemble to `206 015 002`.
OK, I can't read #octal as easily as #hexadecimal, so I didn't check that the 206 is correct. But that address in the 2nd/3rd bytes looks proper dodgy.
-
CW: spoiler
I think that `CAL XCHGI` should assemble to `206 015 002`.
OK, I can't read #octal as easily as #hexadecimal, so I didn't check that the 206 is correct. But that address in the 2nd/3rd bytes looks proper dodgy.
-
CW: spoiler
I think that `CAL XCHGI` should assemble to `206 015 002`.
OK, I can't read #octal as easily as #hexadecimal, so I didn't check that the 206 is correct. But that address in the 2nd/3rd bytes looks proper dodgy.
-
CW: spoiler
I think that `CAL XCHGI` should assemble to `206 015 002`.
OK, I can't read #octal as easily as #hexadecimal, so I didn't check that the 206 is correct. But that address in the 2nd/3rd bytes looks proper dodgy.
-
Fairly sure I just spotted a bug in some #Intel8008 code. Yes, 8008, not 8080 or 8086.
It's at https://en.wikipedia.org/w/index.php?title=Intel_8008&oldid=1346138297#Code_example_2
-
Do any of my #FreeBSD homies know how well supported this machine is? In particular, can it drive two HDMI monitors, the wireless network, and get OMG TEH SPEEEEED out of disks on the USB-C ports? Don't care about GPU performance, just about xterms and maybe the occasional web page with pictures and a video in it.
Intention is to run a bunch of VMs with other OSes for testing purposes, using #VirtualBox, and a fileserver.
https://www.tuxedocomputers.com/en/TUXEDO-Nano-Pro-Gen14-AMD.tuxedo
-
-
@futurebird for #dictionary and #BlackAdder fans ... #Johnson's dictionary *does* include "#sausage", but at least in my copy it is not sorted as we would, so I suspect that the writers really did check.
-
@futurebird for #dictionary and #BlackAdder fans ... #Johnson's dictionary *does* include "#sausage", but at least in my copy it is not sorted as we would, so I suspect that the writers really did check.