---------- Forwarded message ----------
From: Axel Liljencrantz <[EMAIL PROTECTED]>
Date: Feb 17, 2006 11:30 AM
Hmmm, did you intend for this mail to be on-list? If so, feel free to
forward this reply to the list as well...
On 2/9/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> Allowing "foo |; bar" is bad because it complicates the rule for
> ending statements: a statement ends at a newline or semicolon EXCEPT
> if the preceding token is a pipe.
>
> A better option is to have an escape character (backslash), as
> Netocrat suggested earlier:
>
> for h in (cat /etc/dupload.conf $HOME/.dupload.conf ^/dev/null \
> | awk -F "=" '/('\''fqdn'\''| *fqdn *=)/ {print $2}' \
> | cut -d"'" -f2 \
> | cut -d'"' -f2)
> set hosts $hosts $h
> end
>
> In this way, semicolon (;) and newline mean the same thing, and
> strange expressions like "foo |; bar" are avoided. Axel originally
> objected (and I replied):
I dislike this because it is impossible to tell if a newline is
escaped or if one is escaping a space character. Though I've thought
about this for a bit and have come to the conclusion that this is an
editor issue. An editor could, if it wanted to, differentiatte between
the two, for example by highlighting the backslashed newline using a
different background color.
I guess an otherwise rather sane syntax should not be punished because
editors are stupid.
>
> > > > [...] I do not think it is a good idea to allow
> > > > a single-line command to extend to the next terminal line on
> > > > overflow, since this will lead to subtle visual glitches unless you
> > > > start doing crazy stuff like implement a full terminal emulator in
> > > > the shell.
> > >
> > > Other shells manage it - I wonder what the usual approach is.
> >
> > The usual approach is to slightly break the shell. Long lines will
> > result in parts of the prompt beeing visible where it shouldn't, and
> > other minor issues, at least on some terminals. Other terminals
> > handle things differently. Anyway, I think this will be a minor
> > issue once multiline editing is in place.
>
>
> By the way, I too have been getting messages with empty bodies from
> Axel and Nick, including this one. It is probably GMail's fault.
> GMail's "message text garbled?" link (under "More Options") leads to a
> page that suggests setting the character encoding, but that does not
> help. What encoding do you use?
I've switched a charset option in the properties - preliminary results
is that things are now better. Let me know...
>
>
> On 2/8/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> >
>
--
Axel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
