unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 19152@debbugs.gnu.org
Subject: bug#19152: 25.0.50; Suggestions for M-x commands
Date: Tue, 25 Nov 2014 09:09:33 +0000	[thread overview]
Message-ID: <87lhmzsl2q.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <jwvr3wssl7j.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 24 Nov 2014 09:57:11 -0500")

>>>>> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

 >> One more reason for the new features to provide a way for the user
 >> to opt out, – just in case they turn to be buggy.

 > Options to circumvent bugs are a bad idea, in general (with
 > exceptions, of course, like everything, such as when the bug is
 > particularly hard to fix, or occurs in some code we can't control).

	Analogously speaking, isn’t --without-x-toolkit just an option
	to circumvent Gtk-related bugs?

 >>>> I believe there should be a variable to customize this behavior
 >>>> (say, suggest-shorter-command-limit; defaulting to 5, but with nil
 >>>> as an option to disable such suggestions altogether.)  As a
 >>>> workaround, I’ve simply disabled it entirely (see the patch
 >>>> MIMEd.)

 >>> I don't think that's needed.

 >> The mere fact that bug#19152 was filed suggests otherwise.

 > An option to turn the feature off is fine.  An option to choose the
 > number of chars we have to gain is not.

	Why not?

	Diff-wise, the difference is two lines only: one in defcustom,
	to allow for an integer value for the option; the other in
	execute-extended-command--shorter, to replace the currently
	magic 5.

	That said, I’m fine with doing it either way.

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A





  reply	other threads:[~2014-11-25  9:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 21:51 bug#19013: 25.0.50; Suggestions for M-x commands Lars Magne Ingebrigtsen
2014-11-11  1:38 ` Stefan Monnier
2014-11-11  2:08   ` Jay Belanger
2014-11-11  4:01     ` Stefan Monnier
2014-11-11  2:45   ` Lars Magne Ingebrigtsen
2014-11-16 19:39   ` Lars Magne Ingebrigtsen
2014-11-16 19:41   ` Lars Magne Ingebrigtsen
2014-11-19  7:14 ` Ivan Shmakov
2014-11-23 11:50   ` bug#19152: " Ivan Shmakov
2014-11-24  4:11     ` Stefan Monnier
2014-11-24  7:01       ` bug#19013: bug#19152: " Ivan Shmakov
2014-11-24 14:57         ` bug#19152: " Stefan Monnier
2014-11-25  9:09           ` Ivan Shmakov [this message]
2014-11-25 14:50             ` Stefan Monnier
2014-11-25 15:45               ` Ivan Shmakov
2014-11-25 16:51                 ` Eli Zaretskii
2014-11-25 18:10                   ` Ivan Shmakov
2014-11-26  2:22                     ` Stefan Monnier
2016-04-30 15:22                   ` Lars Ingebrigtsen
2014-11-25 17:38                 ` Stefan Monnier
2014-11-24 13:12       ` bug#19152: bug#19013: bug#19152: bug#19013: " Eli Zaretskii
2014-11-28 23:15       ` Stefan Monnier
2014-12-02 10:14         ` bug#19152: " Ivan Shmakov
2014-12-02 13:57           ` Stefan Monnier
2016-03-09 11:37             ` Brendan O'Dea

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=87lhmzsl2q.fsf_-_@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=19152@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 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).