Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Rationalized? aliases
- X-seq: zsh-workers 577
- From: schaefer@xxxxxxxxxxxxxx (Barton E. Schaefer)
- To: Mark Borges <mdb@xxxxxxxxxxxx>
- Subject: Re: Rationalized? aliases
- Date: Wed, 8 Nov 1995 17:07:43 -0800
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: Mark Borges <mdb@xxxxxxxxxxxx> "Re: Rationalized? aliases" (Nov 8, 5:52pm)
- References: <199511082317.SAA29367@xxxxxxxxxxxxxxxxxxxxxxxxx> <coleman@xxxxxxxxxxxxxxx> <951108153643.ZM22842@xxxxxxxxxxxxxxxxx> <9511090052.AA17663@xxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxxxxxxxxx
On Nov 8, 5:52pm, Mark Borges wrote:
} Subject: Re: Rationalized? aliases
}
} B> e="gnuclient -q"
} B> [[ $HOST != $HOMESYSTEM ]] && alias e="$=e -h $HOMESYSTEM" || alias e="$=e"
}
} An interesting idea, but it doesn't seem to do the same thing on my
} system:
}
} $ e="gnuclient -q"
} $ echo $=e
} gnuclient -q
} $ alias e="$=e -h $HOMESYSTEM"
} $ type e
} e is an alias for gnuclient
Looks like a bug. Try it with just $e rather than $=e ... using $=e was
a typo anyway; with the double quotes around it, it *should* have become
completely equivalent to just $e. Instead, zsh seems to have broken the
entire quoted string into two words at the space in the value of $e.
--
Bart Schaefer Vice President, Technology, Z-Code Software
schaefer@xxxxxxxxxx Division of NCD Software Corporation
http://www.well.com/www/barts
Messages sorted by:
Reverse Date,
Date,
Thread,
Author