unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: comint-prompt-read-only causes problems in Gnus message mode
Date: Sun, 21 Nov 2004 10:24:31 -0600 (CST)	[thread overview]
Message-ID: <200411211624.iALGOVl21497@raven.dms.auburn.edu> (raw)
In-Reply-To: <m33bz31b5g.fsf@ate.maierh> (message from Harald Maier on Sun, 21 Nov 2004 16:20:43 +0100)

Harald Maier wrote:

   In other modes the inserted prompt too has the property 'read-only'

Did you check this?  (You can do `C-u C-x =' to check the text
properties of a character.)

   but there it's possible to delete the text (e.g. text-mode or the
   normal mail mode).

By default `read-only' is in yank-excluded-properties.  In that
setting, the copied text should not have the `read-only' property.  If
you remove `read-only' from yank-excluded-properties the copied text
should be _truly_ read-only.  Playing around a little bit, this seems
to be exactly what happens in practice, as it should.  So the
_combination_ of the two quotes above looks surprising.

   Except in the Gnu 'Message' mode. Here you are *not able* to delete
   the inserted prompt.  'Message' mode always complains 'Text is read
   only'.

I do not use message mode myself and am completely unfamiliar with it.
So it is difficult for me to fix this bug, which, at first sight, does
not seem to be specific to the comint prompt.  At first sight, it
would look like message mode does not respect
`yank-excluded-properties'.  It should.  I hope somebody familiar with
message mode can look into this.

Sincerely,

Luc.

  reply	other threads:[~2004-11-21 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21 15:20 comint-prompt-read-only causes problems in Gnus message mode Harald Maier
2004-11-21 16:24 ` Luc Teirlinck [this message]
2004-11-21 17:38   ` Harald Maier
2004-11-21 18:04     ` Luc Teirlinck
2004-11-23 16:29       ` Richard Stallman

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=200411211624.iALGOVl21497@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).