From: Sundar Vasan <vr.sundar@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>,
tiefeng wu <icebergwtf@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Learning emacs sources
Date: Thu, 30 Jul 2009 10:23:34 -0700 [thread overview]
Message-ID: <63acfd6c0907301023m418a4ec0xbb3f2b57421d5420@mail.gmail.com> (raw)
In-Reply-To: <e01d8a50907291519p7ac10d83s652850ae2f5144ca@mail.gmail.com>
On Wed, Jul 29, 2009 at 3:19 PM, Lennart
Borgman<lennart.borgman@gmail.com> wrote:
> Do you know about the bug database:
>
> http://emacsbugs.donarmstrong.com/
>
> Even if you can't solve the bugs right now, looking at them and trying
> to understand might perhaps be something that fits your mind.
I knew about it but hadn't looked through it in detail. I took another
look and saw a bug (3849) for eshell (lack of) documentation. That
would work. I saw a couple more that looked interesting. Thanks!
> Another thing to look at (that is quite a bit complicated though) is
> CEDET that is on its way into Emacs. There are plenty of things to do.
Ok, that sounds interesting. I tried ECB + CEDET about a year ago and
found it very hard to use at that point. Felt like I had to really
understand them to be able to use them instead of just being able to
use them. I was also just then starting to try out Emacs so that
probably made it worse. I haven't tried it recently though I read that
a new version of both were released.
prev parent reply other threads:[~2009-07-30 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 2:28 Learning emacs sources tiefeng wu
2009-07-29 3:22 ` Chong Yidong
2009-07-29 4:08 ` Stephen J. Turnbull
2009-07-29 10:23 ` tiefeng wu
2009-07-29 20:59 ` Sean Sieger
2009-07-30 2:45 ` Stephen J. Turnbull
2009-07-29 22:06 ` Sundar Vasan
2009-07-29 22:19 ` Lennart Borgman
2009-07-30 17:23 ` Sundar Vasan [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=63acfd6c0907301023m418a4ec0xbb3f2b57421d5420@mail.gmail.com \
--to=vr.sundar@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=icebergwtf@gmail.com \
--cc=lennart.borgman@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 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).