Bash – Wondering about a nice combo of ls & cat

bashcatcommand linelsshell-script

As ll, I use ls -alh /some/file frequently, and just as often then, follow immediately with cat /some/file. I have to believe this has been addressed with various aliases. And on the next level, with shell functions. I have written a couple hundred aliases, but no shell function. Maybe that's what the doctor orders. Is this an old hat? Is there a shelf remedy? Thank you.

Best Answer

lcat() {
    ls -alh "$@"
    cat "$@"
}

or with less instead of cat. Or ( ls -alh "$@"; cat "$@") | less to see the permissions and all in the same browseable listing.

The I would need is something like this:

lcd() {
    if [ -d "$1" ]; do
        ls -lvF "$1"
    else
        less "$1"
    fi
}

i.e. either take a listing of a directory or view file. There's probably some less frontend that already runs ls on directories, but anyway.

Related Solutions

Bash – How to reliably and simply get the current shell interpreter name

I've had great results with this combination:

ps -p $$ | awk '$1 != "PID" {print $(NF)}'

On Tru64 (OSF/1), the output has parentheses around the shell. Tack on tr -d '()' to remove them.

ps -p $$ | awk '$1 != "PID" {print $(NF)}' | tr -d '()'

Appears to works on all shells, on Solaris 10 and RHEL 5.7 / 6.4. Didn't test other distros such as Debian, Ubuntu, or Mint, but I would think they should all work the same; I also have no idea if FreeBSD would work.

Bash – How to find why a bash exits with signal 11, Segmentation fault

I installed the debuginfo tools as suggested by gdb and then I got the expression responsible for the crash:

#20 0x0000000000457ac8 in expand_compound_array_assignment (
    var=<value optimized out>, 
    value=0x150c660 "$(logPath \"$@\")", flags=<value optimized out>
)

So now I know what and where is the issue. In my case it was in a function sourced in the .bashrc and the root cause was this wrong redefinition of the map variables in Bash:

declare -A myMap
local myMap=""

...
for key in "${!myMap[@]}"; do 
  echo ${myMap[$key]}
done

This function was called inside a sub-shell which caused the 'segmentation fault' error output to be hidden.

Best Answer

Related Solutions

Bash – How to *reliably* and *simply* get the current shell interpreter name

Bash – How to find why a bash exits with signal 11, Segmentation fault

Related Question

Bash – How to reliably and simply get the current shell interpreter name