emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [External] : Re: Turning on savehist-mode by default


From: Drew Adams
Subject: RE: [External] : Re: Turning on savehist-mode by default
Date: Sun, 17 Dec 2023 22:22:28 +0000

> >>> switching it on by default can help with discovering it.
> >>
> >> If true (and it likely is), then it's true
> >> of_everything_  that is off by default.
> >
> > Yes, it is.
> >
> > But it's a counter-argument to the principle of the least inconvenience,
> > presented by Juergen. Not an absolute principle.
> 
> Right. Generally, I agree to Drew's point of view. But on the other
> hand, what would be an advantage of switching on savehist mode by
> default? Maybe it would make it easier for users of other editors to
> switch to Emacs because savehist mode provides a feature they are used
> to and they could miss. This might be a good point indeed.

Are users of other editors really accustomed
to persistent recording of their inputs?
We're talking here about minibuffer input.

With completion - especially with some "fancy
completion frameworks", minibuffer input can
include what corresponds to menu choices in
other apps.  Do users of other editors expect
their _menu_ choices to be recorded
persistently?  I doubt it.
___

But if we think it's important to record such
choices when entered in the minibuffer, then
why not propose to have savehist record Emacs
menu choices more generally?

When you use menubar menu item File > Open
File' to open file XYZ, should savehist
record that in some `menubar-file-history'
variable?  Maybe laughable. ;-)
___

But FWIW, in Icicles there's user option
`icicle-menu-items-to-history-flag':

  `icicle-menu-items-to-history-flag' is a
  variable defined in `icicles-opt.el'.

  Its value is t

  Non-nil means to add menu-item commands to
  the command history.
  This history is `extended-command-history'.

And note that it's ON by default!  (Of course,
Icicle mode itself isn't ON by default.)

`M-x' input contributes to that command
history. And there are features (commands
etc.) that let you reuse/invoke commands in
that history - `M-x' is one such feature!
So why not also let them reuse commands
you've invoked interactively in other ways
than just `M-x'?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]