From: martin rudalics <rudalics@gmx.at>
To: david@ngdr.net
Cc: "25943@debbugs.gnu.org" <25943@debbugs.gnu.org>
Subject: bug#25943: 21.5 Frame Display Difficulties
Date: Fri, 07 Apr 2017 07:56:28 +0200 [thread overview]
Message-ID: <58E72A0C.6090104@gmx.at> (raw)
In-Reply-To: <0312c9ae04719540d13a40236ab9f682@127.0.0.1>
> Unfortunately, problem 3 is alive and well; I shall write again if and
> when I have data that looks useful. I shall address your most recent
> questions as well. If you have any ideas that you would like me to try,
> please let me know.
Build 26.0.50 with any of the other toolkits (Lucid, Motif) or without
toolkit support and tell me whether the problem persists. This way we
can at least rule out that this is a GTK specific bug (which is always
the major first step with GNU/Linux builds on graphical terminals)
martin
next prev parent reply other threads:[~2017-04-07 5:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 3:51 bug#25943: 21.5 Frame Display Difficulties david
2017-03-03 8:13 ` martin rudalics
[not found] ` <af552a322a8a630796cbddf1133b6dbe@127.0.0.1>
2017-03-04 9:59 ` martin rudalics
2017-03-07 1:51 ` david
2017-03-07 9:45 ` martin rudalics
2017-03-08 22:58 ` david
2017-03-09 8:56 ` martin rudalics
2017-03-10 18:44 ` david
2017-03-11 10:21 ` martin rudalics
2017-03-23 7:59 ` martin rudalics
2017-03-28 22:43 ` david
2017-03-29 7:36 ` martin rudalics
2017-03-29 19:53 ` david
2017-03-30 7:29 ` martin rudalics
2017-04-01 4:35 ` david
2017-04-01 7:36 ` martin rudalics
[not found] ` <7ee8200b866d8067514fb8b0bb9e814b@127.0.0.1>
2017-04-02 7:55 ` martin rudalics
2017-04-04 0:35 ` david
2017-04-04 7:25 ` martin rudalics
2017-04-07 0:12 ` david
2017-04-07 5:56 ` martin rudalics [this message]
2017-04-07 21:16 ` david
2022-04-25 14:48 ` Lars Ingebrigtsen
2022-05-24 12:50 ` Lars Ingebrigtsen
2017-04-07 21:19 ` david
2017-04-08 9:00 ` martin rudalics
2017-04-11 6:49 ` 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=58E72A0C.6090104@gmx.at \
--to=rudalics@gmx.at \
--cc=25943@debbugs.gnu.org \
--cc=david@ngdr.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).