From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 58899@debbugs.gnu.org, Brian Cully <bjc@spork.org>
Subject: bug#58899: [PATCH v1] Add the "doas" alias to eshell.
Date: Mon, 31 Oct 2022 09:16:56 +0100 [thread overview]
Message-ID: <87r0yojtl3.fsf@gmx.de> (raw)
In-Reply-To: <286825e7-2dc2-9cc7-73a3-1056a249d56f@gmail.com> (Jim Porter's message of "Sun, 30 Oct 2022 14:51:26 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi,
>> I'm unsare whether to use “TRAMP” or “Tramp” spelling. The existing
>> routines in the file use the former, but I've been informed the latter
>> is correct. A future patch should make all spellings (at least within
>> this module) consistent.
>
> I'd say go with "Tramp" like you did in your patch. Since you're
> modifying code near most of the existing usages of "TRAMP", now would
> probably be a good time to fix that everywhere in the file too.
Yes. Sometimes it might even be worth to RTFM. From the Tramp manual
(info "(tramp) Frequently Asked Questions")
--8<---------------cut here---------------start------------->8---
• What is the official name - “Tramp” or “TRAMP”?
The official name is “Tramp”. This is used in comments,
docstrings, and everywhere speaking about TRAMP.
However, for historical reasons this is formatted as “@sc{Tramp}”
in the TRAMP manual. *note (texinfo)Smallcaps::. So it looks
different there.
--8<---------------cut here---------------end--------------->8---
Best regards, Michael.
next prev parent reply other threads:[~2022-10-31 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 16:42 bug#58899: [PATCH v1] Add the "doas" alias to eshell Brian Cully via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-30 21:51 ` Jim Porter
2022-10-30 22:06 ` Jim Porter
2022-10-31 12:36 ` Eli Zaretskii
2022-10-31 8:16 ` Michael Albinus [this message]
2022-10-31 16:01 ` Brian Cully via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-31 18:01 ` Eli Zaretskii
2022-10-31 18:29 ` Brian Cully via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-03 17:09 ` Jim Porter
2022-11-03 20:24 ` Brian Cully via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05 19:10 ` Jim Porter
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0yojtl3.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=58899@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=jporterbugs@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.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).