unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: jidanni@jidanni.org, emacs-devel@gnu.org
Subject: Re: dired-man can't deal with compressed pages
Date: Sun, 22 Feb 2004 23:59:29 +0200	[thread overview]
Message-ID: <8765dyzshr.fsf@mail.jurta.org> (raw)
In-Reply-To: 4038-Sun22Feb2004225922+0200-eliz@elta.co.il

"Eli Zaretskii" <eliz@elta.co.il> writes:
>> From: Juri Linkov <juri@jurta.org>
>> Date: Sun, 22 Feb 2004 21:03:02 +0200
>> 
>> I agree that this will not work for man who don't have the -l option.
>> On the other hand, man with the -l option should take the advantage of
>> this option.  So I think a good solution is to let users to choose
>> the command line they want, like in the patch below.
>
> The canonical Emacs solution to such situations is to try running
> `man' with the -l switch and see if it barfs.

Seeing how man barfs will not help to construct an alternative
command line.

>> I think it's better not to duplicate what man already does.
>
> `man' doesn't do what we want except where it supports -l.

This is why I suggested that the user should be able to specify
how to uncompress compressed man files (guznip, uncompress, etc.)

>> Blindly running the file through all preprocessors will fail if some
>> preprocessor is not installed.
>
> ??? Is that even possible?  I thought all the preprocessors we need
> (eqn, tbl, refer, and soelim) are always installed as part of the
> standard Troff/Groff/man packages.  How else would users be able to
> format the pages they have?

Could you assure that all these preprocessors are available for all
man versions?

>> > Yet another possible solution is to use functions from woman.el, which
>> > IIRC has a special command to format a single file.  However, I don't
>> > remember how well it supports various preprocessors.
>> 
>> There is already a dired binding to `W' key in woman.el.
>> So users desiring a woman can get her with this key.
>
> Then perhaps dired-x should suggest using it on systems which don't
> support "man -l", if the file at point requires that.

That would be good.

-- 
http://www.jurta.org/emacs/

  reply	other threads:[~2004-02-22 21:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  0:45 dired-man can't deal with compressed pages Juri Linkov
2004-02-22  6:31 ` Eli Zaretskii
2004-02-22 19:03   ` Juri Linkov
2004-02-22 20:59     ` Eli Zaretskii
2004-02-22 21:59       ` Juri Linkov [this message]
2004-02-23  6:09         ` Eli Zaretskii
2004-02-23 19:07           ` Kevin Rodgers
2004-02-23 19:51             ` Eli Zaretskii
2004-02-23  3:42       ` Juri Linkov
2004-02-23  6:12         ` Eli Zaretskii
2004-02-23 18:57         ` Richard Stallman
2004-02-23 15:28       ` Stefan Monnier
2004-02-23 18:57         ` Eli Zaretskii
2004-02-23 23:36 ` Juri Linkov
2004-02-24  6:21   ` Eli Zaretskii
2004-02-24 22:03     ` Juri Linkov
2004-02-24 19:26   ` Dan Jacobson

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=8765dyzshr.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=jidanni@jidanni.org \
    /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).