rect its output,
but it's too late now.
--
Ed Avis
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
The reason I found 'whoami | >out' to be surprising is that none of the
following work:
% | >out
% (whoami |)
% whoami | | cat
If | > is a valid construct, what are its semantics?
--
Ed Avis
__
This ema
ntax error
% whoami | # syntax error
--
Ed Avis
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
message explaining that only the current subprocess
would be interrupted, and saying to hit Ctrl-Z again if that is what you really
wanted. I hope this might go some way to making things less confusing, and be
relatively quick to hack up.
--
Ed Avis
r' loop with
Ctrl-Z, then 'fg' and have it continue where it left off. If putting it into
the background is not practical then 'bg' can give an error message.
Backgrounding or foregrounding just one individual command, and then
abandoning the rest of the loop somehow, is surely never the desired
behaviour.
--
Ed Avis
e bound
to previous-history, so that those who flip back and forth between these
two GNU programs could keep using the same key sequence.
--
Ed Avis
__
This email has been scanned by the Symantec Email Security.cloud service
characters.
It could more usefully go back in the history instead. Then if you flip
between GNU
emacs and GNU bash you wouldn't keep typing the wrong thing.
--
Ed Avis
__
This email has been scanned by the Symantec
or the noise.
--
Ed L. Cashin <[EMAIL PROTECTED]>
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Lese selbst:
http://www.kommunisten-online.de/blackchanel/dresden3.htm
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
