From: Dima Kogan <dima@secretsauce.net>
To: emacs-devel@gnu.org
Subject: Re: Can we expand the valid location of "Local Variables" ?
Date: Mon, 23 Mar 2020 10:03:26 -0700 [thread overview]
Message-ID: <87d093ovfl.fsf@dima.secretsauce.net> (raw)
In-Reply-To: <83k13bawyn.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: dima@secretsauce.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org
>> Date: Mon, 23 Mar 2020 16:28:49 +0100
>>
>> >>>>> On Mon, 23 Mar 2020 16:17:46 +0200, Eli Zaretskii <eliz@gnu.org> said:
>>
>> >> From: Robert Pluim <rpluim@gmail.com>
>> >> Date: Mon, 23 Mar 2020 09:25:28 +0100
>> >> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
>> >>
>> >> Would providing a defcustom be such a hardship?
>>
>> Eli> Given that "enlarging the limit is a bad idea", I'm not even sure we
>> Eli> should provide a variable. We definitely shouldn't document
>> Eli> it.
>>
>> In that case we shouldnʼt even provide the variable, no?
>
> Possibly. Stefan didn't say why he thought adding a variable was an
> improvement, but my guess would be ease of change in the future.
I think we should provide the variable, because even here the usual
reasons apply:
- With a variable the reader of the code knows that all uses of that
variable refer to the same logical thing. If I see "3000" in two
different places I don't know if they're related: it may just be a
coincidence
- With a variable, the reader of the code knows where to find the
documentation. If we document this.
- With a variable, the generated .tex docs and the value (3000) can't go
out of sync
next prev parent reply other threads:[~2020-03-23 17:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 20:56 Can we expand the valid location of "Local Variables" ? Dima Kogan
2020-03-10 21:39 ` Stefan Monnier
2020-03-10 23:44 ` Dima Kogan
2020-03-11 2:01 ` Stefan Monnier
2020-03-22 23:08 ` Dima Kogan
2020-03-23 8:25 ` Robert Pluim
2020-03-23 14:17 ` Eli Zaretskii
2020-03-23 15:28 ` Robert Pluim
2020-03-23 15:54 ` Eli Zaretskii
2020-03-23 17:03 ` Dima Kogan [this message]
2020-03-23 17:24 ` Stefan Monnier
2020-03-24 2:20 ` Richard Stallman
2020-03-12 2:26 ` Richard Stallman
2020-03-14 5:54 ` Steve Youngs
2020-03-14 7:07 ` Stefan Monnier
2020-03-15 3:08 ` Richard Stallman
2020-03-15 6:41 ` Steve Youngs
2020-03-16 3:36 ` Richard Stallman
2020-03-23 15:56 ` Yuri Khan
2020-03-23 16:55 ` Dima Kogan
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=87d093ovfl.fsf@dima.secretsauce.net \
--to=dima@secretsauce.net \
--cc=emacs-devel@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.