From: martin rudalics <rudalics@gmx.at>
To: Alan Third <alan@idiocy.org>,
Alexander Miller <alexanderm@web.de>,
45620@debbugs.gnu.org, tumashu@163.com
Subject: bug#45620: 28.0.50; Child frames should have their own border width and colour
Date: Fri, 29 Jan 2021 08:51:13 +0100 [thread overview]
Message-ID: <254e45e6-7afb-a871-f7e0-be65ec3c1dd1@gmx.at> (raw)
In-Reply-To: <YBLn616pvkGEtX1L@breton.holly.idiocy.org>
> That all works as I expect on macOS, so I guess we can say it's fine?
I guess so too. Many thanks for checking.
> I don't get these warnings on my old Debian Jessie build environment,
> just on the newer Buster one, but Jessie's really old by now.
Here (with Buster) I especially get some 2000 lines of
2021-01-29 08:45:54.042 temacs[3778:3778] autorelease called without pool for object (0xd6f990) of class GSCInlineString in thread <NSThread: 0xbde000>{name = (null), num = 3778}
I've never seen before.
martin
next prev parent reply other threads:[~2021-01-29 7:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 13:24 bug#45620: 28.0.50; Child frames should have their own border width and colour Alexander Miller
2021-01-03 16:15 ` martin rudalics
2021-01-04 13:38 ` Alexander Miller
2021-01-04 16:22 ` martin rudalics
2021-01-04 17:48 ` Alexander Miller
2021-01-04 18:54 ` martin rudalics
2021-01-05 12:50 ` Alexander Miller
2021-01-05 15:33 ` martin rudalics
2021-01-05 15:34 ` martin rudalics
2021-01-06 11:32 ` Arthur Miller
2021-01-06 13:36 ` martin rudalics
2021-01-06 15:01 ` Arthur Miller
2021-01-05 16:26 ` Eli Zaretskii
2021-01-06 16:32 ` Alexander Miller
2021-01-06 18:48 ` martin rudalics
2021-01-13 9:17 ` Alexander Miller
2021-01-13 18:07 ` martin rudalics
2021-01-25 12:08 ` Alexander Miller
2021-01-25 19:05 ` martin rudalics
2021-01-26 15:59 ` martin rudalics
2021-01-27 20:49 ` Alan Third
2021-01-28 9:42 ` martin rudalics
2021-01-28 16:35 ` Alan Third
2021-01-29 7:51 ` martin rudalics [this message]
2021-01-27 20:44 ` Alexander Miller
2021-01-28 3:33 ` Eli Zaretskii
2021-01-28 7:06 ` Alexander Miller
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=254e45e6-7afb-a871-f7e0-be65ec3c1dd1@gmx.at \
--to=rudalics@gmx.at \
--cc=45620@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=alexanderm@web.de \
--cc=tumashu@163.com \
/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).