all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 13 Mar 2009 10:40:40 +0545	[thread overview]
Message-ID: <7F976ABF-21AD-48B9-BEAB-CBA371B59710@gmail.com> (raw)
In-Reply-To: <97A16350-7C3B-45CA-8E59-5B4313AB53A2@gmail.com>


On Mar 11, 2009, at 6:12 PM, David Reitter wrote:

> On Mar 11, 2009, at 5:59 AM, Adrian Robert wrote:
>>
>> 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.
>
> Yes, but the technical distinction of what is available across  
> platforms is not a user-level category that merits aggregating  
> these functions in a panel (vs. Emacs customization vs. Options  
> menu vs. Lisp variables).

I'm not sure about this.  Whether I were using W32 or Mac or anything  
else it makes sense as a user to split these out.  Since if I'm an  
emacs user on other platforms, these will be exactly the things I  
don't know about and might want to set on moving to the new  
platform.  But anway it doesn't matter since it will be removed, I  
was only mentioning it to point out a possible hazard (which turns  
out not to be a hazard) about transitioning to .emacs.






  parent reply	other threads:[~2009-03-13  4:55 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 ` app termination / ns resources Adrian Robert
2009-03-11 12:27   ` David Reitter
2009-03-11 16:51     ` Adrian Robert
2009-03-13  4:55     ` Adrian Robert [this message]
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=7F976ABF-21AD-48B9-BEAB-CBA371B59710@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.