bug#62961: closed (fringe.c comment does not show the actual definition)

[GNU bug Tracking System]

Your message dated Thu, 20 Apr 2023 13:06:53 +0300
with message-id <83o7ni6f5u.fsf@gnu.org>
and subject line Re: bug#62961: fringe.c comment does not show the actual 
definition
has caused the debbugs.gnu.org bug report #62961,
regarding fringe.c comment does not show the actual definition
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
62961: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62961
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> fringe.c comment does not show the actual definition
>
>
>
>
> Date: 
>
> Thu, 20 Apr 2023 02:33:17 +0200
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
>
>
>
>
>
> IS:
>
> /* Large circle bitmap.  */
> /*
>   ........
>   ..xxxx..
>   .xxxxxx.
>   xxxxxxxx
>   xxxxxxxx
>   .xxxxxx.
>   ..xxxx..
>   ........
> */
> static unsigned short large_circle_bits[] = {
>   0x3c, 0x7e, 0xff, 0xff, 0xff, 0xff, 0x7e, 0x3c};
>
> SHOULD BE:
>
>   ..xxxx..
>   .xxxxxx.
>   xxxxxxxx
>   xxxxxxxx
>   xxxxxxxx
>   xxxxxxxx
>   .xxxxxx.
>   ..xxxx..
>
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#62961: fringe.c comment does not show the actual definition
>
>
>
>
> Date: 
>
> Thu, 20 Apr 2023 13:06:53 +0300
>
>
>
>
> > Date: Thu, 20 Apr 2023 02:33:17 +0200
> > From: Claudio Grondi <claudio.grondi@freenet.de>
> > 
> > 
> > IS:
> > 
> > /* Large circle bitmap.  */
> > /*
> >    ........
> >    ..xxxx..
> >    .xxxxxx.
> >    xxxxxxxx
> >    xxxxxxxx
> >    .xxxxxx.
> >    ..xxxx..
> >    ........
> > */
> > static unsigned short large_circle_bits[] = {
> >    0x3c, 0x7e, 0xff, 0xff, 0xff, 0xff, 0x7e, 0x3c};
> > 
> > SHOULD BE:
> > 
> >    ..xxxx..
> >    .xxxxxx.
> >    xxxxxxxx
> >    xxxxxxxx
> >    xxxxxxxx
> >    xxxxxxxx
> >    .xxxxxx.
> >    ..xxxx..
>
> Thanks, fixed on the emacs-24 branch, and closing the bug.
>
>
> --- End Message ---