Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

934

I'm too much of a smooth brain to figure what I'm doing wrong here. I have the following in my bashrc:

alias ls="command ls --color=always --classify -v -C --group-directories-first --show-control-chars --sort=extension"

cd () { command cd "$@" && ls ; }

Now, when I "cd ~/some/dir", my customized view is properly displayed. If I manually 'ls' in that dir or any other dir, my customized view is lost. Any ideas what could cause that?

While I have your ear, somewhat off topic, why is it that when I write the 'ls' alias as a function, bash shits itself? When I write it like so:

ls () { command ls --color=always --classify -v -C --group-directories-first --show-control-chars --sort=extension ; }

bash complains:

bash: /home/FreedomLover/.bashrc: line 106: syntax error near unexpected token('`

bash: /home/FreedomLover/.bashrc: line 106: 'ls () { command ls --color=always --classify -v -C --group-directories-first --show-control-chars --sort=extension' ; }

Prost.

Ed: I forgot to mention that 'alias ls' says:

ls='ls --color=auto'

I'm too much of a smooth brain to figure what I'm doing wrong here. I have the following in my bashrc: `alias ls="command ls --color=always --classify -v -C --group-directories-first --show-control-chars --sort=extension"` `cd () { command cd "$@" && ls ; }` Now, when I "cd ~/some/dir", my customized view is properly displayed. If I manually 'ls' in that dir or any other dir, my customized view is lost. Any ideas what could cause that? While I have your ear, somewhat off topic, why is it that when I write the 'ls' alias as a function, bash shits itself? When I write it like so: `ls () { command ls --color=always --classify -v -C --group-directories-first --show-control-chars --sort=extension ; }` bash complains: `bash: /home/FreedomLover/.bashrc: line 106: syntax error near unexpected token `('` `bash: /home/FreedomLover/.bashrc: line 106: 'ls () { command ls --color=always --classify -v -C --group-directories-first --show-control-chars --sort=extension' ; }` Prost. Ed: I forgot to mention that 'alias ls' says: `ls='ls --color=auto'`

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (14).
[–] [deleted] • 1 pt

In Unix, everything is a script. That's the beauty of Unix philosophy.

.bashrc is run as

$ ./.bashrc

NOT

$ source .bashrc

NOT

$ . .bashrc

Etc...

The difference is not trivial as script kiddies may assume. For more information RTFM

$ man command

[–] • 0 pt

Oh yeah, for got to mention 'man' too:

No manual entry for command

[–] [deleted] • 1 pt

When you fully grok this, you will be enlightened.

[–] • 0 pt (edited )

So if I understand the man page correctly, what I read before was true. 'command' prevents recursions, at least with functions.

Also, if I understand your first comment correctly, since I am the sole user of my box, would a check for an interactive shell before applying a modded cd/ls command be ok? Something in the spirit of:

[ "-t0" ] && blah () { command ... ; }?

If the check succeeds, that shouldn't be applied scripts, right?