all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Enable guix-devel-mode only in guix source files
Date: Sat, 25 Aug 2018 00:30:28 +0200	[thread overview]
Message-ID: <87y3cvgzy3.fsf@gnu.org> (raw)
In-Reply-To: <87efeqg710.fsf@gmail.com> (Alex Kost's message of "Wed, 22 Aug 2018 11:06:03 +0300")

Hello,

Alex Kost <alezost@gmail.com> skribis:

> And in general, I don't like when developers make default settings that
> are hard to "fix".  What if I don't want to use 'guix-devel-mode' at
> all?  Why do you force me to use it?
>
> That's why I disabled all these dir-locals in my emacs config:
> developers often put to ".dir-locals.el" their personal settings.  I
> just can't stand it.

I view .dir-locals as a simple way to share project-wide settings among
developers, for settings that implement conventions that the project
follows.

I was thinking of it as something to help developers get started (as in:
the editor will follow some conventions without you having to worry too
much about it), but I also understand and respect the desire to not be
“forced” and to remain in control.

Ludo’.

      reply	other threads:[~2018-08-24 22:30 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
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 [this message]

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