Path: utzoo!telly!philmtl!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!sbphy.ai.mit.edu!bfox
From: bfox@sbphy.ai.mit.edu (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: alias? some problem..
Message-ID: <8912051746.AA09687@sbphy.Ucsb.EDU>
Date: 5 Dec 89 17:46:44 GMT
References: <11925@phoenix.Princeton.EDU>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.cns.caltech.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 32


   Date: 4 Dec 89 19:16:13 GMT
   From: phoenix!tbrakitz@princeton.edu  (Triantaphyllos Byron Rakitzis)
   Organization: Princeton University, NJ
   Sender: bug-bash-request@prep.ai.mit.edu

   I can't really describe this problem accurately, since I'm not sure
   what caused it, but after using bash in the normal way certain
   commands started behaving in a really odd fashion. For example, I
   alias cd to a function which changes directories and then echoes the
   pwd. All of a sudden, nothing is echoed. Other commands behave
   normally, but as soon as I type an incorrect command (with the error
   message "command not found") all the previous stored `pwd`s show up
   all at once. The same thing happens with alias. alias produces no
   output, but after an error, all my aliases are flushed to stdout. 

   Is this some problem with buffered i/o in bash? This has only happened
   to me once so far, but it has happened to a friend of mine a couple of
   times already.

   Has anyone got any experience with this at all?

   Thanks.
   -- 
   "C Code."
	     "C Code run."
			   "Run, Code, run!"
   Byron Rakitzis. (tbrakitz@phoenix.princeton.edu ---- tbrakitz@pucc.bitnet)

I need the machine type, the OS, and the version of Bash.

Brian