unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: man integration with tramp
Date: Thu, 30 Jul 2020 19:58:16 +0200	[thread overview]
Message-ID: <87r1ssdgw7.fsf@gmx.de> (raw)
In-Reply-To: <20200730044554.obcvownwrmv4du7m@ergus> (Ergus's message of "Thu,  30 Jul 2020 06:45:54 +0200")

Ergus <spacibba@aol.com> writes:

> Hi:

Hi Ergus,

> Do we have any functionality to support man in tramp mode to access man
> pages in the remote node?
>
> The actual implementation of man has call-process so I suppose we
> don't. But it doesn't seems too complex to do.
>
> Suggestions?
>
> Should we add a different command, a configuration option or you think
> it is not a good idea? Is there anything special to take into account
> and I am ignoring so far?

I think it is a good idea. Sometimes, I felt such a need as well. But it
was so rare, that it didn't kick me enough to run.

I see two possibilities to achieve this goal.

- Adapt man.el. Likely, it just needs a prefix argument for `man' and
  related commands. This would control to call the remote counterparts of
  `call-process' and `start-process', resulting man pages from a remote
  host. A proper managemnt of $MANPATH for different hosts is also
  required.

- Configure woman.el. Likely, we don't need to touch the code; just
  instructions are needed how to set `woman-manpath', `woman-path' and
  friends for remote hosts. Maybe we must enable connection-local
  variables in woman.el (this would be a code change, but a small one).

Personally, I prefer the second option, but I haven't digged deeper for
possible problems.

Comments?

> Best
> Ergus

Best regards, Michael.



  reply	other threads:[~2020-07-30 17:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200730044554.obcvownwrmv4du7m.ref@ergus>
2020-07-30  4:45 ` man integration with tramp Ergus
2020-07-30 17:58   ` Michael Albinus [this message]
2020-07-30 19:38     ` Eli Zaretskii
2020-07-31  9:24       ` Michael Albinus
2020-07-31 12:34         ` Eli Zaretskii
2020-07-31 12:41           ` Michael Albinus
2023-10-07 11:42             ` Max Nikulin
2023-10-07 12:00               ` Michael Albinus
2023-10-07 16:37                 ` Max Nikulin
2023-10-07 16:49                   ` Michael Albinus
2023-10-08  3:02                     ` Max Nikulin
2023-10-08  8:06                       ` 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=87r1ssdgw7.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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).