huf [he/him]

\o/

vim will load some other rc file if it cant find your ~/.vimrc. check what it has loaded with :scriptnames

also, try starting vim in a brand new terminal with vim -u NONE and check if it’s still happening.

linux must go
who must go?
…

in that case, i’d prefer a ~/bin/zcat with the contents

#!/bin/sh
exec gzip -cdf "$@"

this way, it’s exec’able, unlike an alias or shell function.

zgrep . * should do the trick

oh, there’s also zcat -f *

i’m afraid it’s M$ or MiKKKroSSoft. your choice.

i’d probably do

function cap() {
        prename 's/(^[a-z]?)/\U$1/' "$@"
}

it means it has to be invoked as cap *, but it also means that you can do cap foo* or whatever

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:

• write a function instead, as has been suggested
• use $'' quoting, which lets you put ’ (single quote) inside ’ (single quote) without going mad: alias cica=$'foo \'$bar\' baz'
• go insane and do this: alias cica='foo '\''$bar'\'' baz' (this is the old way, without bash’s $'')

none. you dont need a DE, you can just run a tiling wm and some terminals…

are you using ntfs-3g or the older shittier ntfs driver?

makes sense, since we’re on youtube for the ads

what do you mean the output doesnt keep the LF? what LF?

ps also has -u and -U switches to filter by users

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