From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#71554: 29.3; eshell-command async buffer behavior Date: Fri, 14 Jun 2024 21:56:50 +0300 Message-ID: <86tthvwdxp.fsf@gnu.org> References: <87frtfpqyn.fsf@librehacker.com> <87ikyb8igc.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33088"; mail-complaints-to="usenet@ciao.gmane.io" Cc: christopher@librehacker.com, 71554@debbugs.gnu.org To: Thierry Volpiatto Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jun 14 21:00:35 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sICA6-0008Ps-2R for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 14 Jun 2024 21:00:34 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sIC9c-0006lK-IG; Fri, 14 Jun 2024 15:00:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sIC9a-0006kp-NO for bug-gnu-emacs@gnu.org; Fri, 14 Jun 2024 15:00:02 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sIC9a-0004nw-Da for bug-gnu-emacs@gnu.org; Fri, 14 Jun 2024 15:00:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sIC9a-0006DR-Kz for bug-gnu-emacs@gnu.org; Fri, 14 Jun 2024 15:00:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 14 Jun 2024 19:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71554 X-GNU-PR-Package: emacs Original-Received: via spool by 71554-submit@debbugs.gnu.org id=B71554.171839155223799 (code B ref 71554); Fri, 14 Jun 2024 19:00:02 +0000 Original-Received: (at 71554) by debbugs.gnu.org; 14 Jun 2024 18:59:12 +0000 Original-Received: from localhost ([127.0.0.1]:40959 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sIC8l-0006Bm-HZ for submit@debbugs.gnu.org; Fri, 14 Jun 2024 14:59:11 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:50390) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sIC8i-0006BZ-Ov for 71554@debbugs.gnu.org; Fri, 14 Jun 2024 14:59:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sIC6W-0004Y6-Ay; Fri, 14 Jun 2024 14:56:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=86KK7GowYJPNgoDOrxystMN3NnbX+HqupVdyrb8+jPk=; b=Cz09Oylj/18M vCs0qK50G02ZQmsW5XOyxIqBxw2bfBtYjWXy2LnYWuGGfeF3RZ2kgymqbRiO5huD0oYecRGekzeHB KsJvoEskUxIbBvV22voiO1S/AACRXlwLwASc1CpXOWMfEJGqA53vrPu8LIiINhxcBUNqgA/hmvyBW Qe1weyvwSuz/QwHQAIxu3wKY4HnEftjr5kzV5KfzOJDGio//HOrUub0WqZGTDu6+uZ9aren8Xy4ub aH3W6/TgPU0qAFDqhb+xg3u6Qt9RGkXeds2ziQK6dQEoZhnnGebuTFb613FMQaSDg2bbCaLORJwsi 8Kj2MClwyIJujAm675NI0w==; In-Reply-To: <87ikyb8igc.fsf@posteo.net> (message from Thierry Volpiatto on Fri, 14 Jun 2024 18:53:07 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:287243 Archived-At: > Cc: 71554@debbugs.gnu.org > From: Thierry Volpiatto > Date: Fri, 14 Jun 2024 18:53:07 +0000 > > Christopher Howard writes: > > > Hello, I run a lot of async commands a lot with eshell-command, > > preferring it over shell-command. However, there is a difference > > between shell-command and eshell-command behavior which is a little > > bothersome and does not make sense to me. If I run an async command > > with shell-command, e.g. `sleep 60 &', and then run another one while > > the first one is still running, shell-command will ask me if I want to > > create a new buffer for the output, and I usually do. However, if I do > > the same thing with eshell-command, eshell command will give me only > > two options, either (1) kill the currently running command, or (2) > > don't create an output buffer, which also throws an error. I was > > wondering if it would be possible to add the "create a new buffer" > > option to eshell-command as well, for the upcoming 30 release. > > Please do not add a "ask to create a new buffer" option to fix this > issue, just do not ask and create a new buffer What if the user is not aware that a command is already running? More generally, why being consistent with what shell-command does is not a good idea?