unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Tim Gesthuizen <tim.gesthuizen@yahoo.de>, 33598@debbugs.gnu.org
Subject: [bug#33598] Optimizations for emacs-clang-format and emacs-clang-rename
Date: Fri, 14 Dec 2018 10:23:41 +0100	[thread overview]
Message-ID: <87r2ekea1u.fsf@ambrevar.xyz> (raw)
In-Reply-To: <871s6l9h54.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

Hi Tim!

Thanks for working on this.

I'm just a little confused about the intention, so I have a few questions.
The current package re-uses Clang source and packages clang-format.el /
clang-rename.el only.

In your implementation, you've essentially moved the 'configure phase to a
snippet.  As I understand it, this does not change anything.  What is your
reason for doing this?

You are also deleting all non-required files.  Which saves some space in /tmp
indeed, but this won't change anything to the store or the resulting
substitutes, right?  I don't mind this change, I just want to be clear about
what we are trying to achieve here :)

Last, the factorization into package-from-clang-elisp-file: this is a good idea,
and I would make it even more generic.  Simply rename your function

	package-elisp-from-package

(or something like that) and make "clang" a parameter.  Then we can use this
function in other packages like emacs-agda2-mode.

Am I making sense?  What do you think?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-12-14  9:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 13:47 [bug#33598] Optimizations for emacs-clang-format and emacs-clang-rename Tim Gesthuizen
2018-12-13 22:49 ` Ludovic Courtès
2018-12-14  9:23   ` Pierre Neidhardt [this message]
2018-12-14 10:06     ` Tim Gesthuizen
2018-12-14 10:31       ` Pierre Neidhardt
2018-12-14 11:00         ` Tim Gesthuizen
2018-12-14 12:09           ` Pierre Neidhardt
2018-12-14 12:12             ` Tim Gesthuizen
2018-12-19 17:47             ` Tim Gesthuizen
2018-12-19 17:50               ` Pierre Neidhardt
2019-01-04 22:00                 ` Tim Gesthuizen
2019-01-06 19:00                   ` Pierre Neidhardt
2019-01-06 21:29                     ` Tim Gesthuizen
2019-01-07 13:47                       ` Pierre Neidhardt
2019-01-07 14:00                         ` Pierre Neidhardt
2019-01-07 14:08                           ` Pierre Neidhardt
2019-01-07 22:10                             ` Ludovic Courtès
2019-01-07 22:14                               ` Pierre Neidhardt
2019-01-08  8:39                                 ` Ludovic Courtès
2019-01-08  8:48                                   ` Pierre Neidhardt
2019-01-08  9:53                                     ` Ludovic Courtès
2019-01-08 10:05                                       ` Pierre Neidhardt
2019-01-08 15:35                                         ` Tim Gesthuizen
2019-01-10 18:28                                         ` Tim Gesthuizen
2019-01-10 18:40                                           ` Pierre Neidhardt
2019-01-10 18:47                                             ` Tim Gesthuizen
2019-01-10 18:50                                               ` Pierre Neidhardt
2019-01-07 15:37                         ` Tim Gesthuizen

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=87r2ekea1u.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=33598@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=tim.gesthuizen@yahoo.de \
    /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).