unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: spacibba@aol.com, emacs-devel@gnu.org
Subject: Re: man integration with tramp
Date: Fri, 31 Jul 2020 14:41:23 +0200	[thread overview]
Message-ID: <875za326x8.fsf@gmx.de> (raw)
In-Reply-To: <83lfizeucs.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 Jul 2020 15:34:27 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> I'm trying to use woman.el as basis for support of remote man pages,
>> because a short review of man.el gave me the impression that it takes
>> more than just replacing `call-process' by `process-file' at one place.
>
> I understand.  If doing so will solve enough use cases, it's a good
> compromise, of course.

I'll give it a try. If it turns out to be too complex, I'll give up with
woman.el, promised!

Btw, one advantage using woman.el instead of man.el would be, that you
could handle remote man pages for Tramp methods which do not support
remote processes, like sftp or maybe even ftp.

Best regards, Michael.



  reply	other threads:[~2020-07-31 12:41 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
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 [this message]
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=875za326x8.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=eliz@gnu.org \
    --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).