[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Two problems with directory-local variables
From: |
Phil Sainty |
Subject: |
Re: Two problems with directory-local variables |
Date: |
Tue, 18 Sep 2018 12:04:44 +1200 |
User-agent: |
Orcon Webmail |
On 2018-09-18 11:15, Juri Linkov wrote:
When I tried [add-dir-local-variable] it correctly added
((nil
(eval message "hello")))
On this note, while I don't use the commands myself, I've often wished
that add-dir-local-variable would generate the dotted-pair syntax,
because I've often seen confusion about the syntax of dir-locals arising
from dotted vs non-dotted possibilities, and I feel strongly that the
dotted syntax is the most readable for these files.
i.e. To my mind, (eval message "hello") is liable to confuse people,
whereas (eval . (message "hello")) is rather clear.
Of course we wouldn't want this to end up in the file either:
(eval . (message . ("hello" . nil)))
I guess we'd need some code to only 'dot' the high level elements,
but not the values.
I don't suppose anything like that already exists?
-Phil
- Two problems with directory-local variables, Marcin Borkowski, 2018/09/17
- Re: Two problems with directory-local variables, Phil Sainty, 2018/09/17
- Re: Two problems with directory-local variables, Marcin Borkowski, 2018/09/17
- Re: Two problems with directory-local variables, Juri Linkov, 2018/09/17
- Re: Two problems with directory-local variables,
Phil Sainty <=
- Re: Two problems with directory-local variables, Juri Linkov, 2018/09/17
- Re: Two problems with directory-local variables, Stefan Monnier, 2018/09/17
- Re: Two problems with directory-local variables, Juri Linkov, 2018/09/19
- RE: Two problems with directory-local variables, Drew Adams, 2018/09/19
- Re: Two problems with directory-local variables, Juri Linkov, 2018/09/20