From: Glenn Morris <rgm@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Robert Dallas Gray <mail@robertdallasgray.com>, 12368@debbugs.gnu.org
Subject: bug#12368: 24.1; x-parse-geometry broken in Emacs 24.1
Date: Wed, 12 Sep 2012 14:22:32 -0400 [thread overview]
Message-ID: <7sa9wvp0d3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <441C52A0-2893-4403-91D3-8A5BF73234EE@swipnet.se> ("Jan Djärv"'s message of "Sat, 8 Sep 2012 15:29:46 +0200")
Jan Djärv wrote:
> x-parse-geometry (non-NS variant) calls XParseGeometry. This may not
> be available. But the W32-prt has an implementation.
>
> It seems as ns-parse-geometry expects "top left with height", i.e.:
>
> (x-parse-geometry "10 5 80 40")
> ((top . 10) (left . 5) (height . 80) (width . 40))
>
> I don't know where this type of geometry is specified, but we could
> support both (if there is a space in the string, it is NS-style, if
> there is a +, -, x orX, it is X-style).
>
> We could move the W32-version of XParseGeometry somewhere common
> (where?) and use that. Or we can rewrite x-parse-geometry in lisp.
>
> Suggestions?
I don't know...
At first I was going to say, rewrite x-parse-geometry in Lisp sounds
simple, especially if you want to handle both style of geometry.
But then since XParseGeometry is standard in X11 and already
reimplemented in w32xfns.c, maybe it's simpler just to use that.
And set_frame_size calls XParseGeometry from C as well (so how does that
work on NS? I see nsfns.m has a stub definition as well).
next prev parent reply other threads:[~2012-09-12 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 12:31 bug#12368: 24.1; x-parse-geometry broken in Emacs 24.1 Robert Dallas Gray
2012-09-06 16:57 ` Glenn Morris
2012-09-08 13:29 ` Jan Djärv
2012-09-12 18:22 ` Glenn Morris [this message]
2012-09-12 20:30 ` Jan Djärv
2012-09-12 20:41 ` Glenn Morris
2012-09-19 6:51 ` Jan Djärv
2012-09-19 21:21 ` Andy Moreton
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=7sa9wvp0d3.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12368@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=mail@robertdallasgray.com \
/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.