From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: [change the default registry names]
Date: Fri, 27 Apr 2018 06:59:07 -1000 [thread overview]
Message-ID: <CADoYgq_+RMN5Dot49N1uT8xOOhwNNFWExv7uFe5QCixYgR9+VA@mail.gmail.com> (raw)
In-Reply-To: <87zi1pc88p.fsf@mat.ucm.es>
On Thu, Apr 26, 2018 at 11:24 PM, Uwe Brauer <oub@mat.ucm.es> wrote:
> Unfortunately gnus-registry-marks cannot be customized! It is defined
> via defvar.
It seems almost too obvious to state, and probably contrary to
accepted best practices ... but ... I never liked 'customize' for some
things, in fact many things. When possible I prefer to explicitly
override defvar default values with setq, after the relevant package
has been loaded. This keeps my customizations--- with copious in-line
comments--- in startup files which are easily synced between
computers.
--
Bob Newell
Honolulu, Hawai`i
Sent via Linux Mint 17.
next prev parent reply other threads:[~2018-04-27 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 12:52 registry seems to be saved for 27.0.50 any longer/Gnorb Uwe Brauer
2018-04-26 13:28 ` Michael Heerdegen
2018-04-26 15:09 ` Uwe Brauer
2018-04-26 15:18 ` Michael Heerdegen
2018-04-26 15:55 ` Uwe Brauer
2018-04-26 16:35 ` [change the default registry names] (was: registry seems to be saved for 27.0.50 any longer/Gnorb) Uwe Brauer
2018-04-26 18:46 ` [change the default registry names] Eric Abrahamsen
2018-04-26 19:19 ` Michael Heerdegen
2018-04-26 19:30 ` Eric Abrahamsen
2018-04-27 9:24 ` Uwe Brauer
2018-04-27 16:59 ` Bob Newell [this message]
2018-04-27 18:27 ` Eric Abrahamsen
2018-05-07 8:05 ` Uwe Brauer
2018-05-07 23:43 ` Bob Newell
2018-05-10 8:11 ` Uwe Brauer
2018-05-10 12:38 ` Michael Heerdegen
2018-05-11 17:22 ` Uwe Brauer
2018-05-11 17:28 ` Bob Newell
2018-05-07 8:07 ` [setq does not work] (was: [change the default registry names]) Uwe Brauer
2018-04-26 15:15 ` registry seems to be saved for 27.0.50 any longer/Gnorb Uwe Brauer
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=CADoYgq_+RMN5Dot49N1uT8xOOhwNNFWExv7uFe5QCixYgR9+VA@mail.gmail.com \
--to=bobnewell@bobnewell.net \
--cc=ding@gnus.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).