zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ifh.de>
To: Timothy J Luoma <luomat+zsh+users@luomat.peak.org>,
	zsh-users@math.gatech.edu (Zsh users list)
Subject: Re: confusion over the proper way to make an alias
Date: Fri, 07 Nov 1997 16:33:34 +0100	[thread overview]
Message-ID: <199711071533.QAA05401@hydra.ifh.de> (raw)
In-Reply-To: "Timothy J Luoma"'s message of "Fri, 07 Nov 1997 09:54:47 MET." <199711071454.JAA15523@luomat.peak.org>

Timothy J Luoma wrote:
> 
> I have been setting up a new zsh account on a LINUX machine running ZSH  
> 3.0.3 and found that I could not use:
> 
> alias ls="ls $LS_OPTIONS"
> 
> I had to use
> 
> alias ls="command ls $LS_OPTIONS"
> 
> or else I got the 'job table full' message mentioned in the FAQ.

That means you have function, as well as an alias, defined to ls().  It's
possible to have both, but only the function can fill your job table and
needs the `command ls' inside it.  (Also, remember the catch: if you define
an alias for ls, and the function next with 'ls() {...}', the alias
gets expanded in the definition, causing havoc.)

> I went to my NeXT machine running 3.0.5 and found that if I used:
> 
> alias ls="command ls $LS_OPTIONS"
> 
> I got:
> /usr/local/gnu/bin/ls: ls: No such file or directory

This should certainly work.  I can only think of checking paths, value
of $LS_OPTIONS, symbolic links, everything you've probably thought of.

-- 
Peter Stephenson <pws@ifh.de>       Tel: +49 33762 77366
WWW:  http://www.ifh.de/~pws/       Fax: +49 33762 77413
Deutsches Elektronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, Platanenallee 6, 15738 Zeuthen, Germany.


  reply	other threads:[~1997-11-07 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-07 14:54 Timothy J Luoma
1997-11-07 15:33 ` Peter Stephenson [this message]
1997-11-07 15:35   ` Timothy J Luoma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199711071533.QAA05401@hydra.ifh.de \
    --to=pws@ifh.de \
    --cc=luomat+zsh+users@luomat.peak.org \
    --cc=zsh-users@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).