unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Question about defcustom and :set-after
Date: Mon, 30 Apr 2018 18:33:00 -0700	[thread overview]
Message-ID: <87muxk17oz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <jwv36zc2ovy.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 30 Apr 2018 20:37:07 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> So I started writing support for a Gnus mock environment: you call
>> `gnus-mock' and it starts up a Gnus session completely independent of
>> your own Gnus customizations, that has some dummy data in it that gets
>> flushed and restored each time you restart the mock session.
>
> Sounds really useful.
>
>> That involves saving all relevant customizations (and some defvars) and
>> putting them aside, then setting all customization options (and some
>> defvars) back to their default values, and starting Gnus.
>
> Are you intending this mock environment to be used from a running Emacs
> session or from "emacs -Q"?

Being entirely too lazy, I intended it to be run from a running Emacs
session. I was imagining it as sort of a "gnus -Q", as in "please submit
a repro starting with `gnus-mock'".

But realistically that's a dumb idea, and it should be made to be used
from "emacs -Q". That would completely obviate the need for all this
custom-variable tomfoolery. Maybe that stuff could be quietly added but
not encouraged.

The question remains, though: I think several of Gnus' defcustom's might
need :set-after clauses.

Eric




  reply	other threads:[~2018-05-01  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  0:00 Question about defcustom and :set-after Eric Abrahamsen
2018-05-01  0:37 ` Stefan Monnier
2018-05-01  1:33   ` Eric Abrahamsen [this message]
2018-05-01  3:54     ` Stefan Monnier
2018-05-01 16:20       ` Eric Abrahamsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87muxk17oz.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).