all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Dieter Deyke <dieter.deyke@gmail.com>,
	Stefan Kangas <stefan@marxist.se>,
	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 14:50:49 +0200	[thread overview]
Message-ID: <87a6ysnmmu.fsf@gnus.org> (raw)
In-Reply-To: <87pn7ogm1h.fsf@gmx.net> (Stephen Berman's message of "Tue, 18 Aug 2020 14:45:30 +0200")

Stephen Berman <stephen.berman@gmx.net> writes:

> Didn't you already fix this in the ELPA repo with commit
> a52b4832ccf76b4e4332fefa225f21cc26de25c6:
>
> Author:     Lars Ingebrigtsen <larsi@gnus.org>
> AuthorDate: Mon Nov 4 20:02:47 2019 +0100
> Commit:     Lars Ingebrigtsen <larsi@gnus.org>
> CommitDate: Mon Nov 4 20:02:47 2019 +0100
>
>   There's no longer an svg-def function in svg.el
>
> which add the defun svg-clock-def.  And indeed, version 1.1 does work
> here.

D'oh.  Indeed; thanks.  I've now reverted the double-fix patch.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-18 12:50 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
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 [this message]
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=87a6ysnmmu.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36414@debbugs.gnu.org \
    --cc=dieter.deyke@gmail.com \
    --cc=pipcet@gmail.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.