From: Kai Tetzlaff <kai.tetzlaff@web.de>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 10103@debbugs.gnu.org
Subject: bug#10103: 24.0.91; Emacs/nextstep ignores frame geometry from org.gnu.Emacs.plist
Date: Sun, 11 Dec 2011 13:15:43 +0100 [thread overview]
Message-ID: <7ik463xq1c.fsf@mack.tetzco.de> (raw)
In-Reply-To: <1DF79C6D-9B32-4A7F-BDFC-DA26B77C9F37@swipnet.se> ("Jan \=\?utf-8\?Q\?Dj\=C3\=A4rv\=22's\?\= message of "Sat, 10 Dec 2011 15:01:59 +0100")
Hi,
Jan Djärv <jan.h.d@swipnet.se> writes:
> Hello.
>
>
> 5 dec 2011 kl. 01:41 skrev Kai Tetzlaff:
>
>> When i first started Emacs after the fix, i got an immediate crash.
>> After some debugging, i found that i had accidentally changed the type
>> of the Height property from String to Integer. While trying to
>> understand what is happening i found that the following patch allows to
>> use either Integer or String type values in the plist file:
>>
>> === modified file 'src/nsfns.m'
>> --- src/nsfns.m 2011-12-04 13:25:16 +0000
>> +++ src/nsfns.m 2011-12-05 00:07:20 +0000
>> @@ -2217,7 +2217,7 @@
>> /* --quick was passed, so this is a no-op. */
>> return NULL;
>>
>> - res = [[[NSUserDefaults standardUserDefaults] objectForKey:
>> + res = [[[NSUserDefaults standardUserDefaults] stringForKey:
>> [NSString stringWithUTF8String: toCheck]] UTF8String];
>> return !res ? NULL :
>> (!strncasecmp (res, "YES", 3) ? "true" :
>>
>>
>> Would it make sense to change objectForKey to stringForKey (in this and
>> some other places) when trying to retrieve a string type property from a
>> plist file?
>
> It does not work that way for me. The documentation says that stringForKey returns:
>
> "The string associated with the specified key, or nil if the default does not exist or does not contain a string."
>
> and indeed, I get nil if I put in an integer for height, which makes
> UTF8String throw an exception. This is the same behaviour as with
> objectForKey. I tested on OSX 10.7, it may be different on other
> versions.
I'm still running 10.6, which might explain the difference.
>
> It does make sense to avoid crashing on bad user input, so I fixed it in another way.
Thanks!
> Jan D.
>
BR,
Kai
prev parent reply other threads:[~2011-12-11 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 6:51 bug#10103: 24.0.91; Emacs/nextstep ignores frame geometry from org.gnu.Emacs.plist Kai Tetzlaff
2011-12-04 13:27 ` Jan Djärv
2011-12-05 0:41 ` Kai Tetzlaff
2011-12-10 14:01 ` Jan Djärv
2011-12-11 12:15 ` Kai Tetzlaff [this message]
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=7ik463xq1c.fsf@mack.tetzco.de \
--to=kai.tetzlaff@web.de \
--cc=10103@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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).