From: Michael Albinus <michael.albinus@gmx.de>
To: Juri Linkov <juri@linkov.net>
Cc: 35055@debbugs.gnu.org
Subject: bug#35055: 27.0.50; async-shell-command truncates output lines
Date: Wed, 17 Apr 2019 09:22:16 +0200 [thread overview]
Message-ID: <8736mhp047.fsf@gmx.de> (raw)
In-Reply-To: <87mukpznua.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 16 Apr 2019 23:39:41 +0300")
Juri Linkov <juri@linkov.net> writes:
Hi Juri,
>> I don't believe there is a conflict. The main use case will be to
>> increase the output width of a shell command, in order not to loose
>> information. People will do this by setting a large value, say
>> 1024. This will be used for both the synchronous and asynchronous case.
>
> The same value will increase the output width of async shell commands,
> but decrease the output width of synchronous shell commands from unlimited.
Yes. You must set a proper value, large enough.
>> And then there's the use case to have a fixed output width for special
>> commands, in order to get a deterministic layout. This won't be applied
>> globally, neither for synchronous nor for asynchronous
>> `shell-command'. Rather, `shell-command-width' will be let-bound.
>>
>> And we have the advantage, that synchronous `shell-command' behaves
>> consistently, for both the local and remote case.
>>
>> So I don't see a problem.
>
> If output truncation will apply to shell-command-on-region,
> especially with its REPLACE arg, this would be a big problem.
> After filtering the buffer contents with a shell command,
> parts of the buffer will be lost.
No. You can always undo the effect on buffer.
Best regards, Michael.
next prev parent reply other threads:[~2019-04-17 7:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 21:55 bug#35055: 27.0.50; async-shell-command truncates output lines Juri Linkov
2019-04-01 10:00 ` Michael Albinus
2019-04-01 20:44 ` Juri Linkov
2019-04-02 9:27 ` Michael Albinus
2019-04-03 20:36 ` Juri Linkov
2019-04-04 20:59 ` Juri Linkov
2019-04-05 12:35 ` Michael Albinus
2019-04-06 20:47 ` Juri Linkov
2019-04-07 7:32 ` Michael Albinus
2019-04-07 20:15 ` Juri Linkov
2019-04-08 7:39 ` Michael Albinus
2019-04-08 20:23 ` Juri Linkov
2019-04-13 10:45 ` Michael Albinus
2019-04-13 21:48 ` Juri Linkov
2019-04-14 17:55 ` Michael Albinus
2019-04-14 19:41 ` Juri Linkov
2019-04-15 7:47 ` Michael Albinus
2019-04-16 20:39 ` Juri Linkov
2019-04-17 7:22 ` Michael Albinus [this message]
2019-04-17 20:13 ` Juri Linkov
2019-04-18 7:40 ` Michael Albinus
2019-04-18 20:51 ` Juri Linkov
2019-04-19 7:21 ` Michael Albinus
2019-04-30 21:17 ` Michael Albinus
2019-05-01 21:07 ` Juri Linkov
2019-05-02 9:02 ` Michael Albinus
2019-05-02 20:57 ` Juri Linkov
2019-05-03 7:20 ` Michael Albinus
2019-05-05 19:27 ` Juri Linkov
2019-05-06 9:28 ` Michael Albinus
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=8736mhp047.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=35055@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).