From: Yuri Khan <yuri.v.khan@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: Defuns in comint
Date: Fri, 4 Oct 2024 11:40:34 +0700 [thread overview]
Message-ID: <CAP_d_8Vzo8dLxa8z9WcQ34ZZx0Qpa+trjyErq6JNnbe7eHF_Qg@mail.gmail.com> (raw)
In-Reply-To: <5DF72E31-D02C-4B4D-93A5-A04E7C372EC1@dancol.org>
On Fri, 4 Oct 2024 at 06:05, Daniel Colascione <dancol@dancol.org> wrote:
>
> How would people feel about defining defuns in comint mode as subprocesses outputs? This way, the same navigation keys people already have become more useful in comint mode without breaking anything, because defun navigation in comint is useless today.
>
> If not defuns, then paragraphs? Sentences? I feel like there should be *some* way of using existing sets of movement and marking commands to talk about outputs, and probably inputs.
Maybe pages? (Might even work out of the box if the prompt contains ^L)
next prev parent reply other threads:[~2024-10-04 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 23:04 Defuns in comint Daniel Colascione
2024-10-03 23:32 ` Jim Porter
2024-10-04 0:03 ` Daniel Colascione
2024-10-04 4:40 ` Yuri Khan [this message]
2024-10-04 4:58 ` Daniel Colascione
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=CAP_d_8Vzo8dLxa8z9WcQ34ZZx0Qpa+trjyErq6JNnbe7eHF_Qg@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=dancol@dancol.org \
--cc=emacs-devel@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.
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).