From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Alex Branham <alex.branham@gmail.com>
Cc: 30213@debbugs.gnu.org
Subject: bug#30213: 26.0.91; shell buffer not displayed when not erased and async-shell-command-display-buffer is used
Date: Tue, 23 Jan 2018 00:23:28 +0000 [thread overview]
Message-ID: <878tcpfmnz.fsf@tcd.ie> (raw)
In-Reply-To: <87a7x5ejsu.fsf@gmail.com> (Alex Branham's message of "Mon, 22 Jan 2018 14:10:41 -0600")
Alex Branham <alex.branham@gmail.com> writes:
> With async-shell-command-display-buffer set to t and
> shell-command-dont-erase-buffer set to 'beg-last-output, async shell
> buffers do not get displayed after the second async call, presumably
> because the buffer doesn't get erased so there isn't a first line
> written.
Just to clarify: are you setting shell-command-dont-erase-buffer to
beg-last-output or beg-last-out? The former isn't a valid value for
this user option.
Either way, I cannot reproduce what I think you are doing in a build of
today's master branch, but I think it would help if you listed the
precise steps leading to the output buffer failing to display.
Thanks,
--
Basil
next prev parent reply other threads:[~2018-01-23 0:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 20:10 bug#30213: 26.0.91; shell buffer not displayed when not erased and async-shell-command-display-buffer is used Alex Branham
2018-01-23 0:23 ` Basil L. Contovounesios [this message]
2018-01-23 14:53 ` Alex Branham
2018-01-23 14:57 ` Alex Branham
2018-01-23 18:53 ` Basil L. Contovounesios
2018-01-23 19:07 ` Alex Branham
2018-01-23 19:30 ` Eli Zaretskii
2018-01-23 22:44 ` Basil L. Contovounesios
2018-02-03 21:31 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tcpfmnz.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=30213@debbugs.gnu.org \
--cc=alex.branham@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.