unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 13583@debbugs.gnu.org
Subject: bug#13583: 24.3.50; Error when activating auto-revert-mode
Date: Tue, 29 Jan 2013 19:39:27 +0200	[thread overview]
Message-ID: <83a9rrj3cg.fsf@gnu.org> (raw)
In-Reply-To: <87a9rs6r3h.fsf@web.de>

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Tue, 29 Jan 2013 14:44:50 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> IMHO, no user should need to do something like that.

No one does.  Using custom-set-variables is much easier.  I just
wanted to give Dani all the alternatives I knew about.  Nothing wrong
with that, is there?

> I often saw people being reluctant about using `custom-set-variables' in
> their init file.
> 
> I browsed the doc of `custom-set-variables', as well as the
> "Customization" chapter in the manual.  I found no places were we say
> that some of these functions are suitable for being called from other
> files than the custom file, without danger.

I call it from my .emacs, and never had any problems in years.





  reply	other threads:[~2013-01-29 17:39 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 [this message]
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

  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=83a9rrj3cg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13583@debbugs.gnu.org \
    --cc=michael_heerdegen@web.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).