all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: help-guix@gnu.org
Subject: Re: Enable guix-devel-mode only in guix source files
Date: Mon, 20 Aug 2018 22:57:29 +0300	[thread overview]
Message-ID: <87r2isvmja.fsf@gmail.com> (raw)
In-Reply-To: <cu7bm9y6xgf.fsf@systemreboot.net> (Arun Isaac's message of "Sun, 19 Aug 2018 23:38:32 +0530")

Arun Isaac (2018-08-19 23:38 +0530) wrote:

>>> A better approach might be to add it to .dir-locals.el upstream.  What do you
>>> people think?
>>
>> I think the less is added to "dir-locals" the better.  Especially, there
>> shouldn't be any functions there in my opinion.
>
> Thanks, Alex and Pierre, for your replies. But, why is adding to
> dir-locals not a good idea?

It's not a good idea only in my opinion :-)

I personally don't like when someone decides what settings I should use
so much, that I disable all these dir-locals stuff completely (using
'enable-dir-local-variables' variable).

But if I understood this situation correctly, Pierre suggested to:

- add a function to the Guix ".dir-locals.el" (does dir-locals support
  functions at all?)

- the function to set up a third-party package (Emacs-Guix)!  Why Guix
  should do it?

Both these points doesn't look right to me.

-- 
Alex

  reply	other threads:[~2018-08-20 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 16:14 Enable guix-devel-mode only in guix source files Arun Isaac
2018-08-17 16:44 ` Pierre Neidhardt
2018-08-17 19:46   ` Alex Kost
2018-08-19 18:08     ` Arun Isaac
2018-08-20 19:57       ` Alex Kost [this message]
2018-08-20 22:18         ` Pierre Neidhardt
2018-08-21 15:15           ` Alex Kost
2018-08-21 15:23             ` Pierre Neidhardt
2018-08-21 17:12               ` Oleg Pykhalov
2018-08-22  8:06               ` Alex Kost
2018-08-24 22:30                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2isvmja.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=arunisaac@systemreboot.net \
    --cc=help-guix@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.