From: miha--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Hoffman <emacs-hoffman@snkmail.com>, 60244@debbugs.gnu.org
Subject: bug#60244: 27.1; term-line-mode works poorly with git progress rewriting
Date: Mon, 09 Jan 2023 19:27:05 +0100 [thread overview]
Message-ID: <87eds3a7ie.fsf@miha-pc> (raw)
In-Reply-To: <19422-1673285626-849750@sneakemail.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
"Michael Hoffman" <emacs-hoffman@snkmail.com> writes:
> Thanks so much for looking into this.
>
> On Sat, Dec 24, 2022 at 10:01 AM miha wrote:
>
> Two possible ideas to solve this:
>
> - Introduce a new marker to separate user input from process output.
>
> - Use text properties to distinguish user input from process output.
> This is what comint.el does, it marks process output with 'field' =
> 'output'.
>
> Is one of these options preferred? The second idea sounds more robust, and also it is nice that the example of comint.el
> exists for it. But perhaps I am naive about what they require.
I prefer the second option. While it is probably more work to implement
than the first one, it opens up possibilities of more robust input
navigation and multi-line input editing in term-line-mode, just like in
comint.el with 'comint-use-prompt-regexp' = nil.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2023-01-09 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 20:37 bug#60244: 27.1; term-line-mode works poorly with git progress rewriting Michael Hoffman
2022-12-21 21:58 ` Michael Hoffman
2022-12-22 6:57 ` Eli Zaretskii
2022-12-24 15:02 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-24 15:40 ` Eli Zaretskii
2023-01-09 17:33 ` Michael Hoffman
2023-01-09 18:27 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87eds3a7ie.fsf@miha-pc \
--to=bug-gnu-emacs@gnu.org \
--cc=60244@debbugs.gnu.org \
--cc=emacs-hoffman@snkmail.com \
--cc=miha@kamnitnik.top \
/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).