all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 12377@debbugs.gnu.org
Subject: bug#12377: 24.2.50; `minibuffer-prompt-properties' should respect existing faces in prompt string
Date: Thu, 28 Apr 2016 17:21:36 -0700 (PDT)	[thread overview]
Message-ID: <8538abbc-b3cc-4fb3-b917-ec0c652ac729@default> (raw)
In-Reply-To: <87lh3x7jde.fsf@gnus.org>

Dunno why this needs to be done in C code anyway.

It is OK for Emacs to make the prompt read-only, I guess (i.e., to not let user code make it writable), though I would prefer that it just do that by default.

It is OK for Emacs to apply face `minibuffer-prompt' or whatever, by default.

It is not OK for Emacs to overwrite any text properties.

In general, user code should be allowed to do anything it wants to the prompt text. But Emacs should provide, by default, a read-only prompt with its standard face.

And it should be done in Lisp, preferably, so users can easily modify it at will.  This is Emacs.  There is nothing critical for performance about setting up the minibuffer prompt string.





  reply	other threads:[~2016-04-29  0:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 16:31 bug#12377: 24.2.50; `minibuffer-prompt-properties' should respect existing faces in prompt string Drew Adams
2014-02-09  3:11 ` Lars Ingebrigtsen
2014-02-10 22:36   ` Drew Adams
2016-04-28 16:23 ` Lars Ingebrigtsen
2016-04-28 16:38   ` Drew Adams
2016-04-28 16:54     ` Lars Ingebrigtsen
2016-04-28 17:06       ` Lars Ingebrigtsen
2016-04-29  0:21         ` Drew Adams [this message]
2016-05-01 14:54         ` Lars Ingebrigtsen
2016-06-24 16:33 ` Drew Adams
2016-06-24 17:13   ` Noam Postavsky
2016-06-24 18:57     ` Drew Adams

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=8538abbc-b3cc-4fb3-b917-ec0c652ac729@default \
    --to=drew.adams@oracle.com \
    --cc=12377@debbugs.gnu.org \
    --cc=larsi@gnus.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.