From: Stefan Kangas <stefan@marxist.se>
To: Dieter Deyke <dieter.deyke@gmail.com>
Cc: larsi@gnus.org, 36414@debbugs.gnu.org, Pip Cet <pipcet@gmail.com>
Subject: bug#36414: 27.0.50; svg-clock does not work anymore
Date: Tue, 18 Aug 2020 11:21:00 +0000 [thread overview]
Message-ID: <CADwFkmkzGyW9GUN7LUsq8mVEv1NCvfdmGyCON08gLBox6QDT_A@mail.gmail.com> (raw)
In-Reply-To: <87zhm29lgd.fsf@gmail.com> (Dieter Deyke's message of "Fri, 28 Jun 2019 10:13:22 +0200")
tags 36414 + patch
thanks
Dieter Deyke <dieter.deyke@gmail.com> writes:
> Pip Cet <pipcet@gmail.com> writes:
>
>> On Fri, Jun 28, 2019 at 5:29 AM Dieter Deyke <dieter.deyke@gmail.com> wrote:
>>> Executing (svg-clock) from elpa does not show the clock anymore, but just the
>>> single char '*'.
>>
>> Sorry for barging in, I thought this might be related to the recent
>> image.c changes so I had a look.
>>
>> svg-clock.el uses `svg-def', which is now an internal function,
>> `svg--def'. I believe Lars is the one working on this.
>>
>> Can you try the attached patch to see whether that is indeed the problem?
>
> Thanks,
>
> your patch works perfectly.
This patch seems to have fixed the problem, but AFAICT it was never
installed.
Should it be installed, or is there some reason not to? Thanks.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-18 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 5:28 bug#36414: 27.0.50; svg-clock does not work anymore Dieter Deyke
2019-06-28 6:57 ` Pip Cet
2019-06-28 8:13 ` Dieter Deyke
2020-08-18 11:21 ` Stefan Kangas [this message]
2020-08-18 11:33 ` Dieter Deyke
2020-08-18 12:13 ` Eli Zaretskii
2020-08-18 12:35 ` Lars Ingebrigtsen
2020-08-18 12:45 ` Stephen Berman
2020-08-18 12:50 ` Lars Ingebrigtsen
2019-06-30 21:37 ` Michael Heerdegen
2019-07-01 13:38 ` Pip Cet
2019-07-01 22:02 ` Michael Heerdegen
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=CADwFkmkzGyW9GUN7LUsq8mVEv1NCvfdmGyCON08gLBox6QDT_A@mail.gmail.com \
--to=stefan@marxist.se \
--cc=36414@debbugs.gnu.org \
--cc=dieter.deyke@gmail.com \
--cc=larsi@gnus.org \
--cc=pipcet@gmail.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 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.