From: Juri Linkov <juri@linkov.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 35055@debbugs.gnu.org
Subject: bug#35055: 27.0.50; async-shell-command truncates output lines
Date: Sun, 07 Apr 2019 23:15:43 +0300 [thread overview]
Message-ID: <87lg0l1syw.fsf@mail.linkov.net> (raw)
In-Reply-To: <874l7ajmnx.fsf@gmx.de> (Michael Albinus's message of "Sun, 07 Apr 2019 09:32:18 +0200")
>> One thing I still don't understand is how it would be possible
>> to do the same for the remote process?
>
> Well, don't know (yet), this needs more testing. At least, we could set
> $COLUMNS directly:
>
> (let ((default-directory "/ssh::")
> (process-environment (cons "COLUMNS=1024" process-environment)))
> (shell-command-to-string "ps aux"))
>
> (let ((default-directory "/ssh::")
> (process-environment (cons "COLUMNS=1024" process-environment)))
> (shell-command-to-string "ps aux &"))
>
> (let ((default-directory "/ssh::")
> (process-environment (cons "COLUMNS=1024" process-environment)))
> (shell))
>
> Tramp could add the $COLUMNS setting by its own. Maybe, there exist a
> more general solution, let's see.
>
> If you add "COLUMNS=1024" to tramp-remote-process-environment, you would
> get this effect already w/o any change in Tramp. Maybe I shall document
> it somewhere in the Tramp manual.
It seems it's impossible to set COLUMNS to the width of the output window
neither in Tramp nor in async-shell-command. shell-mode can do this
using set-process-window-size. But Tramp can't do the same for the
remote process, and for async-shell-command it's too late to do this
because when it displays a window with the output buffer,
the command is already finished.
next prev parent reply other threads:[~2019-04-07 20:15 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 [this message]
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
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=87lg0l1syw.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=35055@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).