unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: wavexx@users.sf.net
Cc: bug-gnu-emacs@gnu.org
Subject: Re: wrong fullscreen frame size on osx
Date: Sun, 03 Feb 2008 07:41:20 +0900 (JST)	[thread overview]
Message-ID: <20080203.074120.24648493.mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <wavexx-1A464D.20503602022008@ger.gmane.org>

>>>>> On Sat, 02 Feb 2008 20:50:37 +0100, Yuri D'Elia <wavexx@users.sf.net> said:

>> > What about traditional X11 and Xinerama?
>> 
>> I said there's no notion of "monitors" in Emacs, and I didn't mean
>> there's no support for multiple monitors in X11.  Apple X11 uses
>> Xinerama, and I already mentioned this extension in the link below.

> Sorry, since the other thread discussed issues with the Apple's X11
> version too, I supposed there could be differences in the port.

The important point is that the multiple monitors support should be
introduced in a platform-independent way, rather than adding
Mac-specific functions or making some common functions' behavior
different only on Mac.

>> > Is there any progress on the cvs that I can use, or somewhere?
>> 
>> No.  Design and introduction of a new notion should be done really
>> carefully, and such kind of changes should be avoided for Emacs
>> 22.2.  If you want to suggest a design of the notion of "monitors",
>> Emacs 23 would be a good chance.

> Certainly, but current behavior is equally unacceptable. Maximize
> results in a badly-positioned ill-sized frame (not to mention that
> on OSX the menu bar is ignored).

The current behavior is consistent with its specification and not a
bug.  The "Multiple Displays" node in the elisp info says

     Note that some graphical terminals can output to more than a one
  monitor (or other output device) at the same time.  On these
  "multi-monitor" setups, a single DISPLAY value controls the output
  to all the physical monitors.  In this situation, there is currently
  no platform-independent way for Emacs to distinguish between the
  different physical monitors.

and the documentation of x-display-pixel-width says "Return the width
in pixels of DISPLAY."

> Don't you think that, until this notion of monitors exists, just the
> current monitor should be considered?

In that case, "the current monitor" should be well-defined.  And if
you want to make a feature request, emacs-devel@gnu.org would be more
appropriate place.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp




      reply	other threads:[~2008-02-02 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 17:10 wrong fullscreen frame size on osx Yuri D'Elia
2008-02-01  0:54 ` YAMAMOTO Mitsuharu
2008-02-02 12:26   ` Yuri D'Elia
2008-02-02 13:05     ` YAMAMOTO Mitsuharu
2008-02-02 19:50       ` Yuri D'Elia
2008-02-02 22:41         ` YAMAMOTO Mitsuharu [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=20080203.074120.24648493.mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=wavexx@users.sf.net \
    /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).