From: Jani Nikula <jani.nikula@linux.intel.com>
To: Federico Vaga <federico.vaga@vaga.pv.it>,
Bart Van Assche <bvanassche@acm.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, "Geyslan G . Bem" <geyslan@gmail.com>,
Tiago Natel de Moura <tiago4orion@gmail.com>,
Alison Chaiken <alison_chaiken@mentor.com>,
Joe Perches <joe@perches.com>, Zhang Le <r0bertz@gentoo.org>,
Li Yang <leo@zh-kernel.org>
Subject: Re: [PATCH] Documentation/CodingStyle: Move emacs settings into .dir-locals.el
Date: Fri, 04 Jan 2019 13:18:58 +0200 [thread overview]
Message-ID: <87k1jk8ycd.fsf@intel.com> (raw)
In-Reply-To: <4009470.9o5kGc7Prg@harkonnen>
On Fri, 04 Jan 2019, Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> Isn't it better if we collect such configuration files into a
> dedicated directory (where exactly?) instead of putting them in the
> top-level one? Then, the developer has to copy/link the configuration
> file into the top-level directory.
>
> If we accept emacs configuration files in the top-level directory we
> will have to accept also the ones from other editors (of course, when
> they support local configurations). In addition, probably, there are
> people who do not want to use local configurations.
Fully agreed.
Also, you probably do not wish the file to change when you switch
branches with different upstream baselines. Or deal with possible emacs
version dependent changes. I do like having the example in the kernel
tree, but let the users deal with actually using the file. Placing the
file at the top level makes it harder for users to have a file of their
own there. This from an emacs user.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-01-04 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 0:39 [PATCH] Documentation/CodingStyle: Move emacs settings into .dir-locals.el Bart Van Assche
2019-01-04 2:12 ` Matthew Wilcox
2019-01-04 16:06 ` Bart Van Assche
2019-01-04 9:44 ` Federico Vaga
2019-01-04 11:18 ` Jani Nikula [this message]
2019-01-04 16:40 ` Bart Van Assche
2019-01-07 10:29 ` Jani Nikula
2019-01-04 16:32 ` Bart Van Assche
2019-01-04 16:41 ` Jonathan Corbet
2019-01-04 18:26 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2019-01-04 21:08 [PATCH] Documentation/CodingStyle: Use directory-local variables for emacs Bart Van Assche
2019-01-04 21:08 ` [PATCH] Documentation/CodingStyle: Move emacs settings into .dir-locals.el Bart Van Assche
2019-01-04 21:11 ` Bart Van Assche
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=87k1jk8ycd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alison_chaiken@mentor.com \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=geyslan@gmail.com \
--cc=joe@perches.com \
--cc=leo@zh-kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=r0bertz@gentoo.org \
--cc=tiago4orion@gmail.com \
/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.
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 NNTP newsgroup(s).