unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Emanuele M. Monterosso" <emanuele.monterosso@gmail.com>
Cc: 60987@debbugs.gnu.org
Subject: bug#60987: 30.0.50; Calendar not accepting custom holidays
Date: Sat, 21 Jan 2023 17:50:00 +0200	[thread overview]
Message-ID: <83edrnlwev.fsf@gnu.org> (raw)
In-Reply-To: <D5516BA7-7132-4DD5-9BEB-E9E400ED5839@hxcore.ol> (emanuele.monterosso@gmail.com)

[Please keep the bug address on the CC list.]

> Date: Sat, 21 Jan 2023 15:53:49 +0100
> From: "Emanuele M. Monterosso" <emanuele.monterosso@gmail.com>
> 
> >Please show step by step instructions to reproduce the issue starting
> >from "emacs -Q".  It is hard to look into an issue without such a
> >recipe, as the details are usually important.
> >
>  
> >Thanks.
>  
> Steps to reproduce:
> 
> * emacs -Q -> scratch-buffer
> * Copy this snippet from the EmacsWiki 
> 
> (setq holiday-general-holidays
>       '((holiday-fixed 1 1 "Capodanno")
>         (holiday-fixed 5 1 "1 Maggio")
>         (holiday-fixed 4 25 "Liberazione")
>         (holiday-fixed 6 2 "Festa Repubblica")
> ))
>  
> * C-x C-e to eval the snippet
> * Either open the calendar or M-x holiday-list RET RET RET All and they do not appear at all. However,
> 
> they do appear if you do M-x holiday-list RET RET RET General.

For me they appear both with "All" and with "General" if I invoke
holiday-list.

Also, I don't have commit 8aae5fbaf29ee3d845e2bb40ef728765a2246e35 in
my clone of the Emacs Git repository.  Which Git repository are you
using to build Emacs?





  parent reply	other threads:[~2023-01-21 15:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 14:00 bug#60987: 30.0.50; Calendar not accepting custom holidays Emanuele M. Monterosso
2023-01-21 14:18 ` Eli Zaretskii
     [not found]   ` <D5516BA7-7132-4DD5-9BEB-E9E400ED5839@hxcore.ol>
2023-01-21 15:50     ` Eli Zaretskii [this message]
2023-01-21 16:04       ` bug#60987: R: " Emanuele M. Monterosso
2023-01-22 13:20         ` Eli Zaretskii
2023-01-22 14:59           ` bug#60987: R: " Emanuele M. Monterosso
2023-01-22 15:09             ` Eli Zaretskii
2023-01-22 15:26               ` bug#60987: R: " Emanuele M. Monterosso
2023-01-22 15:41                 ` Eli Zaretskii
2023-01-22 15:44                 ` Eli Zaretskii
     [not found]                   ` <9286A4EA-1671-4016-8DD5-46217E56A94F@hxcore.ol>
2023-01-22 17:07                     ` Eli Zaretskii
2023-01-23 16:07       ` Michael Heerdegen
2023-01-24 10:14         ` bug#60987: R: " Emanuele M. Monterosso
2023-01-24 15:26           ` Michael Heerdegen
2023-01-24 16:34             ` bug#60987: R: " Emanuele M. Monterosso
2023-01-24 16:57               ` Michael Heerdegen
2023-01-24 17:24                 ` bug#60987: R: " Emanuele M. Monterosso
2023-01-24 20:17                   ` Michael Heerdegen
2023-01-24 21:12                     ` bug#60987: R: " Emanuele M. Monterosso
2023-01-24 21:19                       ` Michael Heerdegen
2023-01-24 22:09                         ` bug#60987: R: " Emanuele M. Monterosso
2023-01-24 22:32                           ` Michael Heerdegen
2023-01-24 22:46                             ` Emanuele M. Monterosso
2023-01-25 13:26                               ` 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

  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=83edrnlwev.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60987@debbugs.gnu.org \
    --cc=emanuele.monterosso@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 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).