From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: revisiting history-file rewriting
Date: Fri, 18 Mar 2005 21:15:37 +0000 [thread overview]
Message-ID: <1050318211537.ZM1914@candle.brasslantern.com> (raw)
In-Reply-To: <20050318181921.GF5500@blorf.net>
On Mar 18, 10:19am, Wayne Davison wrote:
} Subject: Re: revisiting history-file rewriting
}
} 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 name seems a bit unwieldy, but I suppose one won't be typing it all
that often.
Appending to the history writes in place, too, though, doesn't it? Or
at least incremental appending does?
Maybe HIST_SAVE_BY_COPY, defaulting to on?
Another random thought, far too late for its own good:
HIST_SAVE_NO_DUPS default off should have been HIST_SAVE_DUPS default on,
so as to avoid the double negative in NO_HIST_SAVE_NO_DUPS. Oh, well.
next prev parent reply other threads:[~2005-03-18 21:15 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
2005-03-18 21:15 ` Bart Schaefer [this message]
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=1050318211537.ZM1914@candle.brasslantern.com \
--to=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).