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:57:32 -0600 Message-ID: <874lnc62sj.fsf@gmail.com> References: <87a7x5ejsu.fsf@gmail.com> <878tcpfmnz.fsf@tcd.ie> <87607s62zt.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1516719530 9822 195.159.176.226 (23 Jan 2018 14:58:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 23 Jan 2018 14:58:50 +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:58:45 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 1ee028-0002CW-QL for geb-bug-gnu-emacs@m.gmane.org; Tue, 23 Jan 2018 15:58:44 +0100 Original-Received: from localhost ([::1]:33911 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ee049-0001Fz-0r for geb-bug-gnu-emacs@m.gmane.org; Tue, 23 Jan 2018 10:00:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48222) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ee01W-0007LA-Hu for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:58:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ee01S-000475-Mr for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:58:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:60109) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ee01S-00046t-J9 for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:58:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ee01S-0007R6-Bm for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2018 09:58:02 -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:58:02 +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.151671947328569 (code B ref 30213); Tue, 23 Jan 2018 14:58:02 +0000 Original-Received: (at 30213) by debbugs.gnu.org; 23 Jan 2018 14:57:53 +0000 Original-Received: from localhost ([127.0.0.1]:39773 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ee01J-0007Qj-04 for submit@debbugs.gnu.org; Tue, 23 Jan 2018 09:57:53 -0500 Original-Received: from mail-oi0-f50.google.com ([209.85.218.50]:38283) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ee01I-0007QS-3M for 30213@debbugs.gnu.org; Tue, 23 Jan 2018 09:57:52 -0500 Original-Received: by mail-oi0-f50.google.com with SMTP id m65so505570oig.5 for <30213@debbugs.gnu.org>; Tue, 23 Jan 2018 06:57:51 -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=FsZVmpojGnvARSXJpDJ7nV5dUkJ0JB3k84Il8HXS7n4=; b=Q5YLVu02Tpcq6r6nbejtbNt3P72fhV+wmLtNBZ81SVL3nJZjqyXFVjAe6zq5CP/cPH B/rUA9XwROdQxPwe4dVKsBdmGjZM05+BVXSMmn/CVDfn3Bc0BipyOUo/Q/G1I+wwWHya 7IiRKm1Noaa6WDPztoqHSGAsRp1fZOXAv9FjeQpZaTWbLGl5Qkjo8xki4UNIQIrNk/5R Q8nl5o3fL9C9k9YDUf1k4JvnjpyL3NCqZtnq30OVQjZb7283N/ga73ZENGRZYXdsFaO+ DkW0g2DvDJiHzSRnR3Jt2NokFlznnL+1gLAURrna5CHmCT6qNR7zX+58Xz9eiiG9l6GL vwPw== 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=FsZVmpojGnvARSXJpDJ7nV5dUkJ0JB3k84Il8HXS7n4=; b=bVakkJgPW0xICh1lcE/1qgGObIjE4uaHc/tW/NLayjeLFo2YqJF0K/HAo4YsG4AvIs iMeK27u9deGJQKEcuqPYfx92jb2s+KHffc0iH6pmA4xjJ13PA12C57TiB+UjBJYytWKj HSIR9GCiITLr1E47yaV6XzziaWxdNVtV3Fg06GChhFd1CJweejRYTdQBg7oD9dMKRD0w UyKzC3FsioWuaSd+Ou1Ss4m0oDqb70v7PQxiTpC9e1XtLZAqc/js2ogOk+7yS9o/+uh1 k2PZhcvucAOEWd+VaqrJsxHXEnpQhN41F/iDAz1HfdXCLhEpev6V1b8vZFxOl/q2AvAV zzig== X-Gm-Message-State: AKwxyteHWhflR9NUn68q8J6AAIQyT8dnQlbVHECQsWROXpB8AlMEmhE+ +HtfX37+6ea3v+z2VvjQplJs6EUd X-Google-Smtp-Source: AH8x224YCxUioXoBv+Ygdy8ctdxWB3SvoRSX26fT5PTVTG3fuFsjLqK8Aq0c3Pel4+twIVpa7xCPVA== X-Received: by 10.202.81.215 with SMTP id f206mr5541888oib.310.1516719466105; Tue, 23 Jan 2018 06:57:46 -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 39sm202501otr.47.2018.01.23.06.57.41 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 23 Jan 2018 06:57:45 -0800 (PST) In-reply-to: <87607s62zt.fsf@gmail.com> 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:142428 Archived-At: I'm sorry, haven't had my morning coffee yet. I can reproduce this, but there was an error in my initial email. From emacs -Q (setq shell-command-dont-erase-buffer 'beg-last-out async-shell-command-display-buffer nil) then do an async shell command, delete the window that shows the output, then call another async shell command. The window is never re-shown. Alex On Tue 23 Jan 2018 at 08:53, Alex Branham wrote: > 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,