unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: emacs-devel@gnu.org
Subject: Re: master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516)
Date: Sat, 02 Mar 2019 23:09:42 +0200	[thread overview]
Message-ID: <871s3pynwx.fsf@mail.linkov.net> (raw)
In-Reply-To: <m2pnrazp9m.fsf@gmail.com> (Robert Pluim's message of "Fri, 01 Mar 2019 14:40:37 +0100")

> In any case, I think using x-parse-geometry is not necessary. The
> workarea already contains the relevant coördinates, and you can just
> pass (fullscreen . maximized) to get the right size. Sample patch
> below (which Iʼve tested only on macOS, not under X).

We should not use (fullscreen . maximized) because this is not what
make-frame does by default.  I see that in 'emacs -Q', 'C-x 5 2' makes
a new frame with text sizes 80x35 in the center of the current monitor.

We should do the same also in case when a new frame is created on
another monitor.  So maybe just omit the attributes 'width' and
'height', without using 'fullscreen'.  Any other attributes are
a matter of personal customization.



  reply	other threads:[~2019-03-02 21:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190225211142.21954.14993@vcs0.savannah.gnu.org>
     [not found] ` <20190225211144.0DD23206A2@vcs0.savannah.gnu.org>
2019-02-26  9:12   ` master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516) Robert Pluim
2019-02-26 15:23     ` Eli Zaretskii
2019-02-27 20:59       ` Juri Linkov
2019-02-28  9:38         ` Robert Pluim
2019-02-28 16:52           ` Robert Pluim
2019-02-28 20:40             ` Juri Linkov
2019-03-01 13:40               ` Robert Pluim
2019-03-02 21:09                 ` Juri Linkov [this message]
2019-03-03  1:05                   ` Drew Adams
2019-03-03 21:30                     ` Juri Linkov
2019-03-04  0:01                       ` Drew Adams
2019-03-04  8:53                   ` Robert Pluim
2019-02-28 18:11         ` Eli Zaretskii

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=871s3pynwx.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --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 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).