unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
Cc: jidanni@jidanni.org, emacs-devel@gnu.org
Subject: Re: dired-man can't deal with compressed pages
Date: 22 Feb 2004 08:31:02 +0200	[thread overview]
Message-ID: <uptc7eic9.fsf@elta.co.il> (raw)
In-Reply-To: <87r7wolz6u.fsf@mail.jurta.org> (message from Juri Linkov on Sun,  22 Feb 2004 02:45:13 +0200)

> From: Juri Linkov <juri@jurta.org>
> Date: Sun, 22 Feb 2004 02:45:13 +0200
> 
> > From: Dan Jacobson <jidanni@jidanni.org>
> > To: bug-gnu-emacs@gnu.org
> > Date: Sat, 13 Sep 2003 06:45:22 +0800
> >
> > dired-man can't deal with resolvconf.8.gz etc. compressed man pages.
> 
> I think this problem can be fixed by invoking man with the -l option
> and letting it to handle man files properly instead of calling the
> current "nroff -man -h", i.e. to decompress the manual page files,
> to format the nroff source more correctly: preprocess it thought tbl,
> use correct switches, etc. all what man program does.

I'm not sure this is the right way of solving the problem.  For
starters, the "-l" switch is not portable: most versions of `man'
don't support it.  And after thinking for a while, I don't see any way
of forcing those versions of `man' who don't have "-l" to format a
specific file.  I presume this is the reason why dired-x runs nroff
directly.

If the only problem with the current code is that it doesn't support
compressed man pages, perhaps we could detect compressed files and
decompress them on the fly.

As for preprocessors, I don't know.  If this is important, we could
blindly run the file through all of them, for example, or have a user
option to do that.

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.

  reply	other threads:[~2004-02-22  6:31 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 [this message]
2004-02-22 19:03   ` Juri Linkov
2004-02-22 20:59     ` Eli Zaretskii
2004-02-22 21:59       ` Juri Linkov
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=uptc7eic9.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --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).