From: Ihor Radchenko <yantar92@posteo.net>
To: alain.cochard@unistra.fr
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table)
Date: Tue, 22 Nov 2022 08:31:39 +0000 [thread overview]
Message-ID: <87tu2rie50.fsf@localhost> (raw)
In-Reply-To: <25461.4423.734070.149776@gargle.gargle.HOWL>
Alain.Cochard@unistra.fr writes:
> PS 1: In the manual, I see "backend" and "back-end". So it is an
> issue similar to the "subtree/sub-tree" issue you fixed a few days
> ago, to the "heading/headline" issue that was reported recently, and
> to many similar cases I met in the past. So I was wondering if there
> could exist some (semi-)automatic way which would ensure that future
> maintainers will not inadvertently re-introduce "sub-tree"
> occurrences, or the like. Perhaps some "accepted terminology" list
> that would be checked upon?
I looked into the manual. It has 197 instances of "back-end" and 24
instances of "backend". In the code, "backend" is used almost exclusively
in symbol names (except 5 instances), and "back-end" is used in the
docstrings and comments.
It is actually a bit confusing.
I am looking at https://techterms.com/definition/backend, and it looks
like "backend" is the correct word we need to use here. Am I missing
something?
--
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-22 8:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 6:58 2 'echo' bash instructions produce a table Alain.Cochard
2022-11-07 2:31 ` Ihor Radchenko
2022-11-13 20:41 ` Alain.Cochard
2022-11-14 3:59 ` Ihor Radchenko
2022-11-15 6:00 ` [RFC] :var x=list-name should be resolved into simple lists (item1 item2 ...); not nested ((item1) (item2) ...) (was: 2 'echo' bash instructions produce a table) Ihor Radchenko
2022-11-26 1:54 ` Ihor Radchenko
2022-11-16 1:24 ` 2 'echo' bash instructions produce a table Ihor Radchenko
2022-11-21 9:04 ` Ihor Radchenko
2022-11-21 9:05 ` Ihor Radchenko
2022-11-16 16:35 ` Alain.Cochard
2022-11-19 12:28 ` Rudolf Adamkovič
2022-11-20 5:05 ` Ihor Radchenko
2022-11-22 8:16 ` Ihor Radchenko
2022-11-22 19:13 ` Alain.Cochard
2022-11-24 1:55 ` Ihor Radchenko
2022-11-22 8:31 ` Ihor Radchenko [this message]
2023-02-20 10:07 ` [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table) Ihor Radchenko
2023-02-20 14:54 ` Alain.Cochard
2023-04-06 9:57 ` Ihor Radchenko
2023-04-20 12:17 ` Ihor Radchenko
2023-04-06 23:43 ` Samuel Wales
2022-11-22 8:37 ` [BUG] Make source block auto-completion work for all the loaded babel backends " Ihor Radchenko
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=87tu2rie50.fsf@localhost \
--to=yantar92@posteo.net \
--cc=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
/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).