all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: 10550@debbugs.gnu.org
Subject: bug#10550: 24.0.92; doc of `history-length'
Date: Wed, 18 Jan 2012 15:48:43 -0800	[thread overview]
Message-ID: <135AFF1F7DC1475CA2415422DB477571@us.oracle.com> (raw)

First, this var should really have `max' in its name.
As a general rule, numeric limit vars should have `max' or
`min' in the name.
 
As far as the doc goes, the most important thing is missing.  One can
pretty much guess that this value limits the length of history lists,
but the question is which history-list entries are dropped: the oldest
or the new ones?  Does the list stay the same, with new values rejected,
or do new ones replace the oldest ones? Or do new ones replace the
next-newest ones?  Why make users guess or experiment?
 
And for the doc string the info is also missing about which history
lists are affected: "those that don't specify their own maximum lengths"
(to quote the Elisp manual).
 

In GNU Emacs 24.0.92.1 (i386-mingw-nt5.1.2600) of 2012-01-16 on MARVIN
 Windowing system distributor `Microsoft Corp.', version 5.1.2600
 configured using `configure --with-gcc (4.6) --no-opt --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include --ldflags
 -LD:/devel/emacs/libs/gnutls-3.0.9/lib'
 






             reply	other threads:[~2012-01-18 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 23:48 Drew Adams [this message]
2012-01-28  3:04 ` bug#10550: 24.0.92; doc of `history-length' Chong Yidong

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=135AFF1F7DC1475CA2415422DB477571@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10550@debbugs.gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.