bash 'history' command hangs if piped through more

Article View: gnu.bash.bug

Article #31

#31

From: Charles H. Romine
Date: Tue, 20 Jun 1989 19:43

8 lines
758 bytes

I just noticed that piping the output of `history' through `more' (or through
`less') and then breaking the pipe by quitting from `more' (i.e., typing `q'),
causes the history command to hang, requiring an interrupt to regain access to
the shell.  Thought you'd want to know.

					Ch. Romine

					romine@msr.epm.ornl.gov

Technical Details

Message-ID: <8906201943.AA02920@xagsun.epm.ornl.gov>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!XAGSUN.EPM.ORNL.GOV!romine

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!XAGSUN.EPM.ORNL.GOV!romine
From: romine@XAGSUN.EPM.ORNL.GOV (Charles H. Romine)
Newsgroups: gnu.bash.bug
Subject: bash 'history' command hangs if piped through more
Message-ID: <8906201943.AA02920@xagsun.epm.ornl.gov>
Date: 20 Jun 89 19:43:27 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 8