From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 12890@debbugs.gnu.org
Subject: bug#12890: read-face-attribute, face-valid-attribute-values do not handle all :underline etc forms
Date: Mon, 11 Jul 2022 15:12:37 +0200 [thread overview]
Message-ID: <87bktvvlmi.fsf@gnus.org> (raw)
In-Reply-To: <871qvy3p5j.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 09 Jun 2022 16:08:40 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It might be nice to have the `SPC' in minibuffer-local-completion-map to
> be more DWIM -- don't try to complete if it's "obvious" that the user
> doesn't want completion. Myself, I've disabled completion on `SPC'
> because it's really annoying, but perhaps there is something we could do
> here? I.e., if there are no completions, then just insert a `SPC' and
> make that the new default binding for `SPC' here?
>
> Because I think that would make usability here a lot better. (It could
> say "No completions; inserting space".)
>
> Opinions?
Thinking about this a bit more, I think it's likely that there are
people that are relying on SPC being bound to
`minibuffer-complete-word', and it would be too annoying to change this
behaviour (even when there are no completions to be had).
It could be added as an option, but I don't think it would be a very
popular option -- people that don't like the SPC behaviour already have
(define-key minibuffer-local-completion-map " " 'self-insert-command)
and the rest wouldn't want to use this, anyway. So I'm closing this bug
report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-07-11 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 7:39 bug#12890: read-face-attribute, face-valid-attribute-values do not handle all :underline etc forms Glenn Morris
2022-05-10 12:19 ` Lars Ingebrigtsen
2022-06-09 14:08 ` Lars Ingebrigtsen
2022-07-11 13:12 ` Lars Ingebrigtsen [this message]
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=87bktvvlmi.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12890@debbugs.gnu.org \
--cc=rgm@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.