From: Olwe Melwasul <hercynianforest@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Do we need a "Stevens" book?
Date: Wed, 28 Jul 2010 11:42:14 -0500 [thread overview]
Message-ID: <AANLkTim-4Qv06jW1H-GeuDCqpW4nTx+wDH2CShoNci=1@mail.gmail.com> (raw)
I've not gotten very far with this idea; no one seems interested, but
I'll try it here anyway...
It seems to me that Emacs needs a W. Richard Stevens-style book. As
you may know, Stevens wrote the "Advanced Programming in the UNIX(R)
Environment" textbook that many of us used in college. Or maybe Emacs
needs something along the lines of the many "Linux gnarly/wooly
internals" books. Anyway, I would love to see a book that got into the
nitty-gritty of Emacs/elisp -- just like you see discussed here every
day on the help-gnu-emacs list.
Here's an example: comint. How do you effectively use comint? When
should you use comint? Okay, I can Google around and find one-off blog
discussions here and there about comint; I can read them all; I can
get confused; I can kludge something together ... and then find out
later that what I've done (as well as bloggers A, B, and C) is really
not "best practice" use of comint, i.e., that how I've used comint is
overkill or could have been done much simpler with <some other>.el.
Wouldn't it be nice to have one go-to source/book that thrashed out
comint usage once and for all?
Just skimming through all the elisp material (books, Internet, etc.),
it seems like a hodge-podge on a continuum between gems and junk just
waiting for a clear-speaking Richard Stevens to whip it all into
shape. Sure, the "official" texts will get you pretty far, but no way
are you ready to be a "best-practices" guru. The printed books seem
more like a "cookbook" than a real Stevens-style book. Maybe I'm all
wrong, but I think I like what the Racket/PLT people are doing. They
seem to be whipping the Scheme hodge-podge into a decent
best-practices, best-tools order.
Personally I've been admiring Emacs from afar for quite some time. I'm
really an Emacs/elisp newbie, but I've got a writing/technical writing
background. If what I'm saying strikes a chord, maybe I could be a
receiver/collector of a "best-practices-slash-wooly internals" sorta
book project. It would be a free/GNU sorta thing of course ... and
please don't say "I don't think there'd be enough interest in it."
Olwe
next reply other threads:[~2010-07-28 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 16:42 Olwe Melwasul [this message]
2010-07-28 17:47 ` Do we need a "Stevens" book? Andreas Röhler
2010-07-28 17:48 ` Richard Riley
2010-07-29 6:40 ` Thien-Thi Nguyen
2010-07-30 12:28 ` Thien-Thi Nguyen
2010-07-31 4:47 ` Ken Hori
[not found] ` <mailman.0.1280385826.20966.help-gnu-emacs@gnu.org>
2010-07-29 9:50 ` rustom
2010-07-29 10:02 ` Elena
[not found] ` <35282104-5b51-4ba4-8745-4fae239ce0ee@q21g2000prm.googlegroups.com>
2010-07-30 5:29 ` Fren Zeee
2010-07-31 5:47 ` have you read emacs manual cover to cover?; (was Do we need a "Stevens" book?) Xah Lee
[not found] ` <63e9cab8-17da-4f1a-b055-e172a3ffeb47@o7g2000prg.googlegroups.com>
2010-08-08 12:02 ` Xah Lee
[not found] <mailman.1.1280335348.2485.help-gnu-emacs@gnu.org>
2010-07-28 17:01 ` Do we need a "Stevens" book? Pascal J. Bourguignon
2010-07-28 23:15 ` Stefan Monnier
2010-08-01 17:07 ` Joseph Brenner
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='AANLkTim-4Qv06jW1H-GeuDCqpW4nTx+wDH2CShoNci=1@mail.gmail.com' \
--to=hercynianforest@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.