From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: comint-prompt-regexp
Date: Wed, 6 Apr 2005 20:55:11 -0500 (CDT) [thread overview]
Message-ID: <200504070155.j371tBq27411@raven.dms.auburn.edu> (raw)
I propose the following doc change to comint.el. The reasons are
the same as for the similar change I proposed to the
shell-prompt-pattern docstring. I know of at least two modes, shell
and ielm, that use `comint-prompt-regexp' even if
`comint-use-prompt-regexp-instead-of-fields' is nil.
===File ~/comint-diff=======================================
*** comint.el 04 Apr 2005 19:34:31 -0500 1.310
--- comint.el 06 Apr 2005 20:34:18 -0500
***************
*** 158,165 ****
"Regexp to recognise prompts in the inferior process.
Defaults to \"^\", the null string at BOL.
! This variable is only used if the variable
! `comint-use-prompt-regexp-instead-of-fields' is non-nil.
Good choices:
Canonical Lisp: \"^[^> \\n]*>+:? *\" (Lucid, franz, kcl, T, cscheme, oaklisp)
--- 158,166 ----
"Regexp to recognise prompts in the inferior process.
Defaults to \"^\", the null string at BOL.
! If `comint-use-prompt-regexp-instead-of-fields' is nil, Comint
! completely ignores this variable. However, some derived modes
! may still use it, for instance, to delimit paragraphs.
Good choices:
Canonical Lisp: \"^[^> \\n]*>+:? *\" (Lucid, franz, kcl, T, cscheme, oaklisp)
============================================================
next reply other threads:[~2005-04-07 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 1:55 Luc Teirlinck [this message]
2005-04-07 3:24 ` comint-prompt-regexp Miles Bader
2005-04-08 1:05 ` comint-prompt-regexp Luc Teirlinck
2005-04-08 1:36 ` comint-prompt-regexp Miles Bader
2005-04-08 1:46 ` comint-prompt-regexp Luc Teirlinck
2005-04-08 1:27 ` comint-prompt-regexp Luc Teirlinck
2005-04-08 1:34 ` comint-prompt-regexp Luc Teirlinck
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=200504070155.j371tBq27411@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
/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).