From: Christian Couder <chriscool@tuxfamily.org>
To: Xavier Maillard <xma@gnu.org>
Cc: junkio@cox.net, pascal@obry.net, nanako3@bluebottle.com,
git@vger.kernel.org
Subject: Re: [PATCH] help: implement multi-valued "man.viewer" config option
Date: Fri, 14 Mar 2008 06:26:15 +0100 [thread overview]
Message-ID: <200803140626.16075.chriscool@tuxfamily.org> (raw)
In-Reply-To: <200803140100.m2E105o5004664@localhost.localdomain>
Le vendredi 14 mars 2008, Xavier Maillard a écrit :
> > Ok, woma in not supported here and it is reported like this but
> > would it be possible to just throw an error on stdout and try
> > another viewer ?
>
> Yes, with the following patch on top:
>
> See my "tested-by" message.
Thank you Xavier for this message.
> > We could even imagine something even more
> > general like the possibility for the user to write his own man
> > viewer (a bash script for example) and set it as a candidate.
>
> I will do that in a latter patch, it has been suggested a lot of times
> already.
>
> Glad to read that !
I just sent a patch to do that in "git-web--browse.sh" and I will soon work
on the same stuff for man viewing.
> > By the way, I do not see any reason to put man as a candidate.
> > "man" should be the default when nothing is specified or when all
> > candidates have failed.
>
> It may be more explicit.
>
> Well, I do not buy this argument and I am pretty sure that a
> simple note into the manual would suffice but, that's me :)
As my patch is now on next and as I am not sure to understand exactly what
you want, I can only suggest to send a patch if you really care.
Thanks,
Christian.
next prev parent reply other threads:[~2008-03-14 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 7:51 [PATCH] help: implement multi-valued "man.viewer" config option Christian Couder
2008-03-12 1:00 ` Xavier Maillard
2008-03-12 7:23 ` Christian Couder
2008-03-14 1:00 ` Xavier Maillard
2008-03-14 5:26 ` Christian Couder [this message]
2008-03-15 13:00 ` Xavier Maillard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803140626.16075.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nanako3@bluebottle.com \
--cc=pascal@obry.net \
--cc=xma@gnu.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.
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 NNTP newsgroup(s).