unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"65348@debbugs.gnu.org" <65348@debbugs.gnu.org>
Subject: bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively
Date: Fri, 18 Aug 2023 15:43:47 +0000	[thread overview]
Message-ID: <uHK37UO2MvGkOWHQsyjyhn1cFn4Wcljzatv7bGOTx4IA5PwjONCzBkz8pgf_Np9QPNv49uolGe4zAKeV1UnLqJJvoXeHiuHdUfOlFbzk9iE=@protonmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488A6C48A9CA2FAE8BDBC20F31BA@SJ0PR10MB5488.namprd10.prod.outlook.com>


------- Original Message -------
On Saturday, August 19th, 2023 at 3:16 AM, Drew Adams <drew.adams@oracle.com> wrote:


> > > You can have it there. It does work.
> > 
> > But you are designating it as deprecated, which makes
> > others think that something awful is going to happen to it.
> 
> 
> Agreed. Better to not deprecate it and just explain
> the pros and the cons. However, Emacs deprecated it
> long ago...
> 
> Deprecation shouldn't be used for this kind of
> stylistic choice. For that, when those deciding
> agree on what's the best style, and they agree that
> it's helpful to pass along their suggestion in the
> interest of consistency (for example), then it can
> be advertised as a stylistic convention.
> 
> IMHO, there was never any call for this to be
> branded as "deprecated". I said so at the time,
> but other voices prevailed. History.
> ___
> 
> 
> [FWIW, Icicles considers it not deprecated. The doc
> string of `completing-read' in Icicle mode has this: INITIAL-INPUT is considered deprecated by vanilla Emacs, but not by Icicles. If INITIAL-INPUT is nil and DEF is non-nil, the user can use` next-history-element' to yank DEF into the
> minibuffer.
> 
> In addition, with Icicles users can choose the
> behavior they prefer wrt inserting the DEFAULT
> value, showing it in the prompt, and selecting it
> if inserted.
> 
> See https://www.emacswiki.org/emacs/Icicles_-_Customization_and_General_Tips#icicle-default-value.
> 
> ]
> 
> > The introduction of HIST is only making a good
> > function quite terrible to use, becoming an
> > over-engineering piece of junk to avoid.
> 
> Useless to claim, without saying why you think so.
> And you're quite wrong here, FWIW. HIST is your
> friend.

When using my own function that selects from a collection, I am never 
interested in the history.  Just want it to cycle through the entries,
that's all.  And the less things I got to type, the better.
 
> [But minibuffer history too can be improved for users:
> https://www.emacswiki.org/emacs/Icicles_-_History_Enhancements.
> ]
> 
> > > > I find using INITIAL quite useful because the
> > > > user sees something filled up.
> 
> 
> Yes. More importantly, it's there for you to edit.
> 
> As with everything else, inserting it isn't always
> a plus or always a minus, and different users can
> find it a plus or minus in the same context.
> 
> Callers of `completing-read' can decide whether it
> makes sense (they think) to insert. And users
> should be able to override the caller's choice.

It seems that now I have to know all about the HIST things,
the DEF, the over-riding of same value to call some function 
that I have to write to get the behaviour I was using, etc. 
 
> > Having the user yank it from the default to the
> > minibuffer is a bother
> 
> 
> Having it inserted automatically can also be a
> bother. Different contexts (different calls to
> `completing-read') can call for different behavior,
> and different users can, and do, have different
> ideas about what behavior is more bothersome.

Right.  But if someone wants it displayed immediately, have
to use M-n becomes a bother.  






  reply	other threads:[~2023-08-18 15:43 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  0:47 bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17  5:49 ` Eli Zaretskii
2023-08-17  6:05   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17  7:20     ` Eli Zaretskii
2023-08-17 10:27       ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 10:45         ` Eli Zaretskii
2023-08-18  0:35           ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18  1:47             ` Drew Adams
2023-08-18  3:49             ` Eli Zaretskii
2023-08-18  5:13               ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18  5:36                 ` Eli Zaretskii
2023-08-18  5:56                   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18  6:32                     ` Eli Zaretskii
2023-08-18  8:40                       ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 12:14                         ` Eli Zaretskii
2023-08-18 12:27                           ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 12:30                             ` Eli Zaretskii
2023-08-18 12:55                               ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 13:27                                 ` Eli Zaretskii
2023-08-18 13:36                                   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 15:23                                     ` Drew Adams
2023-08-18 15:16                 ` Drew Adams
2023-08-18 15:43                   ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-18 17:33                     ` Drew Adams
2023-08-18 19:12                       ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 21:03                         ` Drew Adams
2023-08-19  1:55                           ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19  2:34                         ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19  4:14                           ` Drew Adams
2023-08-19  4:22                             ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19  4:46                               ` Drew Adams
2023-08-19  5:05                                 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19  6:34                                   ` Eli Zaretskii
2023-08-19 16:20                                     ` Drew Adams
2023-08-19 19:19                                       ` Eli Zaretskii
2023-08-19 20:56                                         ` Drew Adams
2023-08-20 16:39                                           ` Juri Linkov
2023-08-21  0:23                                             ` Drew Adams
2023-08-21  4:34                                               ` Christopher Dimech
2023-08-20  5:42                                         ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20  6:12                                           ` Michael Heerdegen
2023-08-20  6:23                                             ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20  6:34                                             ` Christopher Dimech
2023-08-21  0:25                                               ` Drew Adams
2023-08-21  4:26                                                 ` bug#65348: RE: [External] : " Christopher Dimech
2023-08-21  5:23                                                   ` Drew Adams
2023-08-21  6:29                                                     ` Christopher Dimech
2023-08-21  7:21                                                     ` bug#65348: " Christopher Dimech
2023-08-21 11:40                                                       ` Eli Zaretskii
2023-08-21 12:07                                                         ` Christopher Dimech
2023-08-21 12:25                                                           ` Eli Zaretskii
2023-08-21 13:27                                                             ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-21 16:08                                                         ` Drew Adams
2023-08-18 19:45                       ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 21:07                         ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='uHK37UO2MvGkOWHQsyjyhn1cFn4Wcljzatv7bGOTx4IA5PwjONCzBkz8pgf_Np9QPNv49uolGe4zAKeV1UnLqJJvoXeHiuHdUfOlFbzk9iE=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65348@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=heimeborgia@protonmail.com \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).