All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] Documentation/config.txt: Order variables alphabetically
Date: Thu, 2 Dec 2010 10:32:58 +0100	[thread overview]
Message-ID: <20101202093258.GA7035@neumann> (raw)
In-Reply-To: <87oc94spax.fsf@picasso.cante.net>

Don't cull the Cc list.


On Thu, Dec 02, 2010 at 07:43:02AM +0200, Jari Aalto wrote:
> 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.

Based on my own experience, I disagree, ...

> 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).

... and therefore I much prefer using the search function.

> [*] less(1) is not the default manual page pager everywhere.

I assume that nowadays search-capable pagers are much more widespread
than non-search-capable ones.


Gábor

  reply	other threads:[~2010-12-02  9:33 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
2010-12-02  9:32                 ` SZEDER Gábor [this message]
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=20101202093258.GA7035@neumann \
    --to=szeder@ira.uka.de \
    --cc=git@vger.kernel.org \
    --cc=jari.aalto@cante.net \
    --cc=jnareb@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.