From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: RE: Modernize frame-title-format: "%b - GNU Emacs" Date: Tue, 1 Sep 2020 19:00:45 +0200 (CEST) Message-ID: References: <> <> <<83y2lux5hm.fsf@gnu.org>> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13186"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , Stefan Kangas , emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 01 19:02:12 2020 Return-path: Envelope-to: ged-emacs-devel@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 1kD9fg-0003JN-4P for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Sep 2020 19:02:12 +0200 Original-Received: from localhost ([::1]:47828 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kD9ff-0001iw-4P for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Sep 2020 13:02:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49496) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kD9eV-00013y-BX for emacs-devel@gnu.org; Tue, 01 Sep 2020 13:00:59 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:54370) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kD9eT-0004HI-5l; Tue, 01 Sep 2020 13:00:59 -0400 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 081H0ngQ015429 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Tue, 1 Sep 2020 17:00:50 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 081H0woY002127; Tue, 1 Sep 2020 17:00:58 GMT In-Reply-To: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/01 11:42:02 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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.io gmane.emacs.devel:254474 Archived-At: > > There's no need for Emacs to justify its behavior wrt other editors or > any other programs, to anyone. Emacs users and developers can decide > what Emacs behavior should be, including default behavior. > I'm an Emacs user, so please allow me to voice my opinions ;-) > > Again: What's a good argument on its own merits, without recourse to an > argument from authority? ("Everybody else does it!") > > Everyone in Texas might have 42 guns and attend church twice every > Sunday. That's not a reason why everyone in Switzerland should act the > same. > That's not at all what I said. Please don't ridicule what I said, it's not helpful. I said: "Where a file is located is most often as important as (and sometimes more important than) the file name to identify a file, at least of you are a programmer." And: "Understanding a uniquified buffer name with only a part of the directory placed after the file name between angle brackets requires (at least for me) much more effort than understanding `buffer-file-truename'. The former is, BTW, much less predictable, as it changes when you open and close files/buffers. The fact that most code editors chose to use the latter is, at least for me, an indication that it is in general easier to understand, and it is indeed, at least for me, easier to understand." If you read this, you'll see that I give arguments that have nothing to do with arguments by authority: "where a file is located is often important" (independently of the fact that another file with the same name is currently opened in Emacs), and the current default behavior "requires more mental effort", because buffer names are "less predictable" and "change". To this I added that my personal experience is indeed that `buffer-file-truename' is easier to understand than `(buffer-name)', and that the fact that the majority of other code editors use `buffer-file-truename' and not `(buffer-name)' is for me an indication that I'm not the only one to have that experience. None of these arguments are arguments by authority. Two more arguments, that are still not arguments by authority: The current default behavior of Emacs (using only the filename as its buffer names) dates from a time when users did not have many files, or at least much less files than what we have today. So having a buffer named "interp.lsp" or "comp.pas" was clear enough. Nowadays it is often not. Emacs has adopted many of the more modern mechanisms used in text/code editors (for example, mouse interaction, the menu bar, the tool bar). It could have been argued that they were unnecessary and should have been disabled by default. I believe Emacs could adopt this (minor) feature as well. In short, my opinion is that: 1. it would be a good thing to introduce a %B construct for mode-line-format and frame-title-format, equivalent to `(or buffer-file-truename "%b")' 2. it would be a good thing if frame-title-format default value was `("%B - GNU Emacs at " system-name)' 3. it would be a good thing to have an option (perhaps a format option) to shorten directory names in %B (for example "%1B" to have "/u/i/stdio.h") Now I stop arguing, and will not contribute further to this thread.