zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@ifh.de>,
	zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: pushdcycle and pushdignoredups
Date: Mon, 4 Nov 1996 10:19:15 -0800	[thread overview]
Message-ID: <961104101915.ZM17201@candle.brasslantern.com> (raw)
In-Reply-To: Peter Stephenson <pws@ifh.de> "Re: pushdcycle and pushdignoredups" (Nov  4,  9:40am)

On Nov 4,  9:40am, Peter Stephenson wrote:
} Subject: Re: pushdcycle and pushdignoredups
}
} "Bart Schaefer" wrote:
} > (Aside #2:  Does anybody wish there were an equivalent of "localoptions"
} > that applied to functions and aliases, so that autoloads could blow away
} > all the possible screwy redefinitions of builtins from their environment,
} > yet have them magically restored when the function exits?)
} 
} Yes, particularly aliases (I can put with `command ls', but `command 'ls''
} is going too far)

When does that problem come up?  I can't seem to get it to happen to me,
unless I use "alias -g" in which case I'd *expect* it to happen.

zagzig[337] alias echo
zagzig[338] alias echo='echo x'
zagzig[339] echo
x
zagzig[340] command echo

zagzig[341] function blat() {
function> echo
function> }
zagzig[342] blat
x
zagzig[343] function blat() {
function> command echo
function> }
zagzig[344] blat

zagzig[345]


-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern


  reply	other threads:[~1996-11-04 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-01 18:16 Bart Schaefer
1996-11-02  0:56 ` Zoltan Hidvegi
1996-11-03  8:53   ` Bart Schaefer
1996-11-04  8:40     ` Peter Stephenson
1996-11-04 18:19       ` Bart Schaefer [this message]
1996-11-05  8:08         ` Peter Stephenson
1996-11-05  8:40           ` "alias" vs. "command" Bart Schaefer

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=961104101915.ZM17201@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=pws@ifh.de \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@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).