zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Local history
Date: Fri, 16 Nov 2001 17:54:30 +0000	[thread overview]
Message-ID: <3BF552D6.EC8645D3@yahoo.co.uk> (raw)
In-Reply-To: <1489.1005931641@csr.com>

Peter Stephenson wrote:
> 
> I'm still thinking about a way of getting a local command history.  My

> Does anyone have any experience of or feeling for this?

I don't have any suitable "experience of" but my feeling is that rather
than having separate mechanisms for making different things local
(traps, history, functions, options etc), it would be better if all
these things were available as parameters. Syntactically there then only
needs to be one way to manipulate these structures from the shell. The
syntax here might be just `local .sh.history'. I said something to this
effect on the shell list a while back in reference to local traps.

For these structures (history etc) to be implemented efficiently as
parameters compound variables would help but we might get round it by
just using special types. For some things it would just amount to things
in zsh/parameter being the real data.

Oliver

_____________________________________________________________________
This message has been checked for all known viruses by the 
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp


  reply	other threads:[~2001-11-16 17:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 17:27 Peter Stephenson
2001-11-16 17:54 ` Oliver Kiddle [this message]
2001-11-16 18:01 ` Danek Duvall
2001-11-19  8:40   ` Wischnowsky, Sven
2001-11-19 16:48     ` Bart Schaefer
2001-11-19 17:36       ` Peter Stephenson
2001-11-19 17:58         ` Bart Schaefer
2001-11-21 18:57       ` history editing Danek Duvall
2001-11-21 22:21   ` Wayne Davison
2001-11-21 22:30     ` Danek Duvall

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=3BF552D6.EC8645D3@yahoo.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).