From: Miles Bader <miles@gnu.org>
Subject: Re: newbie tries to hack comint.el (help!)
Date: Wed, 09 Jun 2004 07:24:43 +0900 [thread overview]
Message-ID: <87oentd6xg.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: 40C5ECBD.4080903@yahoo.com
Kevin Rodgers <ihs_4664@yahoo.com> writes:
> > Note that comint _does not know_ (and cannot know) the difference
> > between "myhost: ~ ...$ " and "> " -- it can't tell when your input
> > causes a process to run in the shell, it just sees the input and output.
> > comint-prompt-regexp is probably not useful because it is designed to
> > match most prompts, and that includes "> ".
>
> But doesn't comint or process-mark keep track of where the previous
> command's output ended? You should be able to search forward from there
> to the next matching prompt.
Note that prompts are output -- in this example "> " is the `commands's
most recent output.'
-Miles
--
Love is a snowmobile racing across the tundra. Suddenly it flips over,
pinning you underneath. At night the ice weasels come. --Nietzsche
prev parent reply other threads:[~2004-06-08 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ca2ctl$6ta$1@reader2.panix.com>
[not found] ` <877jujt2bx.fsf@tc-1-100.kawasaki.gol.ne.jp>
2004-06-08 11:34 ` newbie tries to hack comint.el (help!) bill
2004-06-08 22:23 ` Miles Bader
2004-06-08 16:43 ` Kevin Rodgers
2004-06-08 22:24 ` Miles Bader [this message]
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=87oentd6xg.fsf@tc-1-100.kawasaki.gol.ne.jp \
--to=miles@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.
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).