>
> > [EMAIL PROTECTED] ~> echo foo \
> > bar \
> > foobar
> > foo
> > fish: Unknown command "bar"
> > fish: Unknown command "foobar"
> >
> > Why do I want to achieve it?
> > Simply for a reason of readability, I prefer it to
> > echo foo bar foobar barf ...
> >
> > Hope it is clearer my problem now (at least if it is worth the
> trouble...).
> >
>
> I think so. This should work:
>
> $ echo "foo
> bar
> foobar
> foo bar foobar"
>
> Is that what you're aiming for or am I still misunderstanding you?
>
> Axel
>
I suspect you are still misunderstanding.
In fish shellscripts, whitespace is significant (unlike, say, HTML, C, or
Perl). In particular, a newline is not the same as a space. But to enhance
readability, it's often preferable to split long commands over several
lines. Quotes will only sometimes work for this, it does not solve it
generally.
A way to split commands over multiple lines... in other words, a way to have
the shellscript ignore a newline or treat it like a space... can be helpful.
I personally am ambivalent... I would use the feature if it existed, but
wouldn't miss it much if it never does. I don't mind working with Basic or
Python syntax, which don't generally allow lines to be split either.
(Technically, VB does allow split lines, but I almost never used the
feature)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
