<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">We can fix the documentation then.<div class=""><br class=""></div><div class="">christos<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 10, 2020, at 8:02 AM, H.Merijn Brand <<a href="mailto:h.m.brand@xs4all.nl" class="">h.m.brand@xs4all.nl</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="protected-part" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div class="protected-title">Signed PGP part</div><div class="protected-content">On Sat, 8 Feb 2020 11:39:40 -0500, Christos Zoulas<br class=""><<a href="mailto:christos@zoulas.com" class="">christos@zoulas.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">There is histlit for that... (to print the actual input line).<br class=""></blockquote><br class="">I know that one. I was wondering about the inconsistency between the<br class="">docs and the default expansion.<br class=""><br class="">Reading the docs I would *not* expect the space<br class=""><br class=""><blockquote type="cite" class="">christos<br class=""><br class=""><blockquote type="cite" class="">On Jan 31, 2020, at 4:41 AM, H.Merijn Brand <<a href="mailto:h.m.brand@xs4all.nl" class="">h.m.brand@xs4all.nl</a>><br class="">wrote:<br class=""><br class="">Signed PGP part<br class="">I use >& >>& and |& on a regular basis. very regular :)<br class=""><br class="">The docs refer to these like:<br class=""><br class=""><blockquote type="cite" class="">name<br class="">! name<br class="">& name<br class="">&! name <br class=""></blockquote> The file name is used as standard output. If the<br class="">file does not exist then it is created; if the file exists, it is<br class="">truncated, its previous contents being lost.<br class=""><br class=""> If the shell variable noclobber is set, then the file<br class="">must not exist or be a character special file (e.g., a<br class="">terminal or `/dev/null') or an error results. This helps prevent<br class="">acciden- tal destruction of files. In this case the `!' forms<br class="">can be used to suppress this check. If notempty is given in<br class="">noclob- ber, `>' is allowed on empty files; if ask is<br class="">set, an interacive confirmation is presented, rather than an error.<br class=""><br class=""> The forms involving `&' route the diagnostic output<br class="">into the specified file as well as the standard output.<br class="">name is expanded in the same way as `<' input filenames are. <br class=""></blockquote>[...] <br class=""><blockquote type="cite" class=""> Like `>', but appends output to the end of name. If<br class="">the shell variable noclobber is set, then it is an error for the<br class="">file not to exist, unless one of the `!' forms is given.<br class=""><br class=""> :<br class=""><br class=""> Diagnostic output may be directed through a pipe with the<br class="">standard out- put. Simply use the form `|&' rather than just `|'.<br class=""><br class="">Note there is no space between the '>' or '|' and the '&'<br class=""><br class="">But in the history, these are store separated by a space :(<br class=""><br class="">% echo Foo >& /dev/null<br class="">% echo Foo |& cat > /dev/null<br class="">% echo Foo >>& /dev/null<br class="">% history 4<br class=""> 502 01-31 10:37:20 echo Foo > & /dev/null<br class=""> 503 01-31 10:37:33 echo Foo | & cat > /dev/null<br class=""> 504 01-31 10:37:41 echo Foo >> & /dev/null<br class=""> 505 01-31 10:37:46 history 4<br class=""><br class="">Not that it causes problems, but I find it confusing and it makes<br class="">repeating commands and editing more complex. At least in my brain<br class=""><br class="">Is there a (good) reason to add the unneeded space into the<br class="">history? <br class=""></blockquote></blockquote><br class=""><br class="">--<span class="Apple-converted-space"> </span><br class="">H.Merijn Brand <a href="http://tux.nl" class="">http://tux.nl</a> Perl Monger <a href="http://amsterdam.pm.org/" class="">http://amsterdam.pm.org/</a><br class="">using perl5.00307 .. 5.31 porting perl5 on HP-UX, AIX, and Linux<br class=""><a href="https://useplaintext.email" class="">https://useplaintext.email</a> <a href="https://tux.nl" class="">https://tux.nl</a> <a href="http://www.test-smoke.org" class="">http://www.test-smoke.org</a><br class=""><a href="http://qa.perl.org" class="">http://qa.perl.org</a> <a href="http://www.goldmark.org/jeff/stupid-disclaimers/" class="">http://www.goldmark.org/jeff/stupid-disclaimers/</a><br class=""></div></div><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span id="cid:32B7E312-3B60-4C2A-A50F-2A684D781B0E@astron.com"><sanitizer.log></span></div></blockquote></div><br class=""></div></body></html>