unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Robert Dallas Gray <mail@robertdallasgray.com>
Cc: 12368@debbugs.gnu.org
Subject: bug#12368: 24.1; x-parse-geometry broken in Emacs 24.1
Date: Sat, 8 Sep 2012 15:29:46 +0200	[thread overview]
Message-ID: <441C52A0-2893-4403-91D3-8A5BF73234EE@swipnet.se> (raw)
In-Reply-To: <72685A2C-FE87-434E-991F-AEC63AE1D255@robertdallasgray.com>


6 sep 2012 kl. 14:31 skrev Robert Dallas Gray <mail@robertdallasgray.com>:

> emacs -Q
> M-:
> (x-parse-geometry "80x40+5+10")
> 
> Expected result: ((height . 40) (width . 80) (top . 10) (left . 5))
> Actual result:   ((top . 80)) 


Glenn Morris wrote:

> 
> C-h f x-parse-geometry:
> 
>    On Nextstep, this just calls `ns-parse-geometry'.
> 
> C-h f ns-parse-geometry:
> 
>    Parse a Nextstep-style geometry string GEOM.
> 
> Why this needs to be different on this platform I do not know, but it is.

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?

	Jan D.










  parent reply	other threads:[~2012-09-08 13:29 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 [this message]
2012-09-12 18:22   ` Glenn Morris
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

  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=441C52A0-2893-4403-91D3-8A5BF73234EE@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=12368@debbugs.gnu.org \
    --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 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).