From: Stefan Kangas <stefan@marxist.se>
To: Michael Albinus <michael.albinus@gmx.de>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57061@debbugs.gnu.org
Subject: bug#57061: Don't contrast `separate' TRAMP syntax to XEmacs syntax
Date: Tue, 9 Aug 2022 13:52:47 -0700 [thread overview]
Message-ID: <CADwFkmkahHmXhz1sVkXhx__CMTPTVbKcP6KaiMPUB0SHdaHegw@mail.gmail.com> (raw)
In-Reply-To: <87r11pfa3z.fsf@gmx.de>
close 57061 28.2
thanks
Michael Albinus <michael.albinus@gmx.de> writes:
>> Or perhaps "... syntax originating in XEmacs"?
>
> No problem for me. My point is that this syntax is inherited from XEmacs,
> and it should be said so. The concrete wording doesn't matter.
Thanks.
Lars' suggestion sounds good to me, so I installed this on emacs-28:
diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi
index 06df319296..3dc6da6e7d 100644
--- a/doc/misc/tramp.texi
+++ b/doc/misc/tramp.texi
@@ -3161,7 +3161,7 @@ Change file name syntax
@item @code{simplified}
@cindex simplified syntax
-The remote file name syntax is similar to the syntax used by Ange FTP@.
+This remote file name syntax is similar to the syntax used by Ange FTP@.
A remote file name has the form
@code{@value{prefix}user@@host@value{postfix}path/to/file}. The
@code{user@@} part is optional, and the method is determined by
@@ -3173,7 +3173,7 @@ Change file name syntax
@clear unified
@set separate
@include trampver.texi
-The remote file name syntax is similar to the syntax used by XEmacs.
+This remote file name syntax originated in the XEmacs text editor.
A remote file name has the form
@code{@trampfn{method,user@@host,path/to/file}}. The @code{method}
and @code{user@@} parts are optional.
next prev parent reply other threads:[~2022-08-09 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:47 bug#57061: Don't contrast `separate' TRAMP syntax to XEmacs syntax Stefan Kangas
2022-08-09 5:34 ` Michael Albinus
2022-08-09 18:31 ` Lars Ingebrigtsen
2022-08-09 20:14 ` Michael Albinus
2022-08-09 20:52 ` Stefan Kangas [this message]
2022-08-10 6:20 ` Michael Albinus
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=CADwFkmkahHmXhz1sVkXhx__CMTPTVbKcP6KaiMPUB0SHdaHegw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=57061@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
/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).