From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rfrancoise@debian.org, 7513@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#7513: 24.0.50; shell-command-default-error-buffer should always append to the bottom
Date: Thu, 22 Aug 2019 17:07:19 +0300 [thread overview]
Message-ID: <83a7c1cmzs.fsf@gnu.org> (raw)
In-Reply-To: <877e76w4wf.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Wed, 21 Aug 2019 15:05:36 -0700)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 21 Aug 2019 15:05:36 -0700
> Cc: rfrancoise@debian.org, 7513@debbugs.gnu.org
>
> I looked at the commit history, and it doesn't seem to explain why we
> don't just append:
>
> commit cc039f78e544719115e277364378c217156c958f
> Author: Karl Heuer <kwzh@gnu.org>
> Date: Mon Mar 1 03:19:32 1999 +0000
>
> (shell-command-default-error-buffer): Renamed from
> shell-command-on-region-default-error-buffer.
> (shell-command-on-region): Mention in echo area when there
> is some error output. Mention success or failure, too.
> Accumulate multiple error outputs
> going forward, with formfeed in between. Display the error buffer
> when we have put something in it.
>
> Does anybody object to rewriting it to just append the error messages to
> the end of the buffer?
I'm not sure I understand: you want to lose the ^L separators? Or
something else?
next prev parent reply other threads:[~2019-08-22 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 18:39 bug#7513: 24.0.50; shell-command-default-error-buffer should always append to the bottom jidanni
2019-08-21 22:05 ` Lars Ingebrigtsen
2019-08-22 14:07 ` Eli Zaretskii [this message]
2019-08-22 21:18 ` 積丹尼 Dan Jacobson
2019-08-23 0:14 ` Lars Ingebrigtsen
2019-08-23 7:06 ` Eli Zaretskii
2019-08-23 8:12 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a7c1cmzs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7513@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=rfrancoise@debian.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.