all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Branham <alex.branham@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
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 08:53:10 -0600	[thread overview]
Message-ID: <87607s62zt.fsf@gmail.com> (raw)
In-Reply-To: <878tcpfmnz.fsf@tcd.ie>

Rebuilding Emacs from the latest commit on the emacs-26 branch seems to have solved the issue, whatever it was.

Thanks!

On Mon 22 Jan 2018 at 18:23, Basil L. Contovounesios <contovob@tcd.ie> wrote:

> 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,






  reply	other threads:[~2018-01-23 14:53 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
2018-01-23 14:53   ` Alex Branham [this message]
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=87607s62zt.fsf@gmail.com \
    --to=alex.branham@gmail.com \
    --cc=30213@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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.