zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayned@users.sourceforge.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: revisiting history-file rewriting
Date: Fri, 18 Mar 2005 10:19:21 -0800	[thread overview]
Message-ID: <20050318181921.GF5500@blorf.net> (raw)
In-Reply-To: <1050317180338.ZM32687@candle.brasslantern.com>

On Thu, Mar 17, 2005 at 06:03:38PM +0000, Bart Schaefer wrote:
> I'm OK with this, though I think the documentation should explain in
> more detail how it interacts with APPEND_HISTORY, INC_APPEND_HISTORY,
> and SHARE_HISTORY.

Yeah, my docs were pretty minimal.

> We already have HIST_APPEND; while we're at it, perhaps we add
> HIST_APPEND_INC, HIST_SHARE, and OVERWRITE_HISTORY with appropriate
> aliasing?

I don't like OVERWRITE_HISTORY because it sounds like something that
conflicts with APPEND_HISTORY.  Perhaps my option name needs to be
improved -- how about HIST_WRITE_IN_PLACE?  That seems to better
indicate that it is effecting how the history file is written out
rather than affecting how data is put into the history file.

As for the other aliases, I wouldn't mind seeing them added.

..wayne..


  reply	other threads:[~2005-03-18 18:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 20:40 Wayne Davison
2005-03-17  2:09 ` Geoff Wing
2005-03-17  2:49   ` Wayne Davison
2005-03-18 16:18     ` Andrey Borzenkov
2005-03-18 17:51       ` Wayne Davison
2005-03-18 18:02         ` Wayne Davison
2005-03-17 18:03 ` Bart Schaefer
2005-03-18 18:19   ` Wayne Davison [this message]
2005-03-18 21:15     ` Bart Schaefer
2005-03-18 21:47       ` Wayne Davison
2005-03-18 10:49 ` Peter Stephenson
2005-03-18 17:58   ` Wayne Davison
2005-03-18 18:24     ` Peter Stephenson
2005-03-18 22:53 ` Wayne Davison
2005-03-20  1:57   ` Bart Schaefer
2005-03-21 10:39     ` Peter Stephenson

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=20050318181921.GF5500@blorf.net \
    --to=wayned@users.sourceforge.net \
    --cc=schaefer@brasslantern.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).