From: Kevin Rodgers <ihs_4664@yahoo.com>
Cc: cc-mode-help@lists.sourceforge.net
Subject: Re: cc-langs.el
Date: Fri, 29 Aug 2003 12:49:39 -0600 [thread overview]
Message-ID: <3F4FA043.7080602@yahoo.com> (raw)
In-Reply-To: E19slZL-00072q-C8@fencepost.gnu.org
Richard Stallman wrote:
> > To concretize the discussion, I think the following functions are
> > generally useful and haven't got any direct counterparts in the
> > current set:
> >
> > Sorry, that is far too much.
>
> For what reason? The work of updating the manual?
>
> I don't even want to think about that many different functions, sorry.
Martin's list has 82 functions. In comparison, lisp/files.el defines
83 functions, lisp/simple.el defines 152 function, and src/*.c defines
1,058 (Lisp) functions.
The Common Lisp functions have a well-specified interface, and adding
new functions (vs. modifying existing functions) should not affect
Emacs' behavior. What's to think about?
--
Kevin Rodgers
next prev parent reply other threads:[~2003-08-29 18:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19mCBN-0004BX-4J@fencepost.gnu.org>
2003-08-22 11:45 ` cc-langs.el Martin Stjernholm
2003-08-22 21:21 ` cc-langs.el Miles Bader
2003-08-23 4:01 ` cc-langs.el Richard Stallman
2003-08-23 13:41 ` cc-langs.el Martin Stjernholm
2003-08-24 18:00 ` cc-langs.el Richard Stallman
2003-08-26 22:03 ` cc-langs.el Martin Stjernholm
[not found] ` <E19s8Wc-0005SJ-41@fencepost.gnu.org>
2003-08-28 11:03 ` cc-langs.el Martin Stjernholm
2003-08-29 15:53 ` cc-langs.el Richard Stallman
2003-08-29 18:49 ` Kevin Rodgers [this message]
2003-08-29 23:17 ` cc-langs.el Miles Bader
2003-08-30 19:42 ` cc-langs.el Martin Stjernholm
2003-08-31 0:42 ` cc-langs.el Miles Bader
2003-09-01 2:22 ` cc-langs.el Richard Stallman
2003-09-20 23:31 ` Blessing cl functions Martin Stjernholm
2003-09-21 22:33 ` Richard Stallman
2003-09-21 23:03 ` Miles Bader
2003-08-26 18:22 cc-langs.el Wedler, Christoph
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F4FA043.7080602@yahoo.com \
--to=ihs_4664@yahoo.com \
--cc=cc-mode-help@lists.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.