[svlug] Re: Heads Up: bash 2.0 gives me headaches.

[Stig HackVän]

David Fetter wrote:
> 
> > 2.  [fsck'ed-up pipe]
> >     Does anyone know why this is happenning and how to work around it
> >     without using a temporary file?
> 
> I think you might have to escape the '|'.
> 

no, that's not it.

> Better still, downgrade to 1.14.7 :)

I think I upgraded because I wanted to see if readline was more intelligent
about editing long commands.  It's not (much) better.  I have a prompt that
wraps around the line and so readline tends to hose up my screen when I edit
long commands.

> The only "feature" I've found so far is the ability to go back to a
> multi-line command line statement like:
> 
> perl -e '
> do
> some
> commands
> then
> be
> done'
> 
> as a block, rather than one line of it at a time.  Come to think of
> it, this "feature" may be the root cause of the first randomness.

No, you could do that before.  It just wasn't the default.  You had to set a
variable. 

  case $BASH_VERSION in
    1* )
      notify=                       # immediate notification when jobs finish
      no_exit_on_failed_exec=       # don't quit shell if exec file is bad
      command_oriented_history=     # keep multi-line commands in one hist entry
      ;;
    2* )
      set -b                    # 'set -o notify' is supposed to work
      # shopt execfail       # interactive shell doesn't exit anyway
      # shopt cmdhist        # default
      ;;
  esac

-- 
Stig      ...   http://hackvan.com
HackVän   ...   Friend of Hacking


--
echo "unsubscribe svlug" | mail majordomo at svlug.org
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ to unsubscribe