From: Ihor Radchenko <yantar92@posteo.net>
To: Tim Cross <theophilusx@gmail.com>
Cc: Bastien <bzg@gnu.org>, "André A. Gomes" <andremegafone@gmail.com>,
Timothy <orgmode@tec.tecosaur.net>,
emacs-orgmode@gnu.org
Subject: Re: [RFC] Re: Headings and Headlines
Date: Sun, 20 Nov 2022 05:45:10 +0000 [thread overview]
Message-ID: <87bkp2kwm1.fsf@localhost> (raw)
In-Reply-To: <86v8namtjd.fsf@gmail.com>
Tim Cross <theophilusx@gmail.com> writes:
> I think we are needlessly complicating this. We are talking about the
> use of a term in an internal code base. While I would agree heading is
> more correct, I don't think it is such a big issue to use headline if
> that make the transition to a consistent usage easier. When it comes to
> code, I think consistency trumps correctness.
Changing documentation means changing function symbols.
Changing function symbols means changing the code.
Changing the code should not reduce code readability, which is of
paramount importance to keep new contributions coming.
That's why I also consider code consistency important.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-11-20 5:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 13:32 Headings and Headlines André A. Gomes
2021-07-23 13:56 ` Eric S Fraga
2021-07-23 15:43 ` Christopher Dimech
2021-07-23 15:47 ` Timothy
2021-07-23 15:55 ` Eric S Fraga
2021-07-23 14:04 ` Marco Wahl
2021-07-23 15:03 ` Kaushal Modi
2021-07-23 14:34 ` Timothy
2021-07-23 14:56 ` André A. Gomes
2021-07-23 15:39 ` Timothy
2021-07-24 2:06 ` Tim Cross
2021-07-24 4:04 ` Tom Gillespie
2021-07-24 11:49 ` Matt Price
2021-07-24 18:56 ` Charles Millar
2021-07-24 19:23 ` Timothy
2022-11-13 6:59 ` [RFC] " Ihor Radchenko
2022-11-13 21:10 ` Rudolf Adamkovič
2022-11-14 4:36 ` Ihor Radchenko
2022-11-16 22:16 ` Tim Cross
2022-11-19 13:46 ` Bastien Guerry
2022-11-19 14:34 ` Vikas Rawal
2022-11-19 15:03 ` Timothy
2022-11-19 15:54 ` Bastien Guerry
2022-11-19 15:54 ` Bastien
2022-11-19 16:01 ` Ihor Radchenko
2022-11-19 23:04 ` Tim Cross
2022-11-20 0:56 ` Vikas Rawal
2022-11-20 5:45 ` Ihor Radchenko [this message]
2022-11-20 5:46 ` Bastien
2022-11-20 5:53 ` Ihor Radchenko
2022-11-27 3:33 ` Ihor Radchenko
2022-11-27 10:32 ` Bastien
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87bkp2kwm1.fsf@localhost \
--to=yantar92@posteo.net \
--cc=andremegafone@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--cc=theophilusx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).