From: Adrian Robert <adrian.b.robert@gmail.com>
To: David Reitter <david.reitter@gmail.com>
Cc: 2532@emacsbugs.donarmstrong.com, Emacs-Devel devel <emacs-devel@gnu.org>
Subject: bug#2532: NS: ns-expand-space / slider in Preferences dialog not functional
Date: Fri, 6 Mar 2009 21:20:13 +0200 [thread overview]
Message-ID: <D847E263-9F65-417B-B881-CD1471860821__32070.8309569911$1236368791$gmane$org@gmail.com> (raw)
In-Reply-To: <5393D476-3312-4DF3-AF39-6D698B7FDA49@gmail.com>
On Mar 5, 2009, at 5:39 AM, David Reitter wrote:
> The `ns-set-resource' Elisp interface is better than none on the
> Elisp side, but what happened to Emacs customization variables?
>
> As said before on this list, introducing another way (beyond .emacs
> and customization/custom-file) creates a new failure point for
> people's configurations. This is bad in two respects: they won't
> be able to reset Emacs to a vanilla state, or troubleshoot a faulty
> configuration.
> ...
> All of these things make it harder to support users. "emacs -q" is
> helpful, but at the end of the day, people want to run "emacs".
> Especially seasoned users will complain that they have to find and
> delete ~/Library/Preferences/org.gnu.emacs.plist.
This is no longer true -- running -q or -Q now ignores the plist --
though not X resources, I believe. The one difference between the NS
defaults and X resources is that the defaults system is read/write,
whereas X resources are for some strange reason read-only by design.
After various discussion here, I now believe this difference is
fundamental, and that the NS defaults system should therefore be used
in Emacs only internally for parameters that are specific to NS and
not set by users. This includes reading existing system settings
like anti-aliasing threshold, as well as storing previous directories
and window locations for file open/save dialogs. Completely behind-
the-scenes stuff.
I would advocate transitioning all of the ns-xxx lisp variables that
are not stored in defaults to the customization system.
I am not sure if it is appropriate to do this under pretest,
however. It would be a user-visible change and potentially cause
unexpected side effects.
next prev parent reply other threads:[~2009-03-06 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 21:35 bug#2532: NS: ns-expand-space / slider in Preferences dialog not functional Adrian Robert
2009-03-05 3:39 ` David Reitter
[not found] ` <5393D476-3312-4DF3-AF39-6D698B7FDA49@gmail.com>
2009-03-06 19:20 ` Adrian Robert [this message]
[not found] ` <D847E263-9F65-417B-B881-CD1471860821@gmail.com>
2009-03-06 19:35 ` David Reitter
2009-03-07 1:09 ` YAMAMOTO Mitsuharu
-- strict thread matches above, loose matches on Subject: below --
2009-03-01 23:52 David Reitter
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='D847E263-9F65-417B-B881-CD1471860821__32070.8309569911$1236368791$gmane$org@gmail.com' \
--to=adrian.b.robert@gmail.com \
--cc=2532@emacsbugs.donarmstrong.com \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@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 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).