From: Timothy <orgmode@tec.tecosaur.net>
To: Vikas Rawal <vikasrawal@gmail.com>
Cc: "Bastien Guerry" <bzg@gnu.org>,
"Ihor Radchenko" <yantar92@posteo.net>,
"André A. Gomes" <andremegafone@gmail.com>,
Timothy <orgmode@tec.tecosaur.net>,
emacs-orgmode@gnu.org
Subject: Re: [RFC] Re: Headings and Headlines
Date: Sat, 19 Nov 2022 23:03:22 +0800 [thread overview]
Message-ID: <87zgcnq8wm.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <CALtzAB0oBjA7qA9yCyGwaXkQAN6OteEW48Q4S8tqmaEQG_GQyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
Hi Vikas,
> I think, from a linguistic perspective, “heading” and “subheading” are more
> appropriate than “headline” and “subheadline”.
Unfortunately I’m completely with you (and previous comments here). The meaning
of “headline” is closer to “title” than “heading”. A document can have multiple
headings but only a single headline (which is specifically the line at the top,
e.g. “Newspaper headline”).
As Ihor points out though, from a compat perspective, a change to “heading” may
be intractable. This gives me rather mixed feelings, as I’m of a similar mind
regarding the org-element headline->heading change being too problematic, but
settling on the less accurate term seems quite undesirable too, and doesn’t sit
well with me.
All the best,
Timothy
--
Timothy (‘tecosaur’/‘TEC’), 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/tec>.
next prev parent reply other threads:[~2022-11-19 15:09 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 [this message]
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
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=87zgcnq8wm.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=andremegafone@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=vikasrawal@gmail.com \
--cc=yantar92@posteo.net \
/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).