From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Should minibuffer prompt be made intangible by default? (Was debbugs 21874: 25.0.50; point-entered no longer works)
Date: Thu, 31 Mar 2016 08:38:10 -0400 [thread overview]
Message-ID: <jwvmvpe6d6f.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CAFyQvY0aJqCdA9o3XJTj6hkqdS2vaGLVFit2b3Fi8g=bpOTjNA@mail.gmail.com
> ;; (car (cdr (car (get ..)))) -> (read-only t face minibuffer-prompt)
^^^^^^^^
This "car(cdr" should be spelled "eval" (there's no guarantee that the
arg has always the shape (quote ...something..)).
> (custom-set-variables '(minibuffer-prompt-properties
Don't do that. There should only ever be one call to
custom-set-variables, auto-written by Custom itself. As soon as you
move away from that, you're entering dangerous territory.
You should probably use customize-set-variable instead.
Tho I'd personally recommend that if you don't want to use the Custom
UI, then don't use Custom from Elisp either, and just use straight:
(setq minibuffer-prompt-properties
(append ... minibuffer-prompt-properties))
(add-hook 'minibuffer-setup-hook #'cursor-sensor-mode)
-- Stefan
next prev parent reply other threads:[~2016-03-31 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 16:46 Should minibuffer prompt be made intangible by default? (Was debbugs 21874: 25.0.50; point-entered no longer works) Kaushal Modi
2016-03-31 12:38 ` Stefan Monnier [this message]
2016-03-31 14:58 ` Kaushal Modi
2016-03-31 16:46 ` Clément Pit--Claudel
2016-03-31 21:37 ` Stefan Monnier
2016-03-31 22:04 ` Clément Pit--Claudel
2016-04-01 1:40 ` Configuring fontsets with `unicode-fonts` [Was: Re: Should minibuffer prompt be made intangible by default?] Alexis
2016-04-01 7:27 ` Eli Zaretskii
2016-04-01 10:00 ` Clément Pit--Claudel
2016-04-01 10:06 ` Eli Zaretskii
2016-04-02 8:57 ` Alexis
2016-04-02 10:32 ` Eli Zaretskii
2016-04-02 11:30 ` Alexis
2016-04-01 10:00 ` Clément Pit--Claudel
2016-04-02 11:31 ` Alexis
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=jwvmvpe6d6f.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.