Running bash 3.1.17.
The odd time, when I pass an argument to a command - say for example
editing a file in vi - the shell will prompt me for further input, as
if I'd put a semicolon after the first argument. Going back through the
history, it appears as if that's what bash thinks I did.
Anyone come across this before?
rg
--
Robert Gallagher, Kerna Communications, | P (+353-1) 6647200
105 Lwr. Baggot St., Dublin 2, Ireland. | E robert at kerna.ie
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!