From: Hrvoje Niksic <hniksic@srce.hr>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: (Hrvoje Niksic), zsh-workers@math.gatech.edu
Subject: Re: HISTSIZE
Date: 10 Jun 1996 21:10:30 +0200 [thread overview]
Message-ID: <kigafybpja1.fsf@jagor.srce.hr> (raw)
In-Reply-To: Zoltan Hidvegi's message of Mon, 10 Jun 1996 21:05:20 +0200 (MET DST)
Zoltan Hidvegi (hzoli@cs.elte.hu) wrote:
> > I wonder how difficult would it be to patch hist.c in such a way that
> > the actual size of the history list changes dynamically, HISTSIZE
> > being only an upper limit to that change.
>
> Zsh uses a HISTSIZE long array to store history entries. gethistent(X) is
> defined as (histentarr+((X)%histentct)) (with proper bounds checking at
> apropriate places). This is usually the most compact representation. A
> linked list can be used but then the pointers would require extra memory.
> histentarr is almost full in most cases since it is filled from $HISTFILE
> upon invocation. Most people do like to limit the number of stored history
> events since loading and saving big histories takes a long time. Of course
> SAVEHIST can be smaller than HISTSIZE but most people do not issue more
> than 1000 commands from one shell so HISTSIZE = SAVEHIST + 1000 should be
> enough.
Of course one must be able to limit the number of history items. But
if you want to unlimit it (which I like to do) by setting it to
100,000 or to a 1,000,000, is where the problems arise.
As far as I have seen, bash also represents the history list as an
array, but it starts off with a default size and realloc's it
dynamically each 50 or so commands. This way HISTSIZE is only a limit,
not a memory consumer.
So: gethistent(X) would still be equally defined, but the array would
change its size dynamically. Is this doable?
--
hniksic@srce.hr | Student of electrical engineering
hniksic@fly.cc.fer.hr | University of Zagreb, Croatia
------------------------------------------------------------------
I'm a Lisp variable -- bind me!
prev parent reply other threads:[~1996-06-10 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-08 20:17 HISTSIZE Hrvoje Niksic
1996-06-10 19:05 ` HISTSIZE Zoltan Hidvegi
1996-06-10 19:10 ` Hrvoje Niksic [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=kigafybpja1.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
--cc=hzoli@cs.elte.hu \
--cc=zsh-workers@math.gatech.edu \
/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).