all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Brett Gilio <brettg@posteo.net>
Cc: 38613@debbugs.gnu.org, maxim.cournoyer@gmail.com
Subject: bug#38613: Disabling bytecompilation on a list of files.
Date: Mon, 16 Dec 2019 00:01:36 +0100	[thread overview]
Message-ID: <0b47c65b310b0a0c9e5821070d5e4a888a8c4a58.camel@student.tugraz.at> (raw)
In-Reply-To: <8736dl5ipq.fsf@posteo.net>

Am Sonntag, den 15.12.2019, 16:26 -0600 schrieb Brett Gilio:
> [...]
> I am not sure why the file permissions are needing to be set either.
> On
> a git checkout it looks to me like they are the same as the others. I
> wonder if it might have something to do with the rename-file method
> moving the themes? Idk.
Interesting.  I wonder what would happen if we patched the files before
moving them elsewhere, given that files often are not moved in such a
manner.

> Honestly, it looks fine enough to me. At least for a draft. Does
> anybody
> have any objections or feel an urge for a need for addition of
> something
> else? I think this feature is going to be useful, especially for
> allowing workarounds in cases like this which will certainly pop up
> again in the future.
Regarding the impact, I think it should be fine if we commit this
closely before or after #38619, since that probably forces all Elisp
libraries to be rebuilt anyways (also CC'd Maxim to have a look at
this).  Hopefully at least the doom-theme autoloads compile correctly. 
WDYT?

Leo

  reply	other threads:[~2019-12-15 23:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 19:45 bug#38613: Disabling bytecompilation on a list of files Brett Gilio
2019-12-15  0:35 ` Leo Prikler
2019-12-15 22:26   ` Brett Gilio
2019-12-15 23:01     ` Leo Prikler [this message]
2019-12-15 23:18       ` Brett Gilio
2019-12-17  5:03       ` Maxim Cournoyer
2019-12-24  0:31         ` Brett Gilio
2019-12-27  5:06           ` Maxim Cournoyer
2019-12-27 23:07             ` Brett Gilio

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=0b47c65b310b0a0c9e5821070d5e4a888a8c4a58.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=38613@debbugs.gnu.org \
    --cc=brettg@posteo.net \
    --cc=maxim.cournoyer@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.