From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alex Branham Newsgroups: gmane.emacs.bugs 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 Message-ID: <87607s62zt.fsf@gmail.com> References: <87a7x5ejsu.fsf@gmail.com> <878tcpfmnz.fsf@tcd.ie> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1516719375 8314 195.159.176.226 (23 Jan 2018 14:56:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 23 Jan 2018 14:56:15 +0000 (UTC) User-Agent: mu4e 0.9.18; emacs 26.0.91 Cc: 30213@debbugs.gnu.org To: "Basil L. Contovounesios" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jan 23 15:56:11 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1edzz9-0008V1-Oc for geb-bug-gnu-emacs@m.gmane.org; Tue, 23 Jan 2018 15:55:39 +0100 Original-Received: from localhost ([::1]:33710 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ee01A-0006np-5D for geb-bug-gnu-emacs@m.gmane.org; Tue, 23 Jan 2018 09:57:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45983) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edzxe-0003k7-6A for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:54:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edzxa-0008F0-8x for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:54:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:59585) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1edzxa-0008Ei-54 for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:54:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1edzxZ-0007Dm-Jj for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:54:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Alex Branham Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 23 Jan 2018 14:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30213 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30213-submit@debbugs.gnu.org id=B30213.151671921327723 (code B ref 30213); Tue, 23 Jan 2018 14:54:01 +0000 Original-Received: (at 30213) by debbugs.gnu.org; 23 Jan 2018 14:53:33 +0000 Original-Received: from localhost ([127.0.0.1]:39249 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1edzx7-0007D5-Dw for submit@debbugs.gnu.org; Tue, 23 Jan 2018 09:53:33 -0500 Original-Received: from mail-ot0-f170.google.com ([74.125.82.170]:46539) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1edzx5-0007Cq-Ke for 30213@debbugs.gnu.org; Tue, 23 Jan 2018 09:53:31 -0500 Original-Received: by mail-ot0-f170.google.com with SMTP id t35so607622otd.13 for <30213@debbugs.gnu.org>; Tue, 23 Jan 2018 06:53:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=lmo34/nBOOR58BEozbzCmmSEWgGgstv/d6lK1pqNm10=; b=h4sI9ZQkSO0qo/gYkQfIt/w+tE9k+E036BiQtoQL40zzVhhmhPuRNumUYMJ0fFN3MW A4kYY2Kbsqv9UPmZOJ3Z3YwXiyIyk5QYwKs2FnLeG6ZcAx6qlhV2FX/KnyA5yUo6ONap o9zYzbfoSIBU8BA2N7t9Q6+OptN7hdBEjURjn99qZFAcOqKzcevuGD1x0AAzgiZYY5aw vWmwreYcdvSgFbrDlj23BIcRpY6PnhIWwzXp3C8fI55NWyHjID9BJpTPdAuIhJKyzjbV VNEvZ7axq8uXErxCMHv3BfRVGS+ZEY0kVAQIa+CnbbBbAZ9k9BlDKkdS95c6B/kB4N8U PkBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=lmo34/nBOOR58BEozbzCmmSEWgGgstv/d6lK1pqNm10=; b=EO1MmnhXL3D2DPZ+Y8tFZ8CCUf7QzxkrsJC0bqsy+Do0s2a8S5gTbnsdBSqs1LfDmk LxF/3NYiyxMFuulkQj8daERkonSs+81+FUTsUXMzf2zSVtvZ4H6LEzgi5L/LcPYSnL41 JneiBeduCuvVJFSFpZudpXvHgtnNiY7GytVlLNcaizTcuTwoEMEwX/qhPoOjfoqhyW1a T1TCUPhxOczGH131h8eivbTqveIX2dBccKtni4IBP9icE/fXrO/9yPLUb/AUBUXUBRE0 FBl5qcQ1EF07l2KWRUaJsBKS7hHXlxW4f1Bjm7zTB+7VMCwjYDfUpaEUwumrJ9NUHXGL Asxw== X-Gm-Message-State: AKwxytd7aNiO2dlyd8QBL7Rk4iDIdiKTG0SXkUB3krS3LUhJov3IvEs2 +Q/FCKcKLd5c+9eI1uA8W/gxnwui X-Google-Smtp-Source: AH8x226jcPv/vQXtaSpRMrIaK0q8qOyd3HqAFSHL5VkZLO6RyYDZe477pUm0geQIQiaNRyG9NLgCzQ== X-Received: by 10.157.80.171 with SMTP id b43mr7382233oth.134.1516719205646; Tue, 23 Jan 2018 06:53:25 -0800 (PST) Original-Received: from earth (cpe-70-114-192-208.austin.res.rr.com. [70.114.192.208]) by smtp.gmail.com with ESMTPSA id d134sm1218081oih.5.2018.01.23.06.53.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 23 Jan 2018 06:53:25 -0800 (PST) In-reply-to: <878tcpfmnz.fsf@tcd.ie> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:142427 Archived-At: 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 wrote: > Alex Branham 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,