From: Jari Aalto <jari.aalto@cante•net>
To: git@vger•kernel.org
Subject: Re: [PATCH] Documentation/config.txt: Order variables alphabetically
Date: Thu, 02 Dec 2010 07:43:02 +0200 [thread overview]
Message-ID: <87oc94spax.fsf@picasso.cante.net> (raw)
In-Reply-To: 20101202010229.GA4832@neumann
2010-12-02 03:02 SZEDER Gábor <szeder@ira•uka.de>:
> On Wed, Dec 01, 2010 at 07:10:55PM +0200, Jari Aalto wrote:
>> Same for command line options. You read zillions of scripts and cryptic
>> options. You want to consult manual page to see what an option means. Again
>> you're searching A-Z.
>
> When I want to look up X or a command line option seen somewhere, I
> never search A-Z. I always search using the pager's or browser's
> search function. And when it found what I was searching for, then I
> much prefer to see related options on the same screen.
Thatäs real slow method.
You don't need specific search function (or reliance on those
availability[*]) when you can just tap
PgUp
PgDown
to locate the information by visual cues (A-Z).
[*] less(1) is not the default manual page pager everywhere.
next prev parent reply other threads:[~2010-12-02 5:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 13:12 [PATCH] Documentation/config.txt: Order variables alphabetically jari.aalto
2010-12-01 13:58 ` Jakub Narebski
2010-12-01 14:34 ` jari
[not found] ` <20101201142920.GB6537@picasso.cante.net>
2010-12-01 14:57 ` Jakub Narebski
2010-12-01 15:09 ` jari
2010-12-01 15:19 ` Erik Faye-Lund
2010-12-01 15:33 ` Jari Aalto
2010-12-01 15:37 ` Jari Aalto
2010-12-01 16:37 ` Jakub Narebski
2010-12-01 17:10 ` Jari Aalto
2010-12-01 18:03 ` Jeff King
2010-12-01 23:38 ` Jakub Narebski
2010-12-02 1:02 ` SZEDER Gábor
2010-12-02 5:43 ` Jari Aalto [this message]
2010-12-02 9:32 ` SZEDER Gábor
2010-12-02 5:46 ` Jari Aalto
2010-12-02 9:24 ` SZEDER Gábor
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=87oc94spax.fsf@picasso.cante.net \
--to=jari.aalto@cante$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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