[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompat
From: |
Christopher Dimech |
Subject: |
bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible) |
Date: |
Fri, 11 Dec 2020 17:31:11 +0100 |
> Sent: Friday, December 11, 2020 at 5:05 PM
> From: "Protesilaos Stavrou" <info@protesilaos.com>
> To: "Stefan Kangas" <stefankangas@gmail.com>
> Cc: contovob@tcd.ie, 45068@debbugs.gnu.org, juri@linkov.net
> Subject: bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2
> (backward-incompatible)
>
> On 2020-12-11, 08:16 -0600, Stefan Kangas <stefankangas@gmail.com> wrote:
>
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> >>> Taking a step back, why are any themes in "etc/themes" to begin with?
> >>
> >> This question should have been asked 10 years ago, when we added that
> >> place.
> >
> > I wasn't paying attention 10 years ago, I'm afraid. :-)
> >
> >> Nowadays I think the question is what's so wrong with that
> >> place that would justify moving the files. If there are no serious
> >> problems, I'd prefer to keep using that directory for themes.
> >
> > Right. Well, I don't exactly have a strong opinion either way. But I
> > do think that we should be consistent: it would be confusing to have
> > some themes in "etc/themes" and some in "lisp/themes".
> >
> > If we can't move all themes to "lisp/themes" and we don't want to use
> > "lisp/themes" just for support files, to my mind the only remaining way
> > forward is to add some way to byte-compile (perhaps only some?) files in
> > "etc/themes". And then make sure they can be loaded, are installed with
> > Emacs, etc.
> >
> > Does that sound good, or could we do even better here?
Perhaps you can make a new location for themes, put the required functionality,
then thrash the part that handled "lisp/themes" and "etc/themes". That would
then be a long term solution.
> > Protesilaos, what do you think? Does it sound workable for you?
>
> I am fine with whatever is considered best for Emacs and am willing to
> make any changes you may consider necessary.
>
> My intent here is to contribute the latest version which satisfies the
> number one feature request I kept receiving: let the themes be
> customised uniformly.
>
> --
> Protesilaos Stavrou
> protesilaos.com
>
>
>
>
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), (continued)
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Protesilaos Stavrou, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Eli Zaretskii, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Christopher Dimech, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Eli Zaretskii, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Christopher Dimech, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Stefan Kangas, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Christopher Dimech, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Eli Zaretskii, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Christopher Dimech, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Protesilaos Stavrou, 2020/12/11
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible),
Christopher Dimech <=
- bug#45068: [PATCH] 28.0.50; Update Modus themes 1.0.2 (backward-incompatible), Christopher Dimech, 2020/12/11