git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
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, 18 Mar 2008 12:02:43 -0700	[thread overview]
Message-ID: <7vabkv7t4c.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080318062236.7b5e515f.chriscool@tuxfamily.org

Christian Couder <chriscool@tuxfamily.org> writes:

> This makes it possible to use different version of the tools
> than the one on the current PATH, or maybe a custom script.
>
> In this patch we also try to launch "konqueror" using
> "kfmclient" even if a path to a konqueror binary is given
> in "man.konqueror.path".

It may be true that allowing customizable paths may be more useful than
not allowing them, so I do not have fundamental objection to this
enhancement.  However, I doubt this s/konqueror/kfmclient/ is a good idea.

As a general rule, if you allow the user to explicitly say "instead of
what you would normally use, use _this_", you should not try to outsmart
the user by using something else that you derived from that "_this_" the
user gave you.

If the user wants to use kfmclient, then the user can say so.  If the user
wants to really launch konq instead of using kfmclient for whatever
reason, the outsmarting code will interfere and make it impossible.

  reply	other threads:[~2008-03-19 19:31 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 [this message]
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
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=7vabkv7t4c.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --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).