unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: brettg@posteo.net
To: 37358@debbugs.gnu.org
Cc: guix-patches-bounces+brettg=posteo.net@gnu.org
Subject: [bug#37358] Add emacs-doom-themes
Date: Wed, 11 Sep 2019 20:13:43 +0200	[thread overview]
Message-ID: <1a4441f767e6fdb890cb13386c26f8f5@posteo.net> (raw)
In-Reply-To: <87woeevkwu.fsf@yahoo.de>

Hi all,

I have a copy of emacs-doom-themes in my channel here. I never pushed it 
because I didnt feel it was good enough for upstream.

It works though, feel free to tweak it and push it.

https://git.sr.ht/~brettgilio/cfg/tree/master/guix-channel/non-gnu/packages/emacs-xyz.scm#L10

On 11.09.2019 18:48, Tim Gesthuizen via Guix-patches via wrote:
> Hi,
> 
> Ludovic Courtès writes:
>> Why is this needed?
> 
> I am pretty sure that this is not what I want (did I miss a 
> build-system
> option?):
> The themes of the package are in a subdirectory that is not byte
> compiled or installed to the store when the package is build.
> The easiest workaround I could come up with is copying all .el files to
> the root of the package.
> The package is pretty useless without the theme .el files.
> 
>> I could suggest:
>> 
>>   (for-each (lambda (file)
>>               (rename-file file (string-append (dirname file) "/..")))
>>             (find-files themes))
>> 
>> … which would really move files, but it also more verbose.
> 
> A version moving the files is attached. I would prefer the copying
> version however: The files will not get installed, we are talking about
> a few kilobytes in /tmp/, and it is easier to read.
> Choose the version you like :)
> 
> Tim.

  reply	other threads:[~2019-09-11 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 16:56 [bug#37358] Add emacs-doom-themes Tim Gesthuizen via Guix-patches via
2019-09-10 22:03 ` Ludovic Courtès
2019-09-11 16:48   ` Tim Gesthuizen via Guix-patches via
2019-09-11 18:13     ` brettg [this message]
2019-09-12 21:22       ` bug#37358: " 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=1a4441f767e6fdb890cb13386c26f8f5@posteo.net \
    --to=brettg@posteo.net \
    --cc=37358@debbugs.gnu.org \
    --cc=guix-patches-bounces+brettg=posteo.net@gnu.org \
    /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).