unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Low-stress useful project
Date: Sat, 12 Aug 2006 18:23:30 +0100	[thread overview]
Message-ID: <20060812172329.GA1432@muc.de> (raw)
In-Reply-To: <E1GBuT5-0008Sx-Os@fencepost.gnu.org>

Hi, Richard!

On Sat, Aug 12, 2006 at 10:28:03AM -0400, Richard Stallman wrote:
>     With all due respect to everybody, and so on, but the Bash manual,
>     the last time I looked at it[*], didn't seem to be one of the
>     better manuals in the GNU system.  It is short on examples,
>     doesn't seem well organized, and I found it maddeningly difficult
>     to find out about basic things (how do you write a `while' loop?)
>     a few years back when I was learning bash.

> Would you like to work on improving it?  It won't magically change by
> itself.

A fair response (even if a little bit hackneyed).  I'd like to work on
it, but that would mean doing less on other things (like Emacs and CC
Mode), so I'll just leave it.

I wasn't disparaging this manual out of personal frustration or hate or
anything like that - I merely wanted anybody contemplating the task (of
doing eshell.texi) not to take over the form of bashref.texi
uncritically.

>       The bash man page is much more coherent.

> It is ok to copy the text from there, too; it will require rewriting
> into Texinfo, though.

-- 
Alan.

  reply	other threads:[~2006-08-12 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 20:18 Low-stress useful project Richard Stallman
2006-08-11  8:58 ` Alan Mackenzie
2006-08-12 14:28   ` Richard Stallman
2006-08-12 17:23     ` Alan Mackenzie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-12  7:28 Mikiya Matsuzaka
2006-08-12 22:01 ` T. V. Raman
2006-08-13  6:43 Mikiya Matsuzaka

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=20060812172329.GA1432@muc.de \
    --to=acm@muc.de \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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