From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: Patch to lisp/bs.el
Date: 19 Nov 2004 13:36:47 -0500 [thread overview]
Message-ID: <jkoeht65z4.fsf@glug.org> (raw)
In-Reply-To: CHENG Gao's message of "Sat, 20 Nov 2004 01:11:40 +0800"
CHENG Gao <chenggao@gmail.com> writes:
(*bash*)Thank you for your clarification.
I am too much a ELISP newbie.
newbiehood is a precious time for the properly receptive newbie.
enjoy it and exploit it while you can. better to be a newbie on
the make than to be a wizard on the fake...
but don't believe me, wander where and as you will.
thi
next prev parent reply other threads:[~2004-11-19 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 16:13 Patch to lisp/bs.el CHENG Gao
2004-11-19 16:41 ` Andreas Schwab
2004-11-19 17:11 ` CHENG Gao
2004-11-19 18:36 ` Thien-Thi Nguyen [this message]
2004-11-21 1:10 ` Richard Stallman
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=jkoeht65z4.fsf@glug.org \
--to=ttn@glug.org \
--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).