From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: write-region bug ? Date: Thu, 09 Jan 2020 16:07:07 +0200 Message-ID: <83k160aflg.fsf@gnu.org> References: <87k169okfu.fsf@igel.home> <83zhf5ixe1.fsf@gnu.org> <83woa7ezzb.fsf@gnu.org> <83r20efua9.fsf@gnu.org> <83k165gbl5.fsf@gnu.org> <046646BD-7C4A-4D42-93F0-9B45980DD9BC@traduction-libre.org> <83y2uldzlz.fsf@gnu.org> <8587D3AF-EB7F-4AF1-806A-5C5EBB5DF8AA@traduction-libre.org> <219F7B4D-88EA-4EE3-A8EB-244A08F43B63@traduction-libre.org> <81246516-A350-4E2A-9F1C-F80BFA0C0316@traduction-libre.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="73536"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 09 15:07:34 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ipYT7-0009Yv-9D for ged-emacs-devel@m.gmane-mx.org; Thu, 09 Jan 2020 15:07:25 +0100 Original-Received: from localhost ([::1]:60976 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ipYT5-0002A4-Ky for ged-emacs-devel@m.gmane-mx.org; Thu, 09 Jan 2020 09:07:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49591) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ipYSZ-0001fC-NP for emacs-devel@gnu.org; Thu, 09 Jan 2020 09:06:52 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57039) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ipYSZ-0003Dv-Hl; Thu, 09 Jan 2020 09:06:51 -0500 Original-Received: from [176.228.60.248] (port=2376 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ipYSY-00086z-It; Thu, 09 Jan 2020 09:06:51 -0500 In-reply-to: (message from Jean-Christophe Helary on Thu, 9 Jan 2020 21:30:49 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:244162 Archived-At: > From: Jean-Christophe Helary > Date: Thu, 9 Jan 2020 21:30:49 +0900 > > Conclusion: the user experience is a mess, messages appear to be contradictory and don't seem to reflect what is actually happening, the state of the file system in emacs does not match the state of the file system in Finder, and besides for the very last message, there are no clues that I've been working on B.txt all that time. My proposed conclusion is different: what you did is not meant for interactive use, certainly not by users who don't have a clear idea what does "visiting a file" means for a buffer and its relation with the file it visits. This feature exists for Lisp programs which need to do something very special for needs that happen relatively rarely, without exposing that to the user. There _are_ interactive features which change the file visited by the current buffer, and they use this very feature, but they do it in a way that doesn't confuse users. See the documentation of "C-x C-w" for more details. > For one, having in plain sight the name of the file (and an extra indication if there are many) associated with the current buffer, if any, or an indication that the buffer is not targeting its original file, would go a long way to remove a considerable amount of potential confusion. The display in the frame title that you describe is just the default. It is deemed to be convenient and useful in regular use, because normally users aren't expected to have the buffer's and file's names diverge. But if you intend to do this stuff frequently, or don't like the default for any other reason, you can customize that to have the file name displayed, either together with, or even instead of, the buffer name. See frame-title-format for more about this.