From: Alison Chaiken <alison@she-devel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
"Geyslan G . Bem" <geyslan@gmail.com>,
Tiago Natel de Moura <tiago4orion@gmail.com>,
Joe Perches <joe@perches.com>, Li Yang <leo@zh-kernel.org>
Subject: Re: [PATCH] Documentation/CodingStyle: Use directory-local variables for emacs
Date: Sat, 05 Jan 2019 11:58:15 -0800 [thread overview]
Message-ID: <84ce7ee302856836b922cfe0ddf2a74e@she-devel.com> (raw)
In-Reply-To: <1546641550.83374.8.camel@acm.org>
On 2019-01-04 14:39, Bart Van Assche wrote:
>> As a general comment, I personally think that it worth to mention the
>> fact
>> that the user can take this code (actually part of it) and put it in a
>> .dir-
>> locals.el file in the top-level directory.
>
> I'm not sure we should recommend this. Settings in ~/.emacs are not
> affected
> by git clean -f -x but .dir-locals.el is removed by that command.
Why not add the file to .gitignore, possibly in a separate patch?
-- Alison
---
Alison Chaiken alison@she-devel.com
http://she-devel.com
The real trolley problem is that trolleys are underfunded. -- Alex Roy
next prev parent reply other threads:[~2019-01-05 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2019-01-04 22:10 ` [PATCH] Documentation/CodingStyle: Use directory-local variables for emacs Federico Vaga
2019-01-04 22:39 ` Bart Van Assche
2019-01-05 19:58 ` Alison Chaiken [this message]
2019-01-05 21:04 ` 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=84ce7ee302856836b922cfe0ddf2a74e@she-devel.com \
--to=alison@she-devel.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=tiago4orion@gmail.com \
--cc=willy@infradead.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.
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).