From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 13583@debbugs.gnu.org
Subject: bug#13583: 24.3.50; Error when activating auto-revert-mode
Date: Tue, 29 Jan 2013 19:48:26 +0200 [thread overview]
Message-ID: <83622fj2xh.fsf@gnu.org> (raw)
In-Reply-To: <87d2wox9cd.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, 13583@debbugs.gnu.org
> Date: Tue, 29 Jan 2013 17:06:10 +0100
>
> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>
> >> Cockipt error. The doc string clearly says
> >> "If non-nil Auto Revert Mode uses file notification functions.
> >> This requires Emacs being compiled with file notification
> >> support (see `auto-revert-notify-enabled'). You should set this
> >> variable through Custom only." ^^^^^^^^^^^^^^^^^^^
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> That's because this defcustom has a :set function defined for it; if
> >> that function isn't run, the results are unpredictable.
> >> Any reason not to close this bug?
> >
> > It should be possible to have (setq auto-revert-use-notify nil) in your
> > .emacs and not use Custom.
>
> I've added
>
> :initialize 'custom-initialize-default
>
> to that defcustom. That seems to do the job.
Thanks, but the doc string still says one needs to use Customize.
Anyway, if ":initialize 'custom-initialize-default" is such a
wonderful feature that everyone wants, why isn't it the default, and
why does the user of defcustom need to opt-in it?
next prev parent reply other threads:[~2013-01-29 17:48 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
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 [this message]
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
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=83622fj2xh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13583@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).