From: Adrian Robert <adrian.b.robert@gmail.com>
To: David Reitter <david.reitter@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: app termination / ns resources
Date: Wed, 11 Mar 2009 11:59:25 +0200 [thread overview]
Message-ID: <81BDC0A8-D72A-4CA7-8342-65057E77339D@gmail.com> (raw)
In-Reply-To: <B9752D2D-6866-4533-841A-CCBC9C51F7B9@gmail.com>
[cc'ing emacs-devel]
> Also, I have a removed the NS resources and also the ns-expand-
> lines business, which helped with the interrupted pattern in the
> fringe for some (but not all) fonts. I will test this a little
> more and check it in later this week.
One final dying thought about this ;) -- the way it was prefs-panel <-
> ns defaults <-> platform-specific settings was a neat way of
keeping the NS-specific stuff, be it line spacing or modifier keys,
out of .emacs, etc. so they would not interfere when moving a .emacs
across platforms.
As some of these were or are being brought up to the core level, this
path can and should go away. However, what WILL be remaining platform-
specific after the current round are:
- modifier key settings
- system highlight color switch
- antialiasing switch
- quickdraw smoothing switch
As these get moved to .emacs, it is important to make sure settings
for these don't pollute it in a way so as to cause migration
problems. I don't know but it would be nice if there were some way
to use .emacs and core customization but have these settings
conditionalized on whether the variables exist, or whether the
windowing system is 'ns.
Finally, the face color setting system will still need to be changed
to use the .emacs path.
next parent reply other threads:[~2009-03-11 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B9752D2D-6866-4533-841A-CCBC9C51F7B9@gmail.com>
2009-03-11 9:59 ` Adrian Robert [this message]
2009-03-11 12:27 ` app termination / ns resources David Reitter
2009-03-11 16:51 ` Adrian Robert
2009-03-13 4:55 ` Adrian Robert
2009-03-14 21:39 ` David Reitter
2009-03-11 14:42 ` Mike Mattie
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=81BDC0A8-D72A-4CA7-8342-65057E77339D@gmail.com \
--to=adrian.b.robert@gmail.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 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.