From: simon cossar <scossar@telus.net>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: TAGS
Date: Sun, 23 Jan 2011 13:50:31 -0800 [thread overview]
Message-ID: <1295819431.19405.20.camel@sentient> (raw)
In-Reply-To: <82A89F07-5B97-4260-9985-59DF8E6721C0@gmail.com>
Thank you for your replies, I was looking everywhere for the elisp
source code - it's good to know it isn't there. I learned a lot about my
file system in the process. It would be great to see the .el files, as
I'm finding emacs lisp combined with the C-h f function surprisingly
easy to read.
Thanks again,
Simon
On Sun, 2011-01-23 at 09:24 -0600, Perry Smith wrote:
> On Jan 23, 2011, at 5:17 AM, Peter Dyballa wrote:
>
> >
> > Am 23.01.2011 um 09:12 schrieb simon cossar:
> >
> >> I am finding all sorts of .elc files. Is it possible that everything has been byte-compiled?
> >
> > To save space an installation of GNU Emacs can be done by only installing the ELC files. If you want to see the EL files, i.e., it's not enough for you what C-h f <function name> RET returns, then get the GNU Emacs source code. Which is now at #23.2.
>
> Also, it might work to post this same question to an ubuntu list asking for what to install to get the source.
>
> In case you didn't get the gist of the previous replies, there are two kinds of source: elisp and c. With a nice full install (like my Mac has), I can do C-h <function> to get the built in help. And then I'll have a link at the top that will take me to the source no matter whether it is in lisp or C. Very very nice to have.
>
> Good luck.
>
> Perry
>
next prev parent reply other threads:[~2011-01-23 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 8:12 TAGS simon cossar
2011-01-23 11:17 ` TAGS Peter Dyballa
2011-01-23 15:24 ` TAGS Perry Smith
2011-01-23 16:28 ` TAGS Peter Dyballa
2011-01-24 0:59 ` TAGS simon cossar
[not found] ` <mailman.5.1295830797.28254.help-gnu-emacs@gnu.org>
2011-01-24 3:53 ` TAGS rusi
[not found] ` <mailman.7.1295800089.26013.help-gnu-emacs@gnu.org>
2011-01-23 16:43 ` TAGS rusi
2011-01-23 21:50 ` simon cossar [this message]
[not found] ` <mailman.2.1295781488.8995.help-gnu-emacs@gnu.org>
2011-01-23 11:31 ` TAGS Alain Ketterlin
[not found] <mailman.24.1295774756.8897.help-gnu-emacs@gnu.org>
2011-01-23 9:44 ` TAGS rusi
2011-01-23 17:15 ` TAGS Memnon Anon
[not found] ` <mailman.0.1295802921.7736.help-gnu-emacs@gnu.org>
2011-01-23 17:39 ` TAGS rusi
2011-01-23 10:00 ` TAGS harven
[not found] <mailman.938.1073284523.868.help-gnu-emacs@gnu.org>
2004-01-05 7:13 ` TAGS Friedrich Dominicus
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 5:30 TAGS Jack Wang
2004-01-05 6:01 ` TAGS Eli Zaretskii
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=1295819431.19405.20.camel@sentient \
--to=scossar@telus.net \
--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.
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).