zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayne@thedavisons.net>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: Zsh list <zsh-workers@zsh.org>,
	749969-forwarded@bugs.debian.org,
	 Peter Palfrader <weasel@debian.org>,
	Han Pingtian <hanpt@linux.vnet.ibm.com>
Subject: Re: Bug#749969: history no longer syncs immediately, INC_APPEND_HISTORY broken
Date: Sat, 31 May 2014 23:05:28 -0700	[thread overview]
Message-ID: <CAHSx_St_j95J0SLPYvcNiGZH0JSC1s_QR=S_psxheF=G8vf9Nw@mail.gmail.com> (raw)
In-Reply-To: <87d2eu5mmg.fsf@ft.bewatermyfriend.org>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

On Sat, May 31, 2014 at 2:21 AM, Frank Terbeck <ft@bewatermyfriend.org>
wrote:

> I think to enable both ways to be possible, there should be two options:
> INC_APPEND_HISTORY that enables the original behaviour and (if the name
> is agreeable) DELAY_INC_APPEND_HISTORY, that amends the behaviour of the
> original option in the way that is reflected by the current behaviour.
>

You should just be able to setopt SHARE_HISTORY to have zsh always append
the entry early.  Of course, that also has the effect of the shell
importing the shared history from other shells, so it's nice to have things
like up/down arrow set to only browse local history (while things like
search look in the shared history).  There was a fairly recent discussion
of up-line-or-local-history() functions and a discussion of making
everything local except for isearch functions.

..wayne..

      parent reply	other threads:[~2014-06-01  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140531074936.GA9011@valiant.palfrader.org>
2014-05-31  9:21 ` Frank Terbeck
2014-05-31 19:22   ` Peter Stephenson
2014-06-03 19:56     ` Peter Stephenson
2014-06-04  7:57       ` Han Pingtian
2014-06-04 14:50         ` Bart Schaefer
2014-06-04 16:13       ` Bart Schaefer
2014-06-01  6:05   ` Wayne Davison [this message]

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='CAHSx_St_j95J0SLPYvcNiGZH0JSC1s_QR=S_psxheF=G8vf9Nw@mail.gmail.com' \
    --to=wayne@thedavisons.net \
    --cc=749969-forwarded@bugs.debian.org \
    --cc=ft@bewatermyfriend.org \
    --cc=hanpt@linux.vnet.ibm.com \
    --cc=weasel@debian.org \
    --cc=zsh-workers@zsh.org \
    /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).