From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#61069: 30.0.50; comint-copy-old-input should include continuation lines Date: Thu, 26 Jan 2023 10:12:49 +0200 Message-ID: <83o7qlemta.fsf@gnu.org> References: <25553.55974.767552.842578@orion.rgrjr.com> <834jsdg4jh.fsf@gnu.org> <25554.11478.609268.317183@orion.rgrjr.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34643"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 61069@debbugs.gnu.org To: Bob Rogers Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jan 26 09:13:13 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pKxNg-0008on-CJ for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 26 Jan 2023 09:13:12 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pKxNY-0002GE-HR; Thu, 26 Jan 2023 03:13:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pKxNW-0002Fi-Ry for bug-gnu-emacs@gnu.org; Thu, 26 Jan 2023 03:13:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pKxNW-0004iV-Jm for bug-gnu-emacs@gnu.org; Thu, 26 Jan 2023 03:13:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pKxNW-0006Rm-Eh for bug-gnu-emacs@gnu.org; Thu, 26 Jan 2023 03:13:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 26 Jan 2023 08:13:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61069 X-GNU-PR-Package: emacs Original-Received: via spool by 61069-submit@debbugs.gnu.org id=B61069.167472076124748 (code B ref 61069); Thu, 26 Jan 2023 08:13:02 +0000 Original-Received: (at 61069) by debbugs.gnu.org; 26 Jan 2023 08:12:41 +0000 Original-Received: from localhost ([127.0.0.1]:60597 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pKxNA-0006R4-VH for submit@debbugs.gnu.org; Thu, 26 Jan 2023 03:12:41 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38220) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pKxN9-0006Qr-Ci for 61069@debbugs.gnu.org; Thu, 26 Jan 2023 03:12:39 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pKxN3-0004eb-JJ; Thu, 26 Jan 2023 03:12:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=KnV2XRMN4vpGvE3g3dKID0TMwO2036r4RREkYyhFh1k=; b=KPnkaUrG2fLU lA6m90+Nv9RFOMLQ94HgEGr16dIDR4jaVBG3PUTmdGlE+HKMW+pVnjevR9g5PYurO8rEjOZ1WZ+uw 4sM2dbA2GlKklIJc47jovq7M1jbZ6/gO1y+7e8r8rkiFhCch/stIm1ox3QemiyhvdhtXX4VF16r8g 708kvrdhL22FyWn16pGMFXrRPNnddEjF0h3BJVpi0zBa4UNgiLyNzxg8nHgS0fBDlfN9qlUIDj/fp 76OZYvFRxDEJgExJ8UYOK2tcRhN4ueg8Y0HrjtcNdHXOhp3e9h5jnVIg5T1dpLyNPDAxR8uh7ZDpa TPCBo+VxKufTx1fdgm0lkw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pKxN3-0005uc-3L; Thu, 26 Jan 2023 03:12:33 -0500 In-Reply-To: <25554.11478.609268.317183@orion.rgrjr.com> (message from Bob Rogers on Wed, 25 Jan 2023 23:33:42 -0800) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:254192 Archived-At: > From: Bob Rogers > Date: Wed, 25 Jan 2023 23:33:42 -0800 > Cc: 61069@debbugs.gnu.org > > Or maybe I don't understand what is this "backslash" business is > about? AFAICT, the "backslashes" shown for long lines of Make output > are those produced by the Emacs display, not by the shell, so the code > you want to change should already take care of that. > > What am I missing? Could you please show an example of "long Make > output" where the current code doesn't DTRT, so we'd be on the same > page wrt the problem? > > Thanks. > > 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"? > 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.