From: Eshel Yaron <me@eshelyaron.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: master 861ac933dd8: Run `man' also on remote systems
Date: Thu, 02 Nov 2023 12:55:03 +0100 [thread overview]
Message-ID: <m1jzr0bca0.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <87o7gcs8nb.fsf@gmx.de> (Michael Albinus's message of "Thu, 02 Nov 2023 12:21:28 +0100")
> I have pushed your proposals to master with the modification, that it
> doesn't speak about *execution* of the man program on the remote
> system. Not all Tramp backends support remote processes, so we cannot
> let run man there. Instead, for such use cases, I plan to implement a
> local copy of the man page from the remote system, and let run "man -l
> <local copy>" then.
I see, that makes sense. So ISTM that what the new option essentially
does is to control whether or not Emacs renders remote man pages, versus
only rendering pages found on the local system. Is that a correct
description?
>> I'm would also consider changing the name of the new user option from
>> `Man-support-remote-systems' to `Man-execute-on-remote-systems', since
>> to me that better conveys the choice you make by setting this option.
>
> For the very same reason I haven't applied this change. But of course,
> I'm open to any better name for `Man-support-remote-systems'.
How about `Man-render-remote-manpage`, or `Man-use-remote-manpage`?
next prev parent reply other threads:[~2023-11-02 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169885408539.20142.2201339795070761011@vcs2.savannah.gnu.org>
[not found] ` <20231101155445.B09E0C0C180@vcs2.savannah.gnu.org>
2023-11-01 18:10 ` master 861ac933dd8: Run `man' also on remote systems Eshel Yaron
2023-11-01 20:13 ` Emanuel Berg
2023-11-02 6:16 ` Eli Zaretskii
2023-11-02 11:21 ` Michael Albinus
2023-11-02 11:43 ` Emanuel Berg
2023-11-02 11:55 ` Eshel Yaron [this message]
2023-11-02 13:51 ` Eli Zaretskii
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=m1jzr0bca0.fsf@dazzs-mbp.home \
--to=me@eshelyaron.com \
--cc=emacs-devel@gnu.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).