all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: .dir-locals.el vs. guix-devel-mode
Date: Fri, 02 Oct 2015 00:10:15 +0300	[thread overview]
Message-ID: <87d1wyqoqw.fsf@gmail.com> (raw)
In-Reply-To: 87r3lhxchs.fsf@gnu.org

Ludovic Courtès (2015-09-29 22:16 +0300) wrote:

> Alex Kost <alezost@gmail.com> skribis:
>
[...]
>> So I think .dir-locals.el is not the proper place for indentation rules.
>> IMHO they should be moved to "guix-devel.el" and the manual should
>> recommend using 'guix-devel-mode' for editing guix package files as it
>> provides the proper indenting, highlighting and some useful key
>> bindings.
>
> Yes, but I agree with Taylan: a passerby should get a reasonable setup
> in place automatically.  That’s what I like about .dir-locals.el: it
> allows you to make sure that a minimum set of rules is in place, which
> in turn means that patches are more likely to come out right, which
> means less frustration and increased happiness.
>
> Using eval + load in .dir-locals.el is indeed ugly though.  So, for lack
> of a better solution, I’m fine having some of the rules duplicated.
> Specifically, rules for ‘package’, ‘origin’, ‘operating-system’,
> ‘substitute*’, ‘with-store’, ‘with-monad’, ‘run-with-store’,
> ‘run-with-state’, and ‘m…’.
>
> How does that sound?

I'd like to have them in "guix-devel.el", but I don't see the reason for
duplicating.  I think they either should be placed in "guix-devel.el"
(surely the right thing for me :-)) or stay in ".dir-locals.el" (I'm
afraid the right thing for the most :-().

Why do you suggest the duplication?

-- 
Ceterum censeo +Carthaginem+ ".dir-locals.el" esse delendam

  reply	other threads:[~2015-10-01 21:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  8:05 [PATCH] emacs: devel: Highlight 'modify-phases' keywords Alex Kost
2015-09-25 19:22 ` Ludovic Courtès
2015-09-26 19:48   ` Alex Kost
2015-09-27 20:29     ` Ludovic Courtès
2015-09-28 12:26       ` .dir-locals.el vs. guix-devel-mode Alex Kost
2015-09-28 20:05         ` Taylan Ulrich Bayırlı/Kammer
2015-09-29 11:06           ` Alex Kost
2015-09-29 11:22             ` Taylan Ulrich Bayırlı/Kammer
2015-09-29 19:16         ` Ludovic Courtès
2015-10-01 21:10           ` Alex Kost [this message]
2015-10-01 21:34             ` Ludovic Courtès
2015-10-02 12:46               ` Alex Kost
2015-10-02 12:51                 ` Ludovic Courtès
2015-10-02 17:25                   ` Alex Kost
2015-10-12  9:33                   ` [PATCH] emacs: devel: Add indentation rules Alex Kost
2015-10-13  9:45                     ` Ludovic Courtès
2015-10-13 17:50                       ` Alex Kost
2015-10-14 20:00                         ` Ludovic Courtès
2015-10-15 17:42                           ` Alex Kost
2015-10-01 21:39             ` .dir-locals.el vs. guix-devel-mode Mathieu Lirzin

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=87d1wyqoqw.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 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.