From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Marek =?UTF-8?Q?=C4=BDach?= via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#54081: Date: Tue, 22 Feb 2022 17:03:57 +0100 (CET) Message-ID: References: Reply-To: Marek =?UTF-8?Q?=C4=BDach?= Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_75954_112466953.1645545837178" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4108"; mail-complaints-to="usenet@ciao.gmane.io" To: 54081@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Feb 22 17:05:31 2022 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 1nMXfO-0000na-E6 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 22 Feb 2022 17:05:30 +0100 Original-Received: from localhost ([::1]:43548 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nMXfN-0003F6-6X for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 22 Feb 2022 11:05:29 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37724) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nMXew-0003Cb-8Z for bug-gnu-emacs@gnu.org; Tue, 22 Feb 2022 11:05:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48534) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nMXev-0003Qp-Va for bug-gnu-emacs@gnu.org; Tue, 22 Feb 2022 11:05:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nMXev-0001YU-O8 for bug-gnu-emacs@gnu.org; Tue, 22 Feb 2022 11:05:01 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: Resent-From: Marek =?UTF-8?Q?=C4=BDach?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 22 Feb 2022 16:05:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54081 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 54081-submit@debbugs.gnu.org id=B54081.16455458455905 (code B ref 54081); Tue, 22 Feb 2022 16:05:01 +0000 Original-Received: (at 54081) by debbugs.gnu.org; 22 Feb 2022 16:04:05 +0000 Original-Received: from localhost ([127.0.0.1]:42431 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nMXe1-0001XB-Cb for submit@debbugs.gnu.org; Tue, 22 Feb 2022 11:04:05 -0500 Original-Received: from w4.tutanota.de ([81.3.6.165]:48786) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nMXdz-0001Wg-7t for 54081@debbugs.gnu.org; Tue, 22 Feb 2022 11:04:03 -0500 Original-Received: from w3.tutanota.de (unknown [192.168.1.164]) by w4.tutanota.de (Postfix) with ESMTP id 3397510602E4 for <54081@debbugs.gnu.org>; Tue, 22 Feb 2022 16:03:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1645545837; s=s1; d=tutanota.com; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender; bh=EWgBXtabqVZrM3PUuS+75+ex/YdTI4bm9mCx8lTVz4Y=; b=rGtfJbUIbKa6PlZXewH2cCDb1vupfE46AkYC9nVc+dxCpjYyE2eNHqbIf/Qctl9n usA7EvZ1kDpXK8A3JNCumgPWg5EPJu6/DGT9EQeS1NAGId/nfvfLPvANrKwk/JZVqh9 wOxfZUJzDG0fFEJCy402CNLkHCSxnz9VoE63jsO9gisV9rmpRIrsIAhvoD+16nsJ7OB LVL8+4dac/Sto67n34UtgTJQmj2YyOB/nUjnLYq2oxEnfq2YRogLTW6anM3MskTldi8 LQjjM7r5HWTAhv4V5FkAEwCGiO+T3ERNUgMUgTuH7EkRYRa7dRhsh8TIQZpRkboXezF 3v7tzCevZA== 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:227442 Archived-At: ------=_Part_75954_112466953.1645545837178 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I should clarify, that I=C2=A0do not consider this a very important issue r= eally, but rather a nice-to-have. It is more of a suggestion for when the name of the buffer doesn=E2=80=99t = yet appear in the MODE line, because it hasn=E2=80=99t been saved yet for e= xample (like if a document is being created in a persistant buffer first, b= ut not yet saved...)=C2=A0 Which makes me think that I should have formulated the suggestion quite a b= it better at the start:=C2=A0 If hitting C-b Beggining of buffer, state it the buffer is not named too, l= ike: Beggining of buffer. . If the buffer is already saved/na= med, then perhaps state something like: Beginning of buffer. Saved as:=C2= =A0mygreatnovel.org As such this functionality wouldn=E2=80=99t be for displaying the name of t= he buffer per-se, but for displaying the name of the buffer (or perhaps eve= n informing the user about the lack of thereof?), only when certain actions= with that buffer are performed, like saving/mamina, renaming/changing exte= nsion/switching mode etc... ------=_Part_75954_112466953.1645545837178 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I should clarify, that I do not consider this a very important is= sue really, but rather a nice-to-have.

I= t is more of a suggestion for when the name of the buffer doesn=E2=80=99t y= et appear in the MODE line, because it hasn=E2=80=99t been saved yet for ex= ample (like if a document is being created in a persistant buffer first, bu= t not yet saved...) 
Which ma= kes me think that I should have formulated the suggestion quite a bit bette= r at the start: 

If hitting C-b Beggining of buffer, state it the buffer is not named = too, like: Beggining of buffer. <Unknown name>. If the buffer is alre= ady saved/named, then perhaps state something like: Beginning of buffer. Sa= ved as: mygreatnovel.or= g

As such this functionality wouldn= =E2=80=99t be for displaying the name of the buffer per-se, but for display= ing the name of the buffer (or perhaps even informing the user about the la= ck of thereof?), only when certain actions with that buffer are performed, = like saving/mamina, renaming/changing extension/switching mode etc...
------=_Part_75954_112466953.1645545837178--