[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comint read-only prompt
From: |
Stefan Monnier |
Subject: |
Re: comint read-only prompt |
Date: |
Wed, 21 Aug 2002 11:28:27 -0400 |
> > A proposed solution: if snapshot were moved to the beginning of the
> > output-filter, these problems would disappear.
>
> That would be completely wrong. The reason why `prompt snapshotting'
> is done when the user sends input is because that's the only time you
> can be pretty sure that what the overlay covers is _actually_ a prompt.
I think what he was suggesting is:
- comint-send-string sets the overlay's `snapshot' property.
- comint's output filter checks the `snapshot' property to determine
whether to call comint-snapshot-last-prompt or to just move
the overlay.
But it seems that it's much simpler to just use process-send-string.
Maybe comint-send-string's docstring could be a bit more forthcoming about
what it means by "extra bookkeeping" so that authors can make a better
informed choice between the two functions.
Stefan
- Re: comint read-only prompt, (continued)
- Re: comint read-only prompt, Richard Stallman, 2002/08/20
- Re: comint read-only prompt, JD Smith, 2002/08/20
- Message not available
- Re: comint read-only prompt, JD Smith, 2002/08/20
- Message not available
- Re: comint read-only prompt, JD Smith, 2002/08/20
- Re: comint read-only prompt, Miles Bader, 2002/08/20
- Re: comint read-only prompt,
Stefan Monnier <=
- Re: comint read-only prompt, Luc Teirlinck, 2002/08/20
- Message not available
- Re: comint read-only prompt, Kim F. Storm, 2002/08/20
- Re: comint read-only prompt, Kai Großjohann, 2002/08/21
- Re: comint read-only prompt, Richard Stallman, 2002/08/21
- Re: comint read-only prompt, JD Smith, 2002/08/21
- Re: comint read-only prompt, Miles Bader, 2002/08/21
- Re: comint read-only prompt, Richard Stallman, 2002/08/23
- Message not available
- Re: comint read-only prompt, Richard Stallman, 2002/08/20
Re: comint read-only prompt, Richard Stallman, 2002/08/19