unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 17:37:47 -0400	[thread overview]
Message-ID: <jwvegaq49gy.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 56FD5468.1070609@gmail.com

> Is that right? That will work in this case, but in general isn't it a bad
> idea to setq a defcustom, given that it won't run its :set form?

That's why there's the

   (add-hook 'minibuffer-setup-hook #'cursor-intangible-mode)

You should always be able to set things up with good ol' setq
and friends.  Custom is something you *can* use but shouldn't have to
(tho, admittedly, currently our story for Elisp-level customization of
faces is rather poor, so for those I think that Custom is the only
reasonable option).


        Stefan




  reply	other threads:[~2016-03-31 21:37 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
2016-03-31 14:58   ` Kaushal Modi
2016-03-31 16:46   ` Clément Pit--Claudel
2016-03-31 21:37     ` Stefan Monnier [this message]
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

  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=jwvegaq49gy.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 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).