zsh-users
 help / color / mirror / code / Atom feed
From: Eugene Dzhurinsky <jdevelop@gmail.com>
To: zsh-users@zsh.org
Subject: Re: delay in exitting from zsh shell
Date: Thu, 10 Nov 2011 12:15:53 +0200	[thread overview]
Message-ID: <20111110101553.GA1368@devbox.epam.com> (raw)
In-Reply-To: <111110021007.ZM6786@torch.brasslantern.com>

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

On Thu, Nov 10, 2011 at 02:10:07AM -0800, Bart Schaefer wrote:
> However, it might be simpler just to unset the options that cause the
> file to be deduped on shell exit, and e.g. allow it to be deduped on
> shell startup instead.


Okay, thank you for the explanations - I was sure that I am not seeing the
whole picture :) About the solution - is it possible to, for example,
configure ZSH to have alias for "de-fragmenting" such a large history files on
demand?

And the problem is that even if I comment out the lines:

HISTFILE=~/.histfile
HISTSIZE=10000
SAVEHIST=10000
#setopt append_history
#setopt inc_append_history
#setopt histignorealldups
#setopt histignorespace
#setopt histreduceblanks
#setopt histsavenodups
#setopt sharehistory
#setopt nohup

it still takes the same (as per my feeling) time as with having those lines in
the configuration. What may be wrong here?

-- 
Eugene N Dzhurinsky

[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2011-11-10 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 22:20 Eugene Dzhurinsky
2011-11-10  1:14 ` Rommel Martinez
2011-11-10  6:56   ` Eugene Dzhurinsky
2011-11-10  3:51 ` Bart Schaefer
2011-11-10  7:19   ` Eugene Dzhurinsky
2011-11-10 10:10     ` Bart Schaefer
2011-11-10 10:15       ` Eugene Dzhurinsky [this message]
2011-11-10 10:46         ` Bart Schaefer
2011-11-10 10:58           ` Eugene Dzhurinsky

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=20111110101553.GA1368@devbox.epam.com \
    --to=jdevelop@gmail.com \
    --cc=zsh-users@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).