From: Stephen Berman <stephen.berman@gmx.net>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 24963@debbugs.gnu.org
Subject: bug#24963: 26.0.50; toggle-frame-maximized broken by double-buffering patch
Date: Fri, 18 Nov 2016 19:43:45 +0100 [thread overview]
Message-ID: <87a8cwfx26.fsf@gmx.net> (raw)
In-Reply-To: <87d1hs99ax.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Fri, 18 Nov 2016 15:01:10 +0100")
On Fri, 18 Nov 2016 15:01:10 +0100 Óscar Fuentes <ofv@wanadoo.es> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> 0. emacs -Q
>> 1. M-x toggle-frame-maximized
>> => frame is maximized
>> 2. M-x toggle-frame-maximized
>> => frame remains maximized,
>
> Cannot reproduce, either with latest master
> (e8efa66e01933b8ae7ac9abf530a3818551c1343) nor with a build made just
> after the double-buffering feature was committed:
>
> In GNU Emacs 26.0.50.1 (x86_64-pc-linux-gnu, X toolkit)
> of 2016-10-21 built on qcore
> Repository revision: 0929e061fb544c0f4c10ff0412a41cf7e8148270
> Windowing system distributor 'The X.Org Foundation', version 11.0.11804000
> System Description: Ubuntu 16.10
>
> (Note that I use Lucid.)
I guess this is a toolkit-specific bug, then, perhaps GTK+ only.
(Unfortunately, I cannot build with lucid or even with no toolkit: both
fail with this error:
/usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: image.o: undefined reference to symbol 'png_set_longjmp_fn@@PNG16_0'
/usr/lib64/libpng16.so.16: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:611: recipe for target 'temacs' failed
)
Steve Berman
next prev parent reply other threads:[~2016-11-18 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 12:10 bug#24963: 26.0.50; toggle-frame-maximized broken by double-buffering patch Stephen Berman
2016-11-18 14:01 ` Óscar Fuentes
2016-11-18 18:43 ` Stephen Berman [this message]
2016-11-18 19:52 ` Óscar Fuentes
2016-11-18 20:36 ` Stephen Berman
2016-11-25 23:29 ` Stephen Berman
2017-03-02 11:01 ` martin rudalics
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=87a8cwfx26.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=24963@debbugs.gnu.org \
--cc=ofv@wanadoo.es \
/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).