From: Xue Fuqiao <xfq.free@gmail.com>
To: Josh <josh@foxtail.org>
Cc: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>,
"Stephen Berman" <stephen.berman@gmx.net>,
"Michael Albinus" <michael.albinus@gmx.de>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: About `<prefix>--' (was Re: filenotify.el)
Date: Fri, 28 Jun 2013 11:00:35 +0800 [thread overview]
Message-ID: <CAAF+z6G5Wwz8Vyc-7EnmThJDi+6ayU==VANQhp+OQtxpR6Hx+A@mail.gmail.com> (raw)
In-Reply-To: <CANdFEAHHs7rua-Ytgi7OUo4NS9y8PfredMBqEEd6zFQ_x4_xyQ@mail.gmail.com>
On Fri, Jun 28, 2013 at 7:19 AM, Josh <josh@foxtail.org> wrote:
> It would be great if more of these generally useful functions were
> "promoted" from the libraries where they originated into the core of
> Emacs, stripped of package prefixes and properly documented in the
> Emacs or Elisp info manuals in order to make them more discoverable
> for use elsewhere. Doubtless many wheels have been reinvented after
> failed searches for functionality that already ships with Emacs.
> Users' interest in a richer set of elisp building blocks is evident
> from the existence and popularity of libraries such as Magnar Sveen's
> dash[0] ("a modern list library for emacs") and s[1] ("the long lost
> Emacs string manipulation library"). IMO it would be a worthwhile
> goal to move toward shipping canonical implementations of these
> building blocks with Emacs. What do others think?
Agreed. XOR is also an example. Some generally useful features have
been added to core Emacs Lisp recently (e.g., generalized variables),
and more ones are expected, I think.
--
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/
next prev parent reply other threads:[~2013-06-28 3:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 12:02 filenotify.el Michael Albinus
2013-06-25 16:25 ` filenotify.el Rüdiger Sonderfeld
2013-06-25 19:00 ` filenotify.el Michael Albinus
2013-06-25 19:20 ` filenotify.el Eli Zaretskii
2013-06-25 19:27 ` filenotify.el Michael Albinus
2013-06-25 20:14 ` filenotify.el Eli Zaretskii
2013-06-26 6:06 ` filenotify.el Michael Albinus
2013-06-26 0:11 ` filenotify.el Stefan Monnier
2013-06-26 6:21 ` filenotify.el Michael Albinus
2013-06-26 13:04 ` filenotify.el Stefan Monnier
2013-06-26 14:15 ` filenotify.el Michael Albinus
2013-06-26 14:28 ` filenotify.el Stefan Monnier
2013-06-26 14:37 ` filenotify.el Michael Albinus
2013-06-26 15:57 ` filenotify.el Eli Zaretskii
2013-06-26 19:59 ` filenotify.el Stefan Monnier
2013-06-26 20:28 ` filenotify.el Michael Albinus
2013-06-26 0:45 ` filenotify.el Rüdiger Sonderfeld
2013-06-26 6:40 ` filenotify.el Michael Albinus
2013-06-26 7:50 ` About `<prefix>--' (was Re: filenotify.el) Stephen Berman
2013-06-26 13:06 ` Stefan Monnier
2013-06-26 22:36 ` Stephen Berman
2013-06-27 1:39 ` Stefan Monnier
2013-06-27 23:19 ` Josh
2013-06-28 3:00 ` Xue Fuqiao [this message]
2013-06-28 22:54 ` Stefan Monnier
2013-06-28 23:50 ` Xue Fuqiao
2013-06-29 2:06 ` Stefan Monnier
2013-06-28 21:59 ` Richard Stallman
2013-06-30 18:50 ` Josh
2013-06-27 12:18 ` filenotify.el (2) Michael Albinus
2013-07-04 9:54 ` Michael Albinus
2013-07-17 13:52 ` filenotify.el Rüdiger Sonderfeld
2013-07-17 14:54 ` filenotify.el Michael Albinus
2013-07-17 16:21 ` filenotify.el Rüdiger Sonderfeld
2013-07-18 10:10 ` filenotify.el Michael Albinus
2013-07-22 18:17 ` filenotify.el Davis Herring
2013-07-22 18:28 ` filenotify.el Michael Albinus
2013-07-22 19:00 ` filenotify.el Stefan Monnier
2013-07-23 6:57 ` filenotify.el Michael Albinus
2013-07-23 13:08 ` filenotify.el Stefan Monnier
2013-07-23 13:34 ` filenotify.el Michael Albinus
2013-07-23 13:57 ` filenotify.el Stefan Monnier
2013-07-23 14:13 ` filenotify.el Michael Albinus
2013-07-23 14:23 ` filenotify.el Stefan Monnier
2013-07-23 15:31 ` filenotify.el Davis Herring
2013-07-24 9:14 ` filenotify.el Michael Albinus
2013-08-02 7:10 ` filenotify.el Michael Albinus
2013-07-24 14:01 ` filenotify.el Michael Albinus
2013-07-23 16:10 ` filenotify.el Glenn Morris
2013-07-23 16:58 ` filenotify.el Michael Albinus
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='CAAF+z6G5Wwz8Vyc-7EnmThJDi+6ayU==VANQhp+OQtxpR6Hx+A@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=josh@foxtail.org \
--cc=michael.albinus@gmx.de \
--cc=ruediger@c-plusplus.de \
--cc=stephen.berman@gmx.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 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).