unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: emacs-devel@gnu.org
Cc: Protesilaos Stavrou <info@protesilaos.com>
Subject: Re: [elpa] externals/ef-themes b6fc326946: Add ef-bio theme
Date: Sun, 02 Oct 2022 11:50:52 +0000	[thread overview]
Message-ID: <87ill24f6r.fsf@posteo.net> (raw)
In-Reply-To: <20221002055734.E8E12C0004A@vcs2.savannah.gnu.org> (ELPA Syncer's message of "Sun, 2 Oct 2022 01:57:34 -0400 (EDT)")

ELPA Syncer <elpasync@gnu.org> writes:

> branch: externals/ef-themes
> commit b6fc32694646c65adbf1ed6d3d7bfddf55e16273
> Author: Protesilaos Stavrou <info@protesilaos.com>
> Commit: Protesilaos Stavrou <info@protesilaos.com>
>
>     Add ef-bio theme
>     
>     Read the announcement, which also includes screen shots:
>     <https://protesilaos.com/codelog/2022-10-02-ef-themes-bio-theme/>.
>     
>     Enjoy your new theme :)

Out of curiosity, what is your long-term plan for ef-themes?  Do you
plan to add more and more variations, or is there some upper bound you
plan to approach?  It seems to me that maintenance will become more and
more difficult, and it would be a shame to see the nice themes
abandoned, because of it becoming infeasible to properly test all the
changes.

Also, do you think that splitting up the theme into multiple packages
would be a good idea?



       reply	other threads:[~2022-10-02 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166469025461.5911.14047450412101243173@vcs2.savannah.gnu.org>
     [not found] ` <20221002055734.E8E12C0004A@vcs2.savannah.gnu.org>
2022-10-02 11:50   ` Philip Kaludercic [this message]
2022-10-02 12:18     ` [elpa] externals/ef-themes b6fc326946: Add ef-bio theme Protesilaos Stavrou
2022-10-02 16:50       ` Philip Kaludercic

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=87ill24f6r.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.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 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).