From: tomas@tuxteam.de
To: Glenn Morris <rgm@gnu.org>
Cc: 5618@debbugs.gnu.org, rfrancoise@debian.org
Subject: bug#5618: 23.1.91; shell-command-on-region unexpectedly erases buffer
Date: Wed, 24 Feb 2010 06:58:29 +0100 [thread overview]
Message-ID: <20100224055829.GA9795@tomas> (raw)
In-Reply-To: <ew635nx1sq.fsf@fencepost.gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks, Glenn for looking into it.
On Tue, Feb 23, 2010 at 01:08:37PM -0500, Glenn Morris wrote:
> tomas@tuxteam.de wrote:
>
> > The whole content of the buffer gets replaced by output of
> > command. According to the doc, I'd expect the ouput to be inserted
> > before point.
>
> I guess this is a documentation bug, in the same way as was
>
> http://debbugs.gnu.org/4891
Yes, I think it's the same "bug". Now if I knew how to merge that...
> I'm not sure that the installed doc fix for that bug is actually
> correct. The suggestion in
>
> http://debbugs.gnu.org/4891#10
Except that in our case, even if it's the current buffer, the whole
content of the buffer is overwritten as well, rendering the above
mentioned doc fix incorrect:
"If OUTPUT-BUFFER is not a buffer and not nil,
insert output in current buffer. (This cannot be done
asynchronously.) In the latter case, the output is inserted
after point (leaving mark after it)"
Besides, the behaviour in the current documentation seems way more
useful (i.e. _not_ erasing the buffer whenever REPLACE is non-nil).
What do you think?
> seems correct to me.
Half of it, yes, see above.
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFLhMAFBcgs9XrR2kYRAghcAJ97B90JiuOcu8Ck+Yt0iCPtRQcw1gCePIY8
XYLgohnxDDQjrsn1OPJf6mY=
=4Z+h
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-24 5:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 9:44 bug#5618: 23.1.91; shell-command-on-region unexpectedly erases buffer tomas
2010-02-23 18:08 ` Glenn Morris
2010-02-24 5:58 ` tomas [this message]
2010-02-26 9:17 ` Juri Linkov
2010-02-26 10:12 ` tomas
2010-03-06 17:34 ` Stefan Monnier
2022-01-27 18:31 ` 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
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=20100224055829.GA9795@tomas \
--to=tomas@tuxteam.de \
--cc=5618@debbugs.gnu.org \
--cc=rfrancoise@debian.org \
--cc=rgm@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).