unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: jdsmith@as.arizona.edu, monnier+gnu/emacs@rum.cs.yale.edu,
	miles@lsi.nec.co.jp, simon.marshall@misys.com,
	emacs-devel@gnu.org
Subject: Re: comint read-only prompt
Date: Tue, 20 Aug 2002 13:36:28 -0500 (CDT)	[thread overview]
Message-ID: <200208201836.NAA06130@eel.dms.auburn.edu> (raw)
In-Reply-To: <200208201721.g7KHLcb09801@wijiji.santafe.edu> (message from Richard Stallman on Tue, 20 Aug 2002 11:21:38 -0600 (MDT))

Richard Stallman wrote:

   It seems rather inconsistent to me to make the newest prompt read-only
   and not the other prompts.

JD Smith wrote:

   So there are three options for old prompts:

	   1. Leave them read-only by virtue of a read-only text-property. 
	      Any attempt to kill or delete any part of the entirety of
	      older prompts generates an error.
	   2. Leave them read-only by virtue of modification and
	      insert-in-front-hooks.  Attempts to delete any part of the
	      prompts signals an error, but the entire prompt can be killed
	      without complaint.
	   3. Leave them read-write.


I believe there is one single important reason to make the latest
prompt read-only: it corresponds to the current command line.  This
reason does not apply to old prompts.

I quite often want to edit or "clean up" comint application buffers.
Option 1 forces one to play around with inhibit-read-only to
accomplish this.  Option 1 is currently implemented in ielm.  It is
extremely inconvenient.

I prefer option 3.  Option 2 might work too.

Sincerely,

Luc.

  parent reply	other threads:[~2002-08-20 18:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19  8:24 comint read-only prompt Marshall, Simon
2002-08-19 10:59 ` Miles Bader
2002-08-19 15:40   ` Stefan Monnier
2002-08-19 15:57     ` JD Smith
2002-08-19 23:45       ` Miles Bader
2002-08-20 16:14         ` Stefan Monnier
2002-08-21  0:12           ` Richard Stallman
2002-08-21 15:06             ` Stefan Monnier
2002-08-21  0:11         ` Richard Stallman
2002-08-20 17:21       ` Richard Stallman
2002-08-20 18:03         ` JD Smith
2002-08-20 21:17           ` Miles Bader
2002-08-20 22:01             ` JD Smith
2002-08-21  0:18               ` Miles Bader
2002-08-21  1:24                 ` JD Smith
2002-08-21  1:36                   ` Miles Bader
2002-08-21 15:28                     ` Stefan Monnier
2002-08-20 18:36         ` Luc Teirlinck [this message]
2002-08-20 21:12         ` Miles Bader
2002-08-20 23:23           ` Kim F. Storm
2002-08-21 11:05         ` Kai Großjohann
2002-08-22  1:57           ` Richard Stallman
2002-08-22  2:21             ` JD Smith
2002-08-22  2:35             ` Miles Bader
2002-08-24  2:33               ` Richard Stallman
2002-08-19 23:41     ` Miles Bader
2002-08-19 20:46 ` Richard Stallman
2002-08-21  0:23   ` Noah Friedman
2002-08-21  1:21     ` Miles Bader
2002-08-21  1:38       ` Miles Bader
2002-08-21  1:32     ` JD Smith
2002-08-21 15:23       ` Stefan Monnier
2002-08-22  1:21         ` Miles Bader
2002-08-22  7:57         ` Eli Zaretskii
2002-08-24  2:32           ` Richard Stallman
2002-08-21  0:23   ` Noah Friedman

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=200208201836.NAA06130@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jdsmith@as.arizona.edu \
    --cc=miles@lsi.nec.co.jp \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=simon.marshall@misys.com \
    /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).