all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Dedicated window for *log-edit-files*
Date: Fri, 25 Oct 2019 11:50:55 -0400	[thread overview]
Message-ID: <jwvwocsomla.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CALDnm51q-f4hsS91YM2YEKyxkYqSHLw1FTOAcbft0w7ew+Ofbw@mail.gmail.com> ("João Távora"'s message of "Fri, 25 Oct 2019 16:36:45 +0100")

>> [ Yes, non-nil default values for non-preloaded hooks are evil.
>>   I confess to doing it, but I plead insanity.  ]
> Why evil?

Because you can't conveniently add/remove values from it (you either
have to wait for the file to be loaded to do that, or force loading it
eagerly at startup, or completely override the default value with your
own).

We discussed a few times teaching Custom how to modify lists like these
(so what is stored in your config file for this variable is morally
a sort of "diff" rather than the current result of applying the diff).

> How else would you arrange to have this default behaviour?

Typically we add ad-hoc config vars to enable/disable features instead
that also helps with discoverability.  But yes, it has its own disadvantages.


        Stefan




  reply	other threads:[~2019-10-25 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 11:48 Dedicated window for *log-edit-files* João Távora
2019-10-25 12:48 ` Stefan Monnier
2019-10-25 15:36   ` João Távora
2019-10-25 15:50     ` Stefan Monnier [this message]
2019-10-25 21:38       ` João Távora
2019-10-25 23:51         ` Stefan Monnier
2019-10-29 21:37     ` Juri Linkov
2019-10-25 14:43 ` Drew Adams
2019-10-25 15:21   ` João Távora
2019-10-26  8:12 ` martin rudalics
2019-10-26 12:00   ` Stefan Monnier
2019-10-27  7:49     ` martin rudalics
2019-10-27 17:43       ` Stefan Monnier

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=jwvwocsomla.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@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.
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.