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 read-only-prompt
Date: Tue, 7 Jun 2005 12:38:46 -0500 (CDT)	[thread overview]
Message-ID: <200506071738.j57Hckj19457@raven.dms.auburn.edu> (raw)
In-Reply-To: <pan.2005.06.07.16.36.57.721232@as.arizona.edu> (message from JD Smith on Tue, 07 Jun 2005 09:36:58 -0700)

JD Smith wrote:

   I just compiled a CVS Emacs v22, and was pleased to find that there is
   a new comint- prompt-read-only variable.  However, when I enable that
   variable, I get the following non-desired behavior:

	1. At each prompt, I am warned "Text is read-only".
	2. All my input is echoed back to me (I use process-echoes).  

   I thought my prompt pattern could be at fault; it contains a \r
   character (which IDL throws in at odd intervals).  I changed it to
   something simple, and get the same behavior.

Unless you set comint-use-prompt-regexp (formerly
comint-use-prompt-regexp-instead-of-fields) to t, the value of
shell-prompt-pattern will not matter very much.  It looks like part of
the echoed input is considered part of the prompt.  The prompt
read-only region includes the prompt and the newline before it.

It is really difficult for me to look into this, because I can not
duplicate the problem.  Trying to use idlwave-shell-mode (assuming
that is what we are talking about) I got:

apply: Searching for program: no such file or directory, idl

Sincerely,

Luc.

  reply	other threads:[~2005-06-07 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 16:36 Comint read-only-prompt JD Smith
2005-06-07 17:38 ` Luc Teirlinck [this message]
2005-06-07 20:59   ` JD Smith
2005-06-07 21:28     ` Luc Teirlinck
2005-06-07 22:10       ` JD Smith
2005-06-07 22:25         ` Luc Teirlinck
2005-06-07 23:53         ` Luc Teirlinck
2005-06-08  1:29           ` JD Smith
2005-06-08 16:06           ` Stefan Monnier

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=200506071738.j57Hckj19457@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).