From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: comint-prompt-read-only causes problems in Gnus message mode Date: Sun, 21 Nov 2004 12:04:24 -0600 (CST) Message-ID: <200411211804.iALI4Oh21595@raven.dms.auburn.edu> References: <200411211624.iALGOVl21497@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1101060392 4636 80.91.229.6 (21 Nov 2004 18:06:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 21 Nov 2004 18:06:32 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 21 19:06:18 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CVw6M-0002zZ-00 for ; Sun, 21 Nov 2004 19:06:18 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVwFM-0000aw-Kf for ged-emacs-devel@m.gmane.org; Sun, 21 Nov 2004 13:15:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CVwF2-0000ZG-RT for emacs-devel@gnu.org; Sun, 21 Nov 2004 13:15:16 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CVwF2-0000Yv-8H for emacs-devel@gnu.org; Sun, 21 Nov 2004 13:15:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVwF2-0000Ym-4z for emacs-devel@gnu.org; Sun, 21 Nov 2004 13:15:16 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CVw5Y-0002EY-TR for emacs-devel@gnu.org; Sun, 21 Nov 2004 13:05:29 -0500 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id iALI5SFu010497; Sun, 21 Nov 2004 12:05:28 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id iALI4Oh21595; Sun, 21 Nov 2004 12:04:24 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: harald@maierh.de In-reply-to: (message from Harald Maier on Sun, 21 Nov 2004 18:38:47 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:30199 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30199 Harald Maier wrote: | There are text properties here: | font-lock-face [comint-highlight-prompt] | inhibit-line-move-field-capture t | rear-nonsticky t | fontified t | front-sticky (read-only) `---- I don't know if this is correct but it seems read-only is still there. No. The value of the _front-sticky_ property is still (read-only), which only will start to matter if you make the text read-only again. That is, the text no longer has the read-only property, but if you make it read-only, then characters added in front of it after you made it read-only will also be read-only. The above fact seems like a shortcoming of yank-excluded-properties, or of its default value. Maybe rear-nonsticky and front-sticky should be in yank-excluded-properties themselves. The text is likely to be yanked into another context and in that context, the old stickiness may no longer be desirable. Sincerely, Luc.