From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13583@debbugs.gnu.org
Subject: bug#13583: 24.3.50; Error when activating auto-revert-mode
Date: Tue, 29 Jan 2013 13:18:58 +0100 [thread overview]
Message-ID: <CAH8Pv0jZtYuwk+_rw=E+AB8NrZ11N9=P7_MUFq1n+aSadZUMmg@mail.gmail.com> (raw)
In-Reply-To: <83d2woi43u.fsf@gnu.org>
>> I try to avoid the customize facility as much as I can, because it
>> doesn't allow to set values based on conditions like the system-type,
>> for example.
>
> Doesn't custom-set-variables work inside an "if" clause? If it does,
> then what's the problem of using it only on some systems?
The problem with that approach is that, if I do some other
customization and save it, the custom facility writes _all_ current
unsaved customization to the custom file, therefore the customization
of `auto-revert-use-notify' would end up in the custom file, which is
not what I want, obviously.
A workaround is to fool the customize facility by marking the relevant
customizations as "saved" just after the call to custom-set-variables,
but that is an ugly hack, IMO.
>> Therefore, I'd like to be able to set `auto-revert-use-notify'
>> directly in my init file, with `setq', but if that is not possible, I
>> will have to adapt myself.
>
> You can run the :set form of the option, with suitable substitutions
> for "variable" and "value", instead of setting the value with setq.
> But then you'd need to change that every time the :set form changes in
> autorevert.el.
So that doesn't seem like a good solution either...
--
Dani Moncayo
next prev parent reply other threads:[~2013-01-29 12:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 10:59 bug#13583: 24.3.50; Error when activating auto-revert-mode Dani Moncayo
2013-01-29 11:10 ` Eli Zaretskii
2013-01-29 11:34 ` Dani Moncayo
2013-01-29 12:08 ` Eli Zaretskii
2013-01-29 12:18 ` Dani Moncayo [this message]
2013-01-29 12:35 ` Eli Zaretskii
2013-01-29 13:42 ` Dani Moncayo
2013-01-29 14:22 ` Dani Moncayo
2013-01-29 15:08 ` Drew Adams
2013-01-29 15:16 ` Wolfgang Jenkner
2013-01-29 16:12 ` Drew Adams
2013-01-29 21:25 ` Andy Moreton
2013-01-29 22:35 ` Drew Adams
2013-01-30 23:42 ` Andy Moreton
2013-01-30 23:52 ` Drew Adams
2013-01-29 17:44 ` Eli Zaretskii
2013-01-29 17:42 ` Eli Zaretskii
2013-01-29 13:44 ` Michael Heerdegen
2013-01-29 17:39 ` Eli Zaretskii
2013-01-29 18:13 ` Michael Heerdegen
2013-01-29 15:10 ` Stefan Monnier
2013-01-29 16:06 ` Michael Albinus
2013-01-29 17:48 ` Eli Zaretskii
2013-01-29 21:39 ` Stefan Monnier
2013-01-30 17:55 ` Eli Zaretskii
2013-01-30 21:02 ` Stefan Monnier
2013-01-30 7:28 ` Michael Albinus
2013-01-30 16:54 ` Eli Zaretskii
2013-01-30 19:24 ` Michael Albinus
2013-01-30 18:05 ` Dani Moncayo
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='CAH8Pv0jZtYuwk+_rw=E+AB8NrZ11N9=P7_MUFq1n+aSadZUMmg@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=13583@debbugs.gnu.org \
--cc=eliz@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.