From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: New optional Eshell module: em-elecslash
Date: Sat, 16 Apr 2022 14:12:52 -0700 [thread overview]
Message-ID: <871qxwka0b.fsf@melete.silentflame.com> (raw)
In-Reply-To: <83ee1wzvki.fsf@gnu.org>
Hello,
On Sat 16 Apr 2022 at 10:18PM +03, Eli Zaretskii wrote:
>> +passed to Lisp functions must have Tramp's @code{/method:host:}
> ^^^^^^^^^^^^^^^^^^^^
> File names should have the @file markup.
>
>> +@noindent and in reviewing the output of the command, you identify a
>> +file @code{/etc/gnugnu} that should be moved somewhere else. So you
> ^^^^^^^^^^^^^^^^^^
> Likewise (and elsewhere in the patch).
>
>> +@noindent But since @code{mv} refers to the local Lisp function
> ^^^^^^^^^
> "mv" is a command, so it should use the @command markup.
I'm sorry I didn't figure these out by myself. I've now found the
relevant section of the texinfo manual so should be able to get them
right myself from now on.
--
Sean Whitton
next prev parent reply other threads:[~2022-04-16 21:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 2:48 Optional Eshell modules -- to emacs.git or ELPA? Sean Whitton
2022-01-29 11:51 ` Philip Kaludercic
2022-04-16 18:57 ` New optional Eshell module: em-elecslash Sean Whitton
2022-04-16 19:18 ` Eli Zaretskii
2022-04-16 20:04 ` Sean Whitton
2022-04-16 21:42 ` [External] : " Drew Adams
2022-04-17 6:20 ` Eli Zaretskii
2022-04-17 16:48 ` [External] : " Drew Adams
2022-04-19 16:52 ` Sean Whitton
2022-04-20 0:36 ` Sean Whitton
2022-04-20 6:19 ` Eli Zaretskii
2022-04-20 20:14 ` Sean Whitton
2022-04-21 6:15 ` Eli Zaretskii
2022-04-16 21:12 ` Sean Whitton [this message]
2022-04-16 22:58 ` Stefan Monnier
2022-04-17 5:02 ` Sean Whitton
2022-04-17 6:24 ` Jim Porter
2022-04-19 15:28 ` Sean Whitton
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=871qxwka0b.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@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.