Sitaram Chamarty wrote:
> Hello,
>
> When the previous command was backgrounded (say "gvim
> filename.c &") and then you try some other command using
> Alt-., it expands to "&" and not "filename.c".
>
> Is this considered a bug? Or correct behaviour that just
> happens to be not useful in this s
Timothy James Erlenmeyer wrote:
> Bash Version: 4.0
> Patch Level: 28
> Release Status: release
>
> Description:
>
> With
> a color prompt, long directory names, and/or long command lines, scrolling
> through the command history often causes the cursor to be in the wrong
> position, the prompt t
Nils wrote:
> I use a shared .profile for bash and ksh93, I have a ksh93 specific
> section which I want to separate through the following construct:
>
> if ( test -n "${.sh.version}" ) 2>/dev/null; then
> echo "ksh"
> fi
>
> bash just hangs while it works in POSIX shell and ksh93. A bash scr
Nils wrote:
> PS1='$( [ "${LOGNAME}" != root ] && color=green )'
>
> works in ksh93 and POSIX shell but fails in bash as bash seems to
> expand the "!" to the next history file number before doing command
> substitution. Setting PS1='$( [ "${LOGNAME}" !!= root ] &&
> color=green )' preserves the "
