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#8399: 23.3; save-some-buffers ignores buffer names Date: Tue, 25 Aug 2020 17:42:26 +0300 Message-ID: <83wo1m4wj1.fsf@gnu.org> References: <83y63vm0v4.fsf@cs.bham.ac.uk> <87imd697mo.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17557"; mail-complaints-to="usenet@ciao.gmane.io" Cc: u.s.reddy@cs.bham.ac.uk, monnier@iro.umontreal.ca, 8399@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 25 16:43:09 2020 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 1kAaAH-0004OX-24 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 25 Aug 2020 16:43:09 +0200 Original-Received: from localhost ([::1]:55896 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kAaAF-0003NY-Qq for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 25 Aug 2020 10:43:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44640) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kAaAA-0003N7-8f for bug-gnu-emacs@gnu.org; Tue, 25 Aug 2020 10:43:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52307) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kAaA9-0007OQ-WC for bug-gnu-emacs@gnu.org; Tue, 25 Aug 2020 10:43:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kAaA9-0008Ri-UB for bug-gnu-emacs@gnu.org; Tue, 25 Aug 2020 10:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 25 Aug 2020 14:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 8399 X-GNU-PR-Package: emacs Original-Received: via spool by 8399-submit@debbugs.gnu.org id=B8399.159836657332450 (code B ref 8399); Tue, 25 Aug 2020 14:43:01 +0000 Original-Received: (at 8399) by debbugs.gnu.org; 25 Aug 2020 14:42:53 +0000 Original-Received: from localhost ([127.0.0.1]:35620 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kAaA0-0008RI-S0 for submit@debbugs.gnu.org; Tue, 25 Aug 2020 10:42:53 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:34332) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kAa9z-0008R6-1K for 8399@debbugs.gnu.org; Tue, 25 Aug 2020 10:42:51 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39478) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kAa9r-0007Jl-NS; Tue, 25 Aug 2020 10:42:43 -0400 Original-Received: from [176.228.60.248] (port=2805 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kAa9r-0002e7-4j; Tue, 25 Aug 2020 10:42:43 -0400 In-Reply-To: <87imd697mo.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 25 Aug 2020 15:29:03 +0200) 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" Xref: news.gmane.io gmane.emacs.bugs:186300 Archived-At: > From: Lars Ingebrigtsen > Date: Tue, 25 Aug 2020 15:29:03 +0200 > Cc: Uday S Reddy , 8399@debbugs.gnu.org > > Isn't it more useful to know what files you're saving to, and not > what buffers they're coming from? In the usual case, i.e. where the file name is not something invented by a VM or somesuch, I think the file name is more useful, yes. Or at least it could be. So maybe we should offer this as an optional feature, as I presume the OP's use case is somewhat rare?