From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@posteo.net>
Cc: alain.cochard@unistra.fr, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table)
Date: Mon, 20 Feb 2023 15:54:27 +0100 [thread overview]
Message-ID: <25587.35235.779651.612028@gargle.gargle.HOWL> (raw)
In-Reply-To: <87pma44pky.fsf@localhost>
Ihor Radchenko writes on Mon 20 Feb 2023 10:07:
> I looked further, and the situation is not as simple.
> https://grammarhow.com/backend-back-end-or-back-end/, for example,
> claims that only "back-end" is grammatically correct.
>
> I am now thinking to do the following:
> 1. Use "backend" in the code symbols
> 2. Use "back-end" in docstrings and the manual.
>
> Would it make sense?
It is not clear to me why it would be a problem to use 'backend' in
code symbols as well, but the only important thing for me as a user is
that the terminology be consistent throughout the documentation. So
yes, it makes sense.
The link you provide is very convincing. Will it still hold in 5 or
10 year from now? (see end of
https://www-cs-faculty.stanford.edu/~knuth/email.html)
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
next prev parent reply other threads:[~2023-02-20 14:56 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 ` [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table) Ihor Radchenko
2023-02-20 10:07 ` Ihor Radchenko
2023-02-20 14:54 ` Alain.Cochard [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25587.35235.779651.612028@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.