git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Pascal Obry" <pascal@obry.net>, "Xavier Maillard" <xma@gnu.org>,
	"しらいしななこ " <nanako3@bluebottle.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/2] help: use man viewer path from "man.<tool>.path" config var
Date: Tue, 25 Mar 2008 07:19:01 +0100	[thread overview]
Message-ID: <200803250719.02044.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vd4poqwu6.fsf@gitster.siamese.dyndns.org>

Le vendredi 21 mars 2008, Junio C Hamano a écrit :
> Christian Couder <chriscool@tuxfamily.org> writes:
> >
> > It's perhaps more honest, but kfmclient is not as well known as
> > konqueror.
> >
> > Isn't a documentation patch like this enough:
>
> I dunno.  I am not a KDE use to begin with.
>
> But I am somewhat uncomfortable with this kind of magic, and very much
> more so with basing the magic on the name of a binary.

I think in this case it should be ok if it's properly documented.

It's good to have a consistent user interface with meaningfull names for the 
available options. And we are right to try to do the same thing as when 
browsing an HTML man page.

In the documentation patch for "man.<tool>.cmd" that I will send just after 
this email, there is also enough information to understand what is going on 
and to find a good way around the magic if needed.

I can send the same kind of documentation patch for git-web--browse too, so 
we are completely consistent.

> For example, if a distro offers two versions of konq to co-exist on the
> same system as konqueror-3 and konqueror-4 (with the usual symlink tricks
> /etc/alternatives/konqueror -> konqueror-3 and /usr/bin/konqueror ->
> /etc/alternatives/konqueror to make one version the systemwide default),
> people who want a particular version may say /usr/bin/konqueror-4 and
> would get frustrated to see kfmclient magic would not kick in.  By taking
> honest route without magic, you would not have to worry about such
> potential confusion.

In my experience KDE people have never changed the binary names like that. 
They just use (or advice users to use) different directory names and change 
environment variables (QTDIR, KDEDIR and maybe others) to point to the new 
dirs.

Thanks,
Christian.

  reply	other threads:[~2008-03-25  6:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  5:22 [PATCH 1/2] help: use man viewer path from "man.<tool>.path" config var Christian Couder
2008-03-18 19:02 ` Junio C Hamano
2008-03-20  7:49   ` Christian Couder
2008-03-20 16:51     ` Junio C Hamano
2008-03-21  7:23       ` Christian Couder
2008-03-21  8:56         ` Junio C Hamano
2008-03-25  6:19           ` Christian Couder [this message]
2008-03-25  6:45             ` Junio C Hamano
2008-03-26 23:42               ` Christian Couder
2008-03-23  1:00         ` Xavier Maillard
2008-03-21  1: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=200803250719.02044.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).