unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25542@debbugs.gnu.org
Subject: bug#25542: 25.1; Restoring the frame from fullscreen to maximized
Date: Fri, 27 Jan 2017 09:22:54 +0100	[thread overview]
Message-ID: <CAH8Pv0i700FUNk269Nw6Oo4fv8dxtYAG2euhRiG8hQPsdakKUw@mail.gmail.com> (raw)
In-Reply-To: <83sho429zr.fsf@gnu.org>

>> > (2) How do the frames from before step 2 and after step 3 differ?
>> >     Please use M-: (frame-geometry) and post the ‘outer-position’ and
>> >     ‘outer-size’ values.
>>
>> The frames are exactly equal.  Both in size and positon on the screen.
>
> This seems to contradict your original report, where you said the two
> frames had different sizes.

Mmmm I said this:

  Observed behavior: The frame is not maximized (it is smaller that a
  maximized one, both in height and width).

So I don't see any contradiction - What I wanted to express in both
cases is that the Emacs frame, after the final step, is _not_
maximized (as it should be).

IOW: in step 3, the frame should have been switched from fullscreen to
maximized, but it actually switched to the initial status/size (i.e.
not maximized).

HTH

-- 
Dani Moncayo





  reply	other threads:[~2017-01-27  8:22 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  8:15 bug#25542: 25.1; Restoring the frame from fullscreen to maximized Dani Moncayo
2017-01-26  9:51 ` martin rudalics
2017-01-26 10:20   ` Dani Moncayo
2017-01-26 10:54     ` Dani Moncayo
2017-01-26 17:49       ` Dani Moncayo
2017-01-26 18:02         ` Noam Postavsky
2017-01-26 19:06         ` martin rudalics
2017-01-27  7:54           ` Dani Moncayo
2017-01-27  9:18             ` martin rudalics
2017-01-26 14:00     ` martin rudalics
2017-01-26 15:43       ` Noam Postavsky
2017-01-26 16:10         ` Eli Zaretskii
2017-01-27  8:03       ` Dani Moncayo
2017-01-27  8:16         ` Eli Zaretskii
2017-01-27  8:22           ` Dani Moncayo [this message]
2017-01-27  9:19         ` martin rudalics
2017-01-27  9:25           ` Dani Moncayo
2017-01-27  9:31             ` Dani Moncayo
2017-01-27  9:50               ` martin rudalics
2017-01-27 10:22                 ` Dani Moncayo
2017-01-27 10:27                   ` Dani Moncayo
2017-01-27  9:34             ` martin rudalics
2017-01-27 10:01               ` Dani Moncayo
2017-01-27 13:47                 ` martin rudalics
2017-01-27 18:50                   ` Noam Postavsky
2017-01-28  8:02                     ` martin rudalics
2020-09-04 12:32                       ` Lars Ingebrigtsen
2020-09-04 17:50                         ` Dani Moncayo
2020-09-05  6:46                           ` Eli Zaretskii
2020-09-05 11:59                             ` Dani Moncayo
2020-09-05 12:17                               ` Eli Zaretskii
2020-09-05 12:19                                 ` Dani Moncayo
2020-09-05 12:30                                   ` Eli Zaretskii
2020-09-05 12:32                                     ` Dani Moncayo
2020-09-05 12:48                                       ` Eli Zaretskii
2020-09-05 15:10                                       ` Ken Brown
2020-09-05 16:07                                         ` Eli Zaretskii
2020-09-05 16:10                                           ` Ken Brown
2020-09-05 16:41                                             ` Eli Zaretskii
2020-09-09  8:44                               ` martin rudalics
2020-09-09 16:46                                 ` Dani Moncayo
2020-09-09 18:19                                 ` Ken Brown
2020-09-09 20:24                                   ` Ken Brown
2020-09-10  7:16                                     ` martin rudalics
2020-09-10 15:05                                       ` Ken Brown
2020-09-10 18:16                                         ` martin rudalics
2020-09-10 19:04                                           ` Ken Brown
2020-09-11  7:53                                             ` martin rudalics
2020-09-11 20:16                                               ` Ken Brown
2020-09-11 20:33                                                 ` Achim Gratz
2020-09-11 21:18                                                   ` Ken Brown
2020-09-12  6:54                                                     ` martin rudalics
2020-09-12 11:37                                                       ` Ken Brown
2020-09-12  6:54                                                   ` martin rudalics
2020-09-12  6:06                                                 ` Eli Zaretskii
2020-09-12  6:54                                                 ` martin rudalics
2017-01-26 16:08   ` 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=CAH8Pv0i700FUNk269Nw6Oo4fv8dxtYAG2euhRiG8hQPsdakKUw@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=25542@debbugs.gnu.org \
    --cc=eliz@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).