all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: stephen.berman@gmx.net, stefan@marxist.se, 51550@debbugs.gnu.org
Subject: bug#51550: 29.0.50; Customize Group INS buttons sometimes don't have a left box line
Date: Tue, 28 Dec 2021 14:40:49 +0200	[thread overview]
Message-ID: <835yr8nbqm.fsf@gnu.org> (raw)
In-Reply-To: <87ee5xzhrr.fsf@yahoo.com> (message from Po Lu on Tue, 28 Dec 2021 08:37:28 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: stefan@marxist.se,  stephen.berman@gmx.net,  51550@debbugs.gnu.org
> Date: Tue, 28 Dec 2021 08:37:28 +0800
> 
> (insert #("foo\nfoo " 0 4 (face widget-field) 4 7 (face custom-button)))
> 
> The second foo will be missing a start box line, which is the bug here.

I didn't yet look seriously enough at that, but: I can only reproduce
this problem on the master branch; Emacs 28 works as expected.  Is
that what you see as well?  If so, then it is strange that you think
the problem happens in the code that wasn't touched at all between
Emacs 28 and Emacs 29, AFAICT.  Most probably, the root cause is
somewhere else.





  reply	other threads:[~2021-12-28 12:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ee80gezy.fsf.ref@yahoo.com>
2021-11-01 13:52 ` bug#51550: 29.0.50; Customize Group INS buttons sometimes don't have a left box line Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-01 14:29   ` Eli Zaretskii
2021-11-01 19:28     ` Stephen Berman
2021-11-01 19:38       ` Eli Zaretskii
2021-11-02  1:58         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-02 10:58           ` Stephen Berman
2021-11-02 14:13           ` Eli Zaretskii
2021-11-02 23:59             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03  5:35             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03  7:03               ` Stefan Kangas
2021-11-03 12:53                 ` Eli Zaretskii
2021-11-05  7:27                   ` Stefan Kangas
2021-12-27 10:50                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27 11:19                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27 14:55                       ` Eli Zaretskii
2021-12-28  0:37                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-28 12:40                           ` Eli Zaretskii [this message]
2021-12-28 12:45                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-28 13:17                               ` Eli Zaretskii
2021-12-28 13:24                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-28 17:35                       ` Eli Zaretskii
2021-12-29  0:33                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 12:56                           ` Eli Zaretskii
2021-12-29 13:23                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 13:37                               ` Eli Zaretskii
2021-12-29 13:54                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 14:56                                   ` Eli Zaretskii
2021-12-30  1:11                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-30 11:37                                   ` Eli Zaretskii
2021-12-30 11:43                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835yr8nbqm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51550@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=stefan@marxist.se \
    --cc=stephen.berman@gmx.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.