From: Bob Rogers <rogers@rgrjr.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61069@debbugs.gnu.org
Subject: bug#61069: 30.0.50; comint-copy-old-input should include continuation lines
Date: Thu, 26 Jan 2023 00:38:56 -0800 [thread overview]
Message-ID: <25554.15392.580428.54160@orion.rgrjr.com> (raw)
In-Reply-To: <83o7qlemta.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
Date: Thu, 26 Jan 2023 10:12:49 +0200
> From: Bob Rogers <rogers@rgrjr.com>
> Date: Wed, 25 Jan 2023 23:33:42 -0800
> Cc: 61069@debbugs.gnu.org
> Here's an example from building emacs:
>
> . . .
> rm -f emacs && cp -f temacs emacs
> LC_ALL=C ./temacs -batch -l loadup --temacs=pdump \
> --bin-dest /usr/local/bin/ --eln-dest /usr/local/lib64/emacs/30.0.50/
> Loading loadup.el (source)...
> Dump mode: pdump
> . . .
Oh, you mean the backslashes that come from the Makefile itself, like
the one after "=pdump"?
Exactly.
> My thought is that C-RET on the "./temacs -batch" line in a *shell*
> buffer should take both that line and the next.
That has to be an optional feature, probably off by default.
As you like. Should this be a comint thing, or a shell thing?
-- Bob
next prev parent reply other threads:[~2023-01-26 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 1:43 bug#61069: 30.0.50; comint-copy-old-input should include continuation lines Bob Rogers
2023-01-26 7:04 ` Eli Zaretskii
2023-01-26 7:33 ` Bob Rogers
2023-01-26 8:12 ` Eli Zaretskii
2023-01-26 8:38 ` Bob Rogers [this message]
2023-01-26 9:32 ` Eli Zaretskii
2023-01-28 3:45 ` Bob Rogers
2023-01-30 8:25 ` Robert Pluim
2023-01-30 21:05 ` Bob Rogers
2023-01-31 2:38 ` Bob Rogers
2023-01-31 9:10 ` Robert Pluim
2023-01-31 19:45 ` Bob Rogers
2023-03-30 19:51 ` Bob Rogers
2023-03-31 8:07 ` Robert Pluim
2023-03-31 10:51 ` Eli Zaretskii
2023-03-31 13:01 ` Robert Pluim
2023-03-31 13:23 ` Robert Pluim
2023-04-01 0:15 ` Bob Rogers
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=25554.15392.580428.54160@orion.rgrjr.com \
--to=rogers@rgrjr.com \
--cc=61069@debbugs.gnu.org \
--cc=eliz@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).