all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* view-lossage hard-codes 100 keystrokes
@ 2006-03-23 21:26 Drew Adams
  2006-03-24  9:35 ` Eli Zaretskii
  2006-03-24 23:24 ` Richard Stallman
  0 siblings, 2 replies; 6+ messages in thread
From: Drew Adams @ 2006-03-23 21:26 UTC (permalink / raw)


Any chance that the number of keystrokes displayed by `view-lossage',
currently hard-coded at 100, could be made a user option?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: view-lossage hard-codes 100 keystrokes
  2006-03-23 21:26 view-lossage hard-codes 100 keystrokes Drew Adams
@ 2006-03-24  9:35 ` Eli Zaretskii
  2006-03-24 13:36   ` Kim F. Storm
  2006-03-24 23:24 ` Richard Stallman
  1 sibling, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2006-03-24  9:35 UTC (permalink / raw)
  Cc: emacs-devel

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Thu, 23 Mar 2006 13:26:05 -0800
> 
> Any chance that the number of keystrokes displayed by `view-lossage',
> currently hard-coded at 100, could be made a user option?

It's not easily done, since the keys are recorded in a statically
allocated C array whose size is a compile-time constant.  I won't
recommend such a change for before the release, but that's just me.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: view-lossage hard-codes 100 keystrokes
  2006-03-24  9:35 ` Eli Zaretskii
@ 2006-03-24 13:36   ` Kim F. Storm
  2006-03-24 14:42     ` Drew Adams
  2006-03-24 23:26     ` Richard Stallman
  0 siblings, 2 replies; 6+ messages in thread
From: Kim F. Storm @ 2006-03-24 13:36 UTC (permalink / raw)
  Cc: emacs-devel

Eli Zaretskii <eliz@gnu.org> writes:

> It's not easily done, since the keys are recorded in a statically
> allocated C array whose size is a compile-time constant. 

Actually, it is recorded in a Lisp Vector, so it should be
trivial to increase the size of that vector.

We could add the size of the lossage buffer as a second
arg to clear-this-command-keys which already interfaces
to the recent keys vector.

> I won't
> recommend such a change for before the release, but that's just me.

I don't see an urgent need, but it would be a trivial change.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: view-lossage hard-codes 100 keystrokes
  2006-03-24 13:36   ` Kim F. Storm
@ 2006-03-24 14:42     ` Drew Adams
  2006-03-24 23:26     ` Richard Stallman
  1 sibling, 0 replies; 6+ messages in thread
From: Drew Adams @ 2006-03-24 14:42 UTC (permalink / raw)


    > It's not easily done, since the keys are recorded in a statically
    > allocated C array whose size is a compile-time constant.

    Actually, it is recorded in a Lisp Vector, so it should be
    trivial to increase the size of that vector.

    We could add the size of the lossage buffer as a second
    arg to clear-this-command-keys which already interfaces
    to the recent keys vector.

    > I won't
    > recommend such a change for before the release, but that's just me.

    I don't see an urgent need, but it would be a trivial change.

No, nothing urgent or even very important. If it could be done, I think it
would be helpful. Even increasing 100 to, say 500 or 1000 would be helpful.

For some reason, I find that on the rare occasions that I need to use this,
what I'm looking for is often further back than 100 keystrokes.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: view-lossage hard-codes 100 keystrokes
  2006-03-23 21:26 view-lossage hard-codes 100 keystrokes Drew Adams
  2006-03-24  9:35 ` Eli Zaretskii
@ 2006-03-24 23:24 ` Richard Stallman
  1 sibling, 0 replies; 6+ messages in thread
From: Richard Stallman @ 2006-03-24 23:24 UTC (permalink / raw)
  Cc: emacs-devel

    Any chance that the number of keystrokes displayed by `view-lossage',
    currently hard-coded at 100, could be made a user option?

I would not mind if this were done, but it should be after the release.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: view-lossage hard-codes 100 keystrokes
  2006-03-24 13:36   ` Kim F. Storm
  2006-03-24 14:42     ` Drew Adams
@ 2006-03-24 23:26     ` Richard Stallman
  1 sibling, 0 replies; 6+ messages in thread
From: Richard Stallman @ 2006-03-24 23:26 UTC (permalink / raw)
  Cc: eliz, emacs-devel

    > I won't
    > recommend such a change for before the release, but that's just me.

    I don't see an urgent need, but it would be a trivial change.

I am glad it is so simple.  I'd still rather save it for after the
release, but at that time, please make the change.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-03-24 23:26 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-23 21:26 view-lossage hard-codes 100 keystrokes Drew Adams
2006-03-24  9:35 ` Eli Zaretskii
2006-03-24 13:36   ` Kim F. Storm
2006-03-24 14:42     ` Drew Adams
2006-03-24 23:26     ` Richard Stallman
2006-03-24 23:24 ` Richard Stallman

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.