From: Eli Zaretskii <eliz@gnu.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: nick@tenpoint.co.nz, 24229@debbugs.gnu.org
Subject: bug#24229: 25.1; Can't set EPA program
Date: Thu, 18 Aug 2016 17:13:30 +0300 [thread overview]
Message-ID: <83pop6dv1x.fsf@gnu.org> (raw)
In-Reply-To: <od160qyo8fg.fsf-ueno@gnu.org> (message from Daiki Ueno on Thu, 18 Aug 2016 09:14:27 +0200)
> From: Daiki Ueno <ueno@gnu.org>
> Cc: nick@tenpoint.co.nz, 24229@debbugs.gnu.org
> Date: Thu, 18 Aug 2016 09:14:27 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> So, we really need to take account of user's intention here; check
> >> whether the variable set by user or it is the default value. With
> >> 'setq' it is not possible to have such distinction.
> >
> > Doesn't Customize provide some functions that allow such a
> > distinction? The Customize UI surely is able to tell when a variable
> > was "changed not through Customize", isn't that what you want?
>
> This is what we are currently doing, and the bug is saying that it
> should be done without Customize. It doesn't make sense to me though.
What I meant is that Customize does have a way of telling that a value
was changed using setq, so evidently there's some infrastructure for
that which you could use. Am I missing something?
next prev parent reply other threads:[~2016-08-18 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 4:58 bug#24229: 25.1; Can't set EPA program Nick Helm
2016-08-15 22:26 ` Noam Postavsky
2016-08-16 0:56 ` Nick Helm
2016-08-16 19:38 ` Daiki Ueno
2016-08-17 0:18 ` Nick Helm
2016-08-17 7:46 ` Daiki Ueno
2016-08-17 15:21 ` Eli Zaretskii
2016-08-18 7:14 ` Daiki Ueno
2016-08-18 14:13 ` Eli Zaretskii [this message]
2016-08-18 15:08 ` Daiki Ueno
2016-08-18 15:35 ` Eli Zaretskii
2016-08-18 15:46 ` Glenn Morris
2016-08-18 16:16 ` Eli Zaretskii
2016-08-19 9:22 ` Daiki Ueno
2016-08-19 9:40 ` Eli Zaretskii
2016-08-17 17:45 ` Richard Stallman
2016-08-18 1:32 ` Nick Helm
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=83pop6dv1x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24229@debbugs.gnu.org \
--cc=nick@tenpoint.co.nz \
--cc=ueno@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.