Re: newbie tries to hack comint.el (help!)

[Miles Bader]

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