all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: .dir-locals.el vs. guix-devel-mode
Date: Tue, 29 Sep 2015 13:22:18 +0200	[thread overview]
Message-ID: <871tdh1ndh.fsf@T420.taylan> (raw)
In-Reply-To: <87d1x1jxhi.fsf@gmail.com> (Alex Kost's message of "Tue, 29 Sep 2015 14:06:33 +0300")

Alex Kost <alezost@gmail.com> writes:

> Taylan Ulrich "Bayırlı/Kammer" (2015-09-28 23:05 +0300) wrote:
>
>> Alex Kost <alezost@gmail.com> writes:
>>
>>> [...]
>>>
>>> More generally, I'm strongly against using "eval" in .dir-locals.  IMO
>>> this file should be used only to set local variables, and ideally it
>>> shouldn't evaluate an arbitrary code.
>>
>> Just to clarify: I suppose you mean using eval for things other than
>> which Emacs can automatically determine to be safe.  E.g.
>>
>>     (eval . (put 'foo 'scheme-indent-function <n>))
>>
>> for integer <n> is safe; Emacs will eval that silently if I'm not
>> mistaken.
>
> Actually I don't like .dir-locals.el in general.  I consider it a
> workaround for the case when there are no appropriate major/minor modes
> for editing the project files.

I agree a full guix-devel minor mode might be a good idea, but a
passerby contributor or newcomer shouldn't need to know about it IMO.
It will seem like an additional hurdle to them.  If the newcomer sticks
around, they'll find out and use the mode eventually, but first
impressions matter a lot.

For that reason I'd use .dir-locals.el to its limits, i.e. so long as
the user isn't bothered with the unsafe warning.  (So that would
actually mean using it less than how much we use it right now...)

Taylan

  reply	other threads:[~2015-09-29 11:22 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 [this message]
2015-09-29 19:16         ` Ludovic Courtès
2015-10-01 21:10           ` Alex Kost
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=871tdh1ndh.fsf@T420.taylan \
    --to=taylanbayirli@gmail.com \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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.