From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: tutorial or guidebook text for some complex topics
Date: Tue, 24 Oct 2006 13:42:24 -0400 [thread overview]
Message-ID: <E1GcQIC-00045h-TT@fencepost.gnu.org> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBKENCDFAA.drew.adams@oracle.com>
There are a few fundamental data structures that Emacs uses that are quite
complex and variable in form. I'm thinking of things like keymaps (including
menus), font-lock-keywords, and faces/text properties.
I did a lot of work on the keymap documentation in response
to your last suggestion. Is there any part of it which is
still insufficient?
I think the documentation of font-lock-keywords is complete.
I agree it is hard to grasp, but I don't know how to make
it clearer. Does anyone else have an idea?
As for faces and text properties, they are veryu simple structurally.
They are just plists. What aspect of them do you find complex?
next prev parent reply other threads:[~2006-10-24 17:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 18:35 tutorial or guidebook text for some complex topics Drew Adams
2006-10-23 19:59 ` Stefan Monnier
2006-10-23 21:14 ` Drew Adams
2006-10-23 21:46 ` Nick Roberts
2006-10-23 21:58 ` Drew Adams
2006-10-23 22:54 ` Nick Roberts
2006-10-23 23:24 ` Drew Adams
2006-10-24 0:13 ` Nick Roberts
2006-10-24 7:06 ` David Kastrup
2006-10-24 7:44 ` David Kastrup
2006-10-24 20:46 ` Drew Adams
2006-10-24 20:45 ` Drew Adams
2006-10-23 23:33 ` Robert J. Chassell
2006-10-24 17:42 ` Richard Stallman
2006-10-24 20:51 ` Drew Adams
2006-10-23 22:08 ` David Kastrup
2006-10-24 17:42 ` Richard Stallman
2006-10-24 23:49 ` Stefan Monnier
2006-10-23 20:01 ` Eli Zaretskii
2006-10-23 21:19 ` Drew Adams
2006-10-24 17:42 ` Richard Stallman [this message]
2006-10-24 19:31 ` Drew Adams
2006-10-25 18:03 ` Richard Stallman
2006-10-25 18:21 ` Drew Adams
2006-10-26 8:52 ` 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=E1GcQIC-00045h-TT@fencepost.gnu.org \
--to=rms@gnu.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).