From: "N. Raghavendra" <nyraghu27132@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: About how misspelled word are displayed
Date: Sun, 14 May 2017 18:37:22 +0530 [thread overview]
Message-ID: <87inl3io39.fsf@gmail.com> (raw)
In-Reply-To: <8778c766-ce0a-4b42-939d-96b0f0b49a82@default> (Drew Adams's message of "Fri, 12 May 2017 10:32:36 -0700 (PDT)")
At 2017-05-12T10:32:36-07:00, Drew Adams wrote:
> If you are not the one who defined a given defcustom,
> and if that defcustom uses a keyword such as :set, then a
> complicated beast has likely been created for you already.
>
> If you try to tame that beast without taking its nature
> into account (e.g., using just `setq') you can find
> yourself surprised.
I was curious about examples of such options, that is, of options for
which (setq option ...) and (customize-set-variable 'option ...) have
different effects. The option `minibuffer-prompt-properties' is one
such, as described in
http://xahlee.blogspot.in/2016/06/emacs-custom-set-variables-vs-setq.html
and
http://ergoemacs.org/emacs/emacs_stop_cursor_enter_prompt.html
If I do
emacs -Q --eval "(setq minibuffer-prompt-properties (append '(cursor-intangible t) minibuffer-prompt-properties))"
and type `M-x query-replace' and start pressing the left arrow key,
point goes over the prompt "M-x".
On the other hand, if I do
emacs -Q --eval "(customize-set-variable 'minibuffer-prompt-properties (append '(cursor-intangible t) minibuffer-prompt-properties))"
and type `M-x query-replace' and start pressing the left arrow key,
point is prevented from entering the prompt "M-x", and stops at the
letter "q" of the command name "query-replace".
Thus, (setq minibuffer-prompt-properties ...) and
(customize-set-variable 'minibuffer-prompt-properties ...) have
different effects. The reason, as pointed out by Clément Pit-Claudel in
a comment at the second URL above, is that the :set function of
minibuffer-prompt-properties does an
(add-hook 'minibuffer-setup-hook 'cursor-intangible-mode)
when the value being assigned is a list containing the symbol
`cursor-intangible'.
Raghu.
--
N. Raghavendra <raghu@hri.res.in>, http://www.retrotexts.net/
Harish-Chandra Research Institute, http://www.hri.res.in/
next prev parent reply other threads:[~2017-05-14 13:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 9:49 About how misspelled word are displayed Angelo Graziosi
2017-05-12 13:09 ` Kaushal Modi
2017-05-12 14:07 ` Angelo Graziosi
2017-05-12 14:14 ` tomas
2017-05-12 14:27 ` Emanuel Berg
2017-05-12 15:16 ` Drew Adams
2017-05-12 16:27 ` Emanuel Berg
2017-05-12 17:32 ` Drew Adams
2017-05-12 18:00 ` Emanuel Berg
2017-05-12 21:15 ` tomas
2017-05-12 21:28 ` N. Raghavendra
2017-05-12 22:08 ` Drew Adams
2017-05-13 14:15 ` N. Raghavendra
2017-05-13 14:59 ` Emanuel Berg
2017-05-13 15:07 ` Emanuel Berg
2017-05-13 15:22 ` Emanuel Berg
2017-05-13 15:34 ` N. Raghavendra
2017-05-13 15:54 ` Emanuel Berg
2017-05-13 17:59 ` Drew Adams
2017-05-14 13:07 ` N. Raghavendra [this message]
2017-05-12 19:30 ` Angelo Graziosi
2017-05-12 20:34 ` Drew Adams
2017-05-12 20:41 ` Drew Adams
2017-05-12 22:14 ` Angelo Graziosi
2017-05-12 23:42 ` Emanuel Berg
2017-05-13 0:22 ` John Mastro
2017-05-13 9:53 ` Emanuel Berg
2017-05-12 21:07 ` Emanuel Berg
2017-05-12 19:57 ` Angelo Graziosi
2017-05-12 20:56 ` Emanuel Berg
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=87inl3io39.fsf@gmail.com \
--to=nyraghu27132@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).