On Thu, Sep 28, 2006 at 07:34:08PM -0400, Philip Ganchev wrote:
> >except that this is not enough to cover the whole range of legal sh or
> >csh syntax that we could possibly be subjected with here.
> >(the value could be in "" instead of '', and i have no idea what else)
> So we have to look at th
On Thu, Sep 28, 2006 at 05:24:33PM -0400, Philip Ganchev wrote:
> Did you mean something like:
>
> #! fish
> command dbus-launch | sed -r 's/=/ /' | while read i j
>set $i (echo $j | sed -r 's/^\'//; s/\'$//; s/[^:]*://')
> end
> echo $DBUS_SESSION_BUS_ADDRESS | tr , '\n' | tr = ' ' | whil
>> An alternative approach that actually almost always works is to parse
>> the manpage, at least as a fallback. I was looking at command
>> completion a while back and this approach worked with nearly every
>> manpage I threw at it.
>
> If you still have the code and have the option of releasing i
On Thu, Sep 28, 2006 at 02:04:19PM +0200, Axel Liljencrantz wrote:
> In what ways do fish and csh quoting differ?
the quoting difference was not meant in reference to csh but to the fact
that i can neither just eval the following nor split it on the =
because i also must remove the '' or they will
