all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: CHENG Gao <chenggao@royau.me>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: loccur
Date: Thu, 31 Dec 2015 13:57:18 +0800	[thread overview]
Message-ID: <m21ta317pd.fsf@royau.me> (raw)
In-Reply-To: m24meziq17.fsf@newartisans.com

*On Wed, 30 Dec 2015 13:29:24 -0800
* Also sprach John Wiegley <jwiegley@gmail.com>:

>>>>>> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> Any reason to go into Elpa and not core, btw?
>
> Packages which core does not depend on go into ELPA. More things will
> go into ELPA in future, so we're starting that trend now.

I like this trend.

Just a little curious about definition of "core".
It means files under lisp/emacs-lisp/ and lisp/?
Grep shows several under lisp/emacs-lisp/ and many under lisp/ do
(featurep 'xemacs) check. Are they necessary still? I understand
standalone packages supporting both Emacs and Xemacs need this, but
these files I wonder.

And that'll be good if files under lisp/ be categorized under subdirs
suck as core/, util/ etc. Just my wish.




  parent reply	other threads:[~2015-12-31  5:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 21:08 [ELPA] New package: loccur Alexey Veretennikov
2015-12-30 21:10 ` John Wiegley
2015-12-30 23:27   ` Alexey Veretennikov
2015-12-30 21:22 ` Marcin Borkowski
2015-12-30 21:29   ` John Wiegley
2015-12-30 21:32     ` Lars Magne Ingebrigtsen
2015-12-30 21:39       ` John Wiegley
2015-12-30 22:41         ` Artur Malabarba
2015-12-31  0:20           ` John Wiegley
2015-12-31  5:57     ` CHENG Gao [this message]
2015-12-31  8:49       ` Michael Albinus
2015-12-31  9:36         ` CHENG Gao
2015-12-31 14:38         ` Rasmus
2015-12-31  0:30 ` Juri Linkov
2015-12-31  3:14   ` daniel sutton
2015-12-31 12:49     ` Alexey Veretennikov

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=m21ta317pd.fsf@royau.me \
    --to=chenggao@royau.me \
    --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 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.