all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Adam Kandur <kefironpremise@gmail.com>, 55164@debbugs.gnu.org
Subject: [bug#55164] [PATCH] gnu: Add emacs-sanityinc-tomorrow.
Date: Fri, 13 May 2022 20:47:05 +0200	[thread overview]
Message-ID: <bb85e9fe250ce9a2397d87b3cb9a02cb0a7eb060.camel@gmail.com> (raw)
In-Reply-To: <20220428112623.23172-1-kefironpremise@gmail.com>

Hi,

Am Donnerstag, dem 28.04.2022 um 14:26 +0300 schrieb Adam Kandur:
> [...]
> +    (synopsis "A set of comprehensive Emacs color themes based on
> Chris Kempson's 'tomorrow' themes")
Pretty long synopsis, don't you think?  Also note that "A" and "The"
are usually frowned upon at the start of a synopsis.
> +    (description
> +     "An Emacs version of Chris Kempson's 'Tomorrow' themes,with
> much
> +more extensive face definitions than the 'official' Emacs variant.
> +The themes work with both the built-in theming support in recent
> Emacsen,
> +and via the traditional color-theme.el add-on library in older
> versions,
> +so use whichever you prefer.")
Note that Guix doesn't have "Chris Kempson's 'Tomorrow' themes", at
least not the version this package is referring to.  We do have base16-
themes, which have an updated version of tomorrow for comparison.
Also, the description should consist of full sentence.  The usual
workaround here is "This package provides [...]", but you can more or
less feel free to do whatever as long as it's actually describing the
package and not marketing it instead.  For instance, "SanityInc
Tomorrow provides variations of Chris Kempson's Tomorrow theme (which
themselves are distributed as part of @code{emacs-base16-themes}) with
[distinctive features]".

Cheers




      reply	other threads:[~2022-05-13 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 11:26 [bug#55164] [PATCH] gnu: Add emacs-sanityinc-tomorrow Adam Kandur
2022-05-13 18:47 ` Liliana Marie Prikler [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=bb85e9fe250ce9a2397d87b3cb9a02cb0a7eb060.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=55164@debbugs.gnu.org \
    --cc=kefironpremise@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/guix.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.