From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Olwe Melwasul <hercynianforest@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Do we need a "Stevens" book?
Date: Fri, 30 Jul 2010 14:28:17 +0200 [thread overview]
Message-ID: <87sk31taqm.fsf@ambire.localdomain> (raw)
In-Reply-To: <87sk32sscx.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Thu, 29 Jul 2010 08:40:46 +0200")
() Thien-Thi Nguyen <ttn@gnuvola.org>
() Thu, 29 Jul 2010 08:40:46 +0200
Afar dilutes this. Stop it.
This was uncalled for. I apologize for the tone.
WRT comint, the main message still stands, however. Why don't you take
a look at comint.el and post specific questions about what you find?
Consider it a shared exercise in (re-)searching a future "Hacking Emacs"
book. The discussion on this mailing list (apart from my chilipepper
pining headache induced vapidity) could be the start of something.
next prev parent reply other threads:[~2010-07-30 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 16:42 Do we need a "Stevens" book? Olwe Melwasul
2010-07-28 17:47 ` 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 [this message]
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=87sk31taqm.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=help-gnu-emacs@gnu.org \
--cc=hercynianforest@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.
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.