From: Adam Faryna via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46883@debbugs.gnu.org, Adam Faryna <adam@faryna.io>
Subject: bug#46883: 28.0.50; calendar-holidays var setup errors
Date: Wed, 03 Mar 2021 23:59:57 +0000 [thread overview]
Message-ID: <m2tuprvldu.fsf@faryna.io> (raw)
In-Reply-To: <87zgzkwach.fsf@gnus.org>
Thanks for prompt reply Lars.
The error I get it's actually a warning from *Warning* buffer, that
welcomes me every time I start Emacs since update. There are
no backtrace after I activate debug-on-error and restart.
The problem occurs even when I deactivate japanese-holidays package.
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Adam Faryna <adam@faryna.io> writes:
>
>> Hi, since I updated Emacs to HEAD, my configuration of calendar-holidays
>> var throws errors on Emacs start (pasted below).
>>
>> I set calendar-holidays like this:
>>
>> (use-package japanese-holidays)
>>
>> (setq
>> general-holidays
>
> [...]
>
>> Errors I get:
>>
>> Error (holidays): Bad holiday list item: ((japanese-holiday-range (holiday-fi
>
> The rest of the configuration is perhaps not relevant here -- the
> problem is just in the "japanese-holidays" package? I'm not familiar
> with that package, and it doesn't seem to be available on GNU ELPA or
> Melpa? Where does it originate from?
>
> Also, could you `(setq debug-on-error t)', repeat whatever is giving you
> the error and post the resulting backtrace?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-03 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 0:40 bug#46883: 28.0.50; calendar-holidays var setup errors Adam Faryna via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-03 15:00 ` Lars Ingebrigtsen
2021-03-03 23:59 ` Adam Faryna via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-04 1:54 ` adam@faryna.io via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-04 11:37 ` Lars Ingebrigtsen
2021-03-05 0:34 ` adam--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-05 13:34 ` Lars Ingebrigtsen
2021-03-05 15:31 ` Stephen Berman
2021-03-05 20:10 ` adam--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-06 12:36 ` Lars Ingebrigtsen
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=m2tuprvldu.fsf@faryna.io \
--to=bug-gnu-emacs@gnu.org \
--cc=46883@debbugs.gnu.org \
--cc=adam@faryna.io \
--cc=larsi@gnus.org \
/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).