Workaround for broken pipe key on 98/ME

["Phil Betts" <Phil dot Betts at heis dot co dot uk>]

Hi Folks,

I just installed cygwin on W98 and hit the problem with the pipe key on
W98/ME: http://cygwin.com/faq/faq_5.html#SEC129

After googling to see what had already been tried, it became clear that
the problem was with readline.  This workaround uses readline to
fix itself.

Just add the following line to your ~/.inputrc

"¦":"|"

In case that got mangled in transmission, or you can't display 8-bit
characters, you should be able to do this:
  $ tail -1 ~/.inputrc | xxd
  0000000: 22a6 223a 227c 220a                      ".":"|".

(although if you got it wrong, you won't be able to pipe into xxd ;-)

This gets readline to map the broken pipe into the solid pipe.

Because of the difficulty in entering this on a system where you can't
enter pipes, might I suggest that the following (slightly more
pedantic) lines are added to the default inputrc file?

# If you are running Windows 98 or Windows ME and cannot enter pipe
# characters in the command shell, remove the hashes from the
# following three lines.
#$if term=cygwin
#"¦":"|"
#$endif

The FAQ could then be amended to direct people in the direction of
~/.inputrc.

Alternatively, (does anyone actually need broken pipes?), the default
behaviour could be to perform the mapping and to instruct users who
want the broken pipe to comment out the mapping.

HTH

Phil


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/