From: David Kastrup <dak@gnu•org>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: Steven Grimm <koreth@midwinter•com>,
Sam Ravnborg <sam@ravnborg•org>,
Junio C Hamano <gitster@pobox•com>,
Ismail D?nmez <ismail@pardus•org.tr>,
git@vger•kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3-rc4
Date: Sun, 05 Aug 2007 09:51:06 +0200 [thread overview]
Message-ID: <85bqdmctcl.fsf@lola.goethe.zz> (raw)
In-Reply-To: <alpine.LFD.0.999.0708042127160.5037@woody.linux-foundation.org> (Linus Torvalds's message of "Sat\, 4 Aug 2007 21\:29\:26 -0700 \(PDT\)")
Linus Torvalds <torvalds@linux-foundation•org> writes:
> On Sat, 4 Aug 2007, David Kastrup wrote:
>> >
>> > None that any normal user would want to use.
>>
>> Linus, do you really think that the editor _you_ use is used by more
>> people than Emacs? Think again.
>
> No.
>
> But I'm also not confused enough to think that people should use
> micro-emacs for reading man-pages.
Could you refrain from using name-calling on everybody that does not
share your preferences? It is annoying to hear you talk all the time
about "normal", "sane", "confused" and so on.
> The UNIX philosophy is "do one thing, and do it well".
And Emacs does text, and does it well. It is just that very much
information can ultimately be viewed as text. For example, I can run
grep or locate inside of Emacs. Nothing exciting. And then I can
click on the lines those put out, and get moved to the corresponding
line in the source code, in my editor. Again, nothing exciting, but
it does not work with disconnected tools without the glue Emacs
provides. There are other IDEs providing that sort of thing, but
usually they work just with output they produced themselves.
Using Emacs to read man-pages means that I can grab manpage content
easily with my accustomed editing commands and paste them into a mail
I am composing. Without having to use a mouse or GUI.
It enables workflows that are not possible outside of it. It is ok if
you don't find the tradeoff appealing, but that does not make you
"normal" and other people "confused" and "insane".
So please get a grip and focus on what we were actually talking
about. Not Emacs, but rather documentation formats.
> Man-pages with man.
Actually, Emacs "woman" does a pretty good job with those, offers
convenient man page name completion and works on Windows and similar
platforms without needing
> html with a web browser. And edit stuff with an editor.
>
> Why the *hell* do you confuse my choice of editor with my choice of
> man-page format? I didn't.
Why the hell do you keep changing the topic and go off on sideline
rants.
> That whole "do everything in emacs" is a disease. And then emacs
> users think that it's "sane".
Focus. How do you propose to manage documention of a hundred pages an
more conveniently, finding information easily by text, index,
hyperlinks? A single large HTML page? A documentation directory full
of *.txt files which you can grep through (not that Emacs would not be
useful for that, too)?
How do you find all information pertaining to "remote tracking
branches" in the git documentation? Explain your workflow with that,
and explain why a sane person would prefer that over typing
info git
i remote TAB RET , , ,
and being taken to the respective text locations in turn.
Standalone info _is_ a single application doing a single job:
navigating large hyperlinked plain text documentation efficiently. It
may be an _ugly_ application, but instead of saying what you use
instead in your daily workflow, you revert to name-calling.
If you have a _working_ solution to offer for that task, try
presenting it instead of calling people using other tools names.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-08-05 7:51 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 0:28 [ANNOUNCE] GIT 1.5.3-rc4 Junio C Hamano
2007-08-04 0:41 ` Ismail Dönmez
2007-08-04 1:30 ` Junio C Hamano
2007-08-04 1:48 ` Ismail Dönmez
2007-08-04 3:13 ` Junio C Hamano
2007-08-04 13:26 ` Ismail Dönmez
2007-08-04 3:49 ` Steven Grimm
2007-08-04 4:38 ` Junio C Hamano
2007-08-04 4:57 ` Daniel Barkalow
2007-08-04 5:23 ` Junio C Hamano
2007-08-04 5:52 ` Daniel Barkalow
2007-08-04 6:11 ` Steven Grimm
2007-08-04 6:17 ` Doug Maxey
2007-08-04 9:12 ` Sam Ravnborg
2007-08-04 10:55 ` Steven Grimm
2007-08-04 12:19 ` David Kastrup
2007-08-04 16:03 ` Steven Grimm
2007-08-04 16:08 ` Johannes Schindelin
2007-08-04 16:27 ` David Kastrup
2007-08-05 9:50 ` Jeff King
2007-08-04 16:59 ` Linus Torvalds
2007-08-04 17:49 ` David Kastrup
2007-08-04 19:03 ` Linus Torvalds
2007-08-04 19:55 ` David Kastrup
2007-08-04 21:27 ` J. Bruce Fields
2007-08-05 4:29 ` Linus Torvalds
2007-08-05 7:51 ` David Kastrup [this message]
2007-08-05 17:08 ` Linus Torvalds
2007-08-05 18:08 ` David Kastrup
2007-08-05 18:23 ` Linus Torvalds
2007-08-05 18:35 ` Johannes Schindelin
2007-08-05 19:11 ` David Kastrup
2007-08-05 19:06 ` David Kastrup
2007-08-05 20:32 ` David Kastrup
2007-08-05 19:29 ` Linus Torvalds
2007-08-05 21:43 ` Bruce Korb
2007-08-05 22:15 ` David Kastrup
2007-08-05 22:31 ` J. Bruce Fields
2007-08-08 8:11 ` Man-pages in user manual (was: [ANNOUNCE] GIT 1.5.3-rc4) David Kastrup
2007-08-05 23:38 ` [ANNOUNCE] GIT 1.5.3-rc4 Junio C Hamano
2007-08-06 0:13 ` Miles Bader
2007-08-06 5:44 ` David Kastrup
2007-08-05 9:42 ` Jeff King
2007-08-05 9:54 ` David Kastrup
2007-08-05 9:59 ` Jeff King
2007-08-05 10:20 ` David Kastrup
2007-08-05 10:22 ` Jeff King
2007-08-05 10:40 ` David Kastrup
2007-08-05 11:23 ` David Kastrup
2007-08-04 11:38 ` Johannes Schindelin
2007-08-04 14:29 ` J. Bruce Fields
2007-08-04 7:30 ` David Kastrup
2007-08-04 10:39 ` Timo Hirvonen
2007-08-04 11:46 ` Johannes Schindelin
2007-08-04 12:51 ` Timo Hirvonen
2007-08-04 15:19 ` Michael
2007-08-04 13:11 ` Robin Rosenberg
2007-08-04 13:42 ` Julian Phillips
2007-08-07 12:11 ` David Kågedal
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=85bqdmctcl.fsf@lola.goethe.zz \
--to=dak@gnu$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=ismail@pardus$(echo .)org.tr \
--cc=koreth@midwinter$(echo .)com \
--cc=sam@ravnborg$(echo .)org \
--cc=torvalds@linux-foundation$(echo .)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