bug#30213: 26.0.91; shell buffer not displayed when not erased and async-shell-command-display-buffer is used

[Basil L. Contovounesios]

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