unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>, <10773@debbugs.gnu.org>
Subject: bug#10773: set-variable can't change values of user options
Date: Tue, 21 Feb 2012 07:26:57 -0800	[thread overview]
Message-ID: <6E2C6DFEC18A42E98A69D5044CF56936@us.oracle.com> (raw)
In-Reply-To: <87mx8dt2mt.fsf@mail.jurta.org>

> In my opinion, the best way to eliminate the distinction
> between user variables (with the leading '*' in the docstring)
> and customizable variables in 24.2 is:
> 
> 1. Make `user-variable-p' an alias for `custom-variable-p'.
> 
> 2. Remove the `user-variable-p' condition from `set-variable'.
> 
> This will fix the reported case where `set-variable' can change
> the value of `outline-mode-hook', but not `outline-minor-mode-hook';
> and many other similar cases.

And how will that help code that uses
(defvar foo "*A user variable.")?

Users have always been able to set such a user variable using `set-variable'.






  reply	other threads:[~2012-02-21 15:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  9:43 bug#10773: set-variable can't change values of user options Juri Linkov
2012-02-09 18:28 ` Glenn Morris
2012-02-10  8:18   ` Kevin Rodgers
2012-02-10 10:18   ` Juri Linkov
2012-02-10 17:31     ` Glenn Morris
2012-02-10 18:01       ` Glenn Morris
2012-02-12  4:34         ` Stefan Monnier
2012-02-12 20:16           ` Glenn Morris
2012-02-13  2:58             ` Stefan Monnier
2020-09-19 15:21           ` Lars Ingebrigtsen
2020-09-19 15:46             ` Stefan Monnier
2020-09-19 15:49               ` Lars Ingebrigtsen
2020-09-19 16:04                 ` Stefan Monnier
2020-09-20  9:14                   ` Lars Ingebrigtsen
2012-02-21  0:40 ` Juri Linkov
2012-02-21 15:26   ` Drew Adams [this message]
2012-02-22  0:16     ` Juri Linkov

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=6E2C6DFEC18A42E98A69D5044CF56936@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10773@debbugs.gnu.org \
    --cc=juri@jurta.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 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).