From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: zyk <zhouyinkun@19lou.com>
Cc: emacs-devel@gnu.org
Subject: Re: read eamcs source code
Date: Fri, 09 Jan 2009 11:04:56 +0100 [thread overview]
Message-ID: <87aba0aj7b.fsf@ambire.localdomain> (raw)
In-Reply-To: <495AFDA7.4030000@19lou.com> (zyk's message of "Wed, 31 Dec 2008 13:05:43 +0800")
() zyk <zhouyinkun@19lou.com>
() Wed, 31 Dec 2008 13:05:43 +0800
Any ideas ?
If you want to learn well, you need to know your learning style.
What is your learning style?
thi
prev parent reply other threads:[~2009-01-09 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 5:05 read eamcs source code zyk
2008-12-31 14:53 ` Lennart Borgman
2008-12-31 15:07 ` zyk
2008-12-31 15:47 ` Stephen J. Turnbull
2008-12-31 17:17 ` Stefan Monnier
2008-12-31 18:12 ` zyk
2009-01-09 10:04 ` Thien-Thi Nguyen [this message]
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=87aba0aj7b.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=zhouyinkun@19lou.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 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).