HEY LINUX MORONS

[rone]

MAKING ls AND vim (AND GOD KNOWS WHAT ELSE) SHOW EVERYTHING IN PRETTY COLORS BY DEFAULT IS USELESS IF THE COLORS RENDER TEXT ILLEGIBLE DEPENDING ON ONE'S TERMINAL BACKGROUND AND FOREGROUND COLORS.  YOU ARE STUPID AND UGLY NERDS.

Comments

[http://users.livejournal.com/_nicolai_/]

Yeah, is there some way to remove this fucking stupidity from a linux box, wholesale?

[http://users.livejournal.com/_nicolai_/]

Oh, by the way, the ls behaviour is some system-wide aliasing in the shell, so you can get rid of it. Getting VI to do it would be nice too though.

[ronebofh.livejournal.com]

Yes, i've taken care of the aliases, and i've been informed that echo 'syntax off' >> ~/.vimrc will take care of "vi". Which, really, vim... ugh. At least it isn't elvis, that's all i can say in its favor.

[http://users.livejournal.com/_nicolai_/]

Having to hax0r the config for each app on each machine (perhaps for each user) is a right pain in the neck for a sysadmin of many machines.

[ronebofh.livejournal.com]

I guess that's why you set things up properly in the kickstart image, or something. For extant machines, though, yeah, big pain in the neck.

[waider.livejournal.com]

in my minimal experience of this, you can "fix" vi by either unaliasing it or removing vim-enhanced from your system (which option you choose depends on other users of the system and your regard for same). This may not actually work for you at all, depending on your choice of OS/Distro.

For ls, you probably have to dink with files in /etc/profile.d.

[pentomino.livejournal.com]

I think that's how they make you join the linux course at community colleges.

Why the deep dark blue for directory names?

[http://users.livejournal.com/_nicolai_/]

Because they are morons.

[qwrrty.livejournal.com]

"hey Red Hat morons," if you please. IIRC you don't get this particular brand of dain bramage from all the distros (I'm using Debian and have not had the terminal emulation problems that seem to be intrinsic with Red Hat).

[rbarclay.livejournal.com]

Sadly enough, even in Debian ls is colored by default. The Evil lurks in the default .bashrc:

    if [ "$TERM" != "dumb" ]; then
        eval `dircolors -b`
        alias ls='ls --color=auto'

so maybe it's a default bash thing.

[ronebofh.livejournal.com]

   if [ "$TERM" != "dumb" ]; then
       force dumb
   fi

[ltempt.livejournal.com]

It ain't a bash thing. I use bash a fair bit and it ain't a bash thing. I wonder how the pretty colours look on a VT220?

[rbarclay.livejournal.com]

You're right, the default .bashrc on Debian comes from /etc/skel, not from bash itself.

[arian1.livejournal.com]

So change your terminal settings. Get with the program man.


:)

[ronebofh.livejournal.com]

Yes, the terminal settings. That must be it. And if that doesn't work, what will you suggest next? That i reboot my server? HUH, PUNK?

[arian1.livejournal.com]

If that fails you should powe...oh wait, you get the plan. That or like..install Windows or something. You know, an easier OS.


*duck*

[(Anonymous)]

No, then you have to zap your P-RAM.

[ronebofh.livejournal.com]

YOUR MOTHER SHOULD ZAP YOUR PRAM, YOU BIG BABY.

[nothings.livejournal.com]

Obviously you need to either recompile the kernel or switch distros. </jwz-bannable-offense>

[haineux.livejournal.com]

I always thought this was a privacy trick, since it effectively means I can't read your damn screen from more than 2 inches away.

It's good to know that they can't either.

[rbarclay.livejournal.com]

Much easier to just use Eterm (warning: may cause eye-cancer in certain nosy cow-orkers).

[ronebofh.livejournal.com]

It'd be nice if their download site didn't massively suck.

[plorkwort.livejournal.com]

The real problem is that this makes the floating eyes deep blue and almost impossible to see until you run into them and get frozen and killed by a grid bug or newt or your own stupid little dog that's gone crazed from hunger.

[sandollar17.livejournal.com]

Psh, fucking idiots. I can't believe them.

[alfvaen]

For vim, I just added "set background=dark" to my default .vimrc, which I've started to install early on any new computers. (This is with Cygwin, but the principle is the same.) With ls, there's some function called "dircolors" or something which I'm given to understand there's some way to set up.

But yeah, defaults are biased against dark backgrounds. What they need is some clever way to determine what the background colour is and play off that.

[(Anonymous)]

wrote various replies.

Deleted them, cuz, well, we all know linux idiocy clan, september, blah blah, and lets face it, WE know how to find the problem and solve it.

But yes, color overkill is teh suck, and hell, half these linuxslashdorks don't even know there IS a console, as they've never seen anything beyond X...or actually, kde or gnome... so.

And don't get me started (I already did 5 times) on the lack of knowledge of other shells than BASH. What with bash scripts being distributed as install bits, as if they were k0rn or sh compatible... and then, when you submit a patch, being told that it's not needed because it works on their /bin/sh ... so obviously YOUR /bin/sh needs to be compiled again...

[cheesetruck.livejournal.com]

GOD DAMMIT LJ I DID NOT WANT TO LOG OUT

[ltempt.livejournal.com]

Suitable punishment for using Linux. Live and learn!

Don't blame Linus

[venividi.livejournal.com]

Yeah, yeah, I know, I know, I'm geeking out here, but it's NOT Linux that's at fault and it doesn't matter what distro you use.

It's that damn GNU stuff from FSF.

So if you've got a problem, take it, and a bunch of broccoli, and go talk to RMS.

Re: Don't blame Linus

[dpk.livejournal.com]

If you want to get technical, it's not even GNU, FSF, or RMS's fault: it's our nation's schools. Garbage in, garbage out. And scotch. Scotch in.

[dpk.livejournal.com]

I sure wish it was limited to Linux morons.

Another default that needs to be tossed in the fire of whatever European embassy is burning currently is vim's "go to the last place you edited" feature. Die die die.