all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Ryo Furue <ryofurue@gmail.com>
Cc: 21667@debbugs.gnu.org
Subject: bug#21667: 24.5; color-theme-buffer-local package misses a dependency
Date: Sun, 11 Oct 2015 18:28:25 -0700 (PDT)	[thread overview]
Message-ID: <a31944f4-c2fb-4435-a455-d972f2a67cc9@default> (raw)
In-Reply-To: <CAGKoo-yDLr823oH6RJGm+5HLxsHG1zu=-KOW4wrAXHiWuyirXQ@mail.gmail.com>

> For my education, may I ask which part of the emacs package system
> (package.el ?) belongs to emacs proper?  The whole thing?  It's
> always hard to know which part of a big system (another example is LaTeX)
> is maintained by whom.

Someone else can answer that better than I.  But I think that
all of the code involved specifically with accessing, downloading,
and installing Emacs libraries belongs to Emacs.  But perhaps it
also depends on what you really mean - by "belong" and by "Emacs
proper", for instance.  Certainly `package.el' is the heart of
what is involved, if it is not all of it, and that is part of
GNU Emacs as distributed.

> > It is unfortunate that when Emacs added "custom" themes it
> > introduced a lot of confusion wrt custom themes vs color themes.
> > This was compounded by some (rash) statements that the former
> > somehow replaces the latter.  The two are different, with only
> > some overlapping features.
> [. . .]
> 
> So, are both"theming systems" themselves part of emacs proper, even
> if each theme is 3rd party?

Dunno what "Emacs proper" means; sorry.  `color-theme.el' is
not included as part of GNU Emacs.  It is a 3rd-party library.





      reply	other threads:[~2015-10-12  1:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  9:46 bug#21667: 24.5; color-theme-buffer-local package misses a dependency Ryo Furue
2015-10-11 18:16 ` Drew Adams
2015-10-12  1:07   ` Ryo Furue
2015-10-12  1:28     ` Drew Adams [this message]

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=a31944f4-c2fb-4435-a455-d972f2a67cc9@default \
    --to=drew.adams@oracle.com \
    --cc=21667@debbugs.gnu.org \
    --cc=ryofurue@gmail.com \
    /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.