From: Lennart Borgman <lennart.borgman@gmail.com>
To: akaiser@visi.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Failing to see the allure of Emacs
Date: Tue, 4 May 2010 21:03:29 +0200 [thread overview]
Message-ID: <x2oe01d8a51005041203q67c40c05ib11cbf61f6ea065a@mail.gmail.com> (raw)
In-Reply-To: <v8-dnXxHe96UyzbWnZ2dnUVZ7qNi4p2d@posted.visi>
On Thu, Mar 25, 2010 at 2:24 PM, akaiser@visi.com <akaiser@visi.com> wrote:
>> For someone who gloats about his own documentation successes
>> which I'm not motivated to track down you have marvellously
>> bad communication skills to get your point across.
>
> Noted, Tim, and thanks so much for the help and understanding.
There are sure glitches in the manual. It is a live document
continously beeing worked on. You can of course contribute on the same
term as anyone else. This mean you must be more specific, using
examples.
Regarding using info I think it works very well. In the beginning I
thought html documentation would be better, but I have changed my
mind.
next prev parent reply other threads:[~2010-05-04 19:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 19:02 Failing to see the allure of Emacs Daniel
2010-03-21 20:22 ` David Kastrup
2010-03-21 20:47 ` Pascal J. Bourguignon
2010-03-21 21:00 ` akaiser
2010-03-21 21:26 ` Daniel
2010-03-21 22:16 ` Pascal J. Bourguignon
2010-03-22 4:05 ` Uday S Reddy
2010-03-21 22:21 ` David Kastrup
2010-03-23 17:22 ` akaiser
2010-03-23 17:52 ` Jeff Clough
2010-03-23 19:10 ` akaiser
2010-03-23 19:32 ` Uday S Reddy
2010-03-23 23:00 ` David Kastrup
2010-03-24 21:40 ` Tim X
2010-03-24 22:00 ` akaiser
2010-03-25 0:28 ` Jason Rumney
2010-03-25 1:03 ` Jay Belanger
2010-03-25 1:27 ` despen
2010-03-25 8:42 ` Tim X
2010-03-25 9:19 ` akaiser
2010-03-25 10:01 ` David Kastrup
2010-03-25 10:09 ` akaiser
2010-03-27 20:59 ` Giorgos Keramidas
2010-04-07 5:36 ` David Kastrup
2010-03-25 9:41 ` akaiser
2010-03-25 12:17 ` Tim Landscheidt
2010-03-25 12:24 ` akaiser
2010-05-04 19:03 ` Lennart Borgman [this message]
[not found] ` <mailman.28.1272999835.29092.help-gnu-emacs@gnu.org>
2010-05-05 7:15 ` David Kastrup
2010-05-05 20:40 ` Stefan Monnier
2010-03-25 12:45 ` Jay Belanger
2010-03-25 18:31 ` Uday S Reddy
2010-03-25 14:07 ` Ted Zlatanov
2010-03-25 14:49 ` David Kastrup
2010-03-26 4:14 ` Galen Boyer
2010-05-05 17:27 ` Joel J. Adamson
2010-03-21 21:02 ` Jeff Clough
2010-03-21 22:09 ` Pascal J. Bourguignon
2010-03-21 22:35 ` B. T. Raven
2010-03-21 22:45 ` Pascal J. Bourguignon
2010-03-22 0:21 ` Jeff Clough
2010-03-22 4:45 ` B. T. Raven
2010-05-22 2:38 ` Joseph Brenner
2010-03-21 22:58 ` John Bokma
2010-04-20 13:04 ` Jim Diamond
2010-04-20 17:15 ` Andreas Politz
2010-04-20 17:34 ` Jeff Clough
2010-04-21 14:26 ` Jim Diamond
2010-04-20 17:36 ` Glenn Morris
2010-04-21 14:31 ` Jim Diamond
2010-04-21 18:23 ` Stefan Monnier
2010-04-22 15:27 ` Uday S Reddy
2010-04-20 22:37 ` Tim X
2010-03-21 22:41 ` despen
2010-03-22 11:59 ` Stefan Kamphausen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x2oe01d8a51005041203q67c40c05ib11cbf61f6ea065a@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=akaiser@visi.com \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).