From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Tristan Cottam <tristan@cott.am>, 67198@debbugs.gnu.org
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Andrew Tropin <andrew@trop.in>
Subject: [bug#67198] [PATCH] gnu: Add emacs-adwaita-dark-theme
Date: Wed, 15 Nov 2023 19:40:14 +0100 [thread overview]
Message-ID: <f2983db552ee7d5a7b0930caa9eb6969e310c087.camel@gmail.com> (raw)
In-Reply-To: <0e781a8a92a4ac67cb659643c2a5a42acc0b9e87.1700051896.git.tristan@cott.am>
Am Mittwoch, dem 15.11.2023 um 13:38 +0100 schrieb Tristan Cottam:
> * gnu/packages/emacs-xyz.scm (emacs-adwaita-dark-theme): New
> variable.
>
> Change-Id: Id6e6d0d6aa27e7c1cc6ec0fc11c3a5f09231d751
> ---
> gnu/packages/emacs-xyz.scm | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
> index be7ffd1f37..b0c5f10b96 100644
> --- a/gnu/packages/emacs-xyz.scm
> +++ b/gnu/packages/emacs-xyz.scm
> @@ -1995,6 +1995,29 @@ (define-public emacs-suneater-theme
> theme but now takes more inspiration from the Nano theme.")
> (license license:gpl3+)))
>
> +(define-public emacs-adwaita-dark-theme
> + (let ((commit "a97d5d5f5657a52c3b4c4b146b4d307dfb1a7a74")
> + (revision "0"))
> + (package
> + (name "emacs-adwaita-dark-theme")
> + (version (git-version "1.1.0" revision commit))
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url
> "https://gitlab.com/jessieh/adwaita-dark-theme")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> +
> "0g8fjqmz805fhqspbzmpvb90kpzwigl4z56bkykywgy2cwb9ljzh"))))
> + (build-system emacs-build-system)
> + (home-page "https://gitlab.com/jessieh/adwaita-dark-theme")
> + (synopsis "Adwaita-inspired dark color scheme for Emacs")
> + (description
> + "adwaita-dark-theme is an Adwaita-inspired dark color scheme
> for
> +Emacs.")
Don't start a description with lower case. If you really need to, use
@code or similar (discouraged here imho), otherwise good ol' "This
package provides" has your back.
> + (license license:gpl2+))))
> +
> (define-public emacs-treepy
> (package
> (name "emacs-treepy")
>
> base-commit: bd0f2173210416e86281c1de8789e7cdab66dd57
> prerequisite-patch-id: 5e36e77f4fa1848dbd20c2e5d5cec31d2473c2a8
Cheers
next prev parent reply other threads:[~2023-11-15 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 12:38 [bug#67198] [PATCH] gnu: Add emacs-adwaita-dark-theme Tristan Cottam via Guix-patches via
2023-11-15 17:11 ` Nicolas Goaziou via Guix-patches via
2023-11-15 18:41 ` Liliana Marie Prikler
2023-11-15 20:07 ` Nicolas Goaziou via Guix-patches via
2023-11-15 18:40 ` Liliana Marie Prikler [this message]
2023-11-15 21:59 ` [bug#67198] [PATCH v2] " Tristan Cottam via Guix-patches via
2023-11-18 11:31 ` [bug#67198] [PATCH v3] " Tristan Cottam via Guix-patches via
2024-01-07 15:04 ` bug#67198: " Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2983db552ee7d5a7b0930caa9eb6969e310c087.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=67198@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=tristan@cott.am \
/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/guix.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).