From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39067@debbugs.gnu.org, Madhu <madhu@cs.unm.edu>,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#39067: shell-command-dont-erase-buffer strange behaviour
Date: Sat, 11 Jan 2020 10:57:20 +0100 [thread overview]
Message-ID: <87d0bqgvsv.fsf@gmx.de> (raw)
In-Reply-To: <834kx28hvl.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 Jan 2020 11:25:18 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> IOW, this feature is not working as advertised in several important
> use case, and never did AFAICT. Its implementation is incomplete.
Test cases for this (and other shell-command functionality) would also
be appreciated.
FTR, Tramp ignores this variable completely. Once it is fixed in
shell-command, we might want to fix it also for Tramp.
The current implementation in simple.el uses
shell-command--save-pos-or-erase and shell-command--set-point-after-cmd,
both are internal functions. Could we make them first class citizens,
that Tramp could profit from?
> Thanks.
Best regards, Michael.
next prev parent reply other threads:[~2020-01-11 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 5:34 bug#39067: shell-command-dont-erase-buffer strange behaviour Madhu
2020-01-11 9:25 ` Eli Zaretskii
2020-01-11 9:57 ` Michael Albinus [this message]
2020-01-13 20:22 ` Tino Calancha
2020-01-14 8:49 ` Michael Albinus
2020-01-19 10:19 ` Tino Calancha
2020-01-19 18:05 ` Glenn Morris
2020-01-19 20:55 ` Tino Calancha
2020-01-20 3:25 ` Eli Zaretskii
2020-01-20 13:20 ` Tino Calancha
2020-02-01 13:36 ` Michael Albinus
2020-01-20 10:04 ` Mattias Engdegård
2020-01-20 13:21 ` Tino Calancha
2020-01-20 13:30 ` Mattias Engdegård
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=87d0bqgvsv.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=39067@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=madhu@cs.unm.edu \
--cc=tino.calancha@gmail.com \
/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).