everything randomly distributed between ~/dl
and ~/tmp
(i dont even remember why i have both), and then i use lr
to find stuff (alias lr='ls -lrth'
). or find
.
everything randomly distributed between ~/dl
and ~/tmp
(i dont even remember why i have both), and then i use lr
to find stuff (alias lr='ls -lrth'
). or find
.
i’m afraid it’s M$ or MiKKKroSSoft. your choice.
they liked 90s russia, when it was weak, full of child prostitutes and people were dying en-masse from substance abuse (and the barn doors were wide open so they could loot it)
when you create the alias, the shell substitutes the $1
(to nothing, probably) since your alias is in ""
(double quotes).
now, if you swap the single and double quotes, then the substitution still happens, but at invocation time instead of at definition time.
you actually want perl to deal with this $1
, so neither is good.
you have three options:
''
quoting, which lets you put ’ (single quote) inside ’ (single quote) without going mad: alias cica=$'foo \'$bar\' baz'
alias cica='foo '\''$bar'\'' baz'
(this is the old way, without bash’s ''
)it’s the fastest way to get crews for your navy
nowhere near as good as their chinese duet
dont watch the sequel (i havent either).
but yeah, it’s a james bond type story set in a super weird garbled mirror image of the cold war. with mice and cats. and bats. and rats.
man i’m gonna re-watch it tonight. got myself hyped up :D
cat city
oh no, i’m not falling for this. you’re not a cat. i’ve met cats, i’ve talked to them, i’ve seen cats use the computer. you’re not a cat.
DOS -> win95 -> win98 -> debian (and i’m still here 24 years later…)
yeah, same. i dont seem to have any problem with my ears per se, it seems more like a processing/noise filtering thing in my brain that’s not working at full power. i think my dad had it too.
i cant understand distorted speech, while most people around me obviously can. i have never been able to understand anyone speaking into a loudspeaker.
it’s gonna keep looping through the foodchain until some microbe finally figures out an easy way to break them down… fun stuff.
it’s been slowly getting worse since the 2010s. i remember talking about it back then.
i dont think they’ve lost touch, they’ve never been in touch. this behavior is apparently what produces the biggest profits for the next quarter, so they’ll do it until they drive the platform into the ground, then just start another one and repeat
“chose”. learning the language of the worst colonizer of your time’s always been economically advantageous
because capitalists have to lie about reality to preserve their ill gotten gains.
it took less than a day for someone to break run0 totally open, so basically, you have a choice between a well tested/debugged sudo and this new thing which may eventually mature
i have bad news: bash is already a massively improved/extended ksh clone. ksh was a massively improved/extended sh clone. sh got a ton of improvements early on.
this is about as good as you can get without breaking compatibility completely (bash already breaks compatibility with posix sh in some ways).
anyway, once you’ve figured out the hermetic incantations required to work with filenames with whitespace in them, it’ll be time to write scripts that can handle filenames with newlines in them :D
does anything flush the buffers after the print, but before the break? otherwise, if the stream you’re printing to is buffered, you’re not necessarily gonna see any output