[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#39067: shell-command-dont-erase-buffer strange behaviour
From: |
Michael Albinus |
Subject: |
bug#39067: shell-command-dont-erase-buffer strange behaviour |
Date: |
Sat, 11 Jan 2020 10:57:20 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
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.
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Madhu, 2020/01/10
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Eli Zaretskii, 2020/01/11
- bug#39067: shell-command-dont-erase-buffer strange behaviour,
Michael Albinus <=
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Tino Calancha, 2020/01/13
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Michael Albinus, 2020/01/14
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Tino Calancha, 2020/01/19
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Glenn Morris, 2020/01/19
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Tino Calancha, 2020/01/19
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Eli Zaretskii, 2020/01/19
- bug#39067: shell-command-dont-erase-buffer strange behaviour, Tino Calancha, 2020/01/20
bug#39067: shell-command-dont-erase-buffer strange behaviour, Mattias EngdegÄrd, 2020/01/20