emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Rudolf Adamkovič" <salutis@me.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-src: Improve the name of source editing buffers
Date: Tue, 07 Mar 2023 22:15:47 +0100	[thread overview]
Message-ID: <m2ilfc460s.fsf@me.com> (raw)
In-Reply-To: <87ilfcg0wy.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Could you elaborate about "more standard"?

Sure.  For example, when I look at my Mode Line now, I see that the major more
is "Message[Notmuch]".  When I look at the names of the currently open buffers,
I see "FOO" and "{FOO}" and "[FOO] BAR" and "FOO(BAR)".  All this is "standard"
in Emacs.  I have yet to see a buffer, or anything else, named `FOO BAR[ BAZ ]'.

> A safer way to fix the inconsistency in the docstring would be updating
> the docstring to reflect the reality.

But misses the point, for I set out to fix the name itself.  I noticed the
documentation error only after the fact.

Every time I see "Org Src FOO BAR[ BAZ ]", it makes me think for a moment that I
must have misconfigured the mode line string or something.  And why?  Because it
looks "non-standard", like nothing else.

"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications."
-- Alfred North Whitehead, 1861-1947

Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava

  reply	other threads:[~2023-03-07 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 14:02 [PATCH] org-src: Improve the name of source editing buffers Rudolf Adamkovič
2023-03-05 21:26 ` Rudolf Adamkovič
2023-03-06 12:09   ` Max Nikulin
2023-03-07 13:13   ` Ihor Radchenko
2023-03-07 21:15     ` Rudolf Adamkovič [this message]
2023-03-08 13:51       ` Ihor Radchenko
2023-03-08 22:02         ` Rudolf Adamkovič
2023-03-10 11:12           ` Ihor Radchenko
2023-03-14 20:55             ` Rudolf Adamkovič

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2ilfc460s.fsf@me.com \
    --to=salutis@me.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).