From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ecbrown@ericcbrown.com, enometh@meer.net, emacs-devel@gnu.org
Subject: Re: master 9b762c35a1: Add Sefirot to Omer counting
Date: Mon, 09 May 2022 19:20:09 -0400 [thread overview]
Message-ID: <E1noCfh-0002lu-P6@fencepost.gnu.org> (raw)
In-Reply-To: <83wneuuccs.fsf@gnu.org> (message from Eli Zaretskii on Mon, 09 May 2022 15:20:03 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > The biblical references for the Parashat HaShavua and its Haftorah are
> > definitely religious in nature.
> And the Hebrew calendar itself isn't?
It has to do with religion to some extent, but the crucial thing is
that it is a calendar. It consists of names of days.
> The proposal was NOT to cite those texts in Emacs, the proposal was
> just to _name_ them.
I think we're using the word "cite" with two different meanings, both
valid. We're talking about including in Emacs the names of certain biblical
texts, right?
Where do we draw the line?
The natural place would be between
(1) identifications/names of specific days, and
(2) specific things some groups customarily DO on specific named days.
The first is part of the calendar; the second is an adjunct used with
the calendar.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-05-09 23:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165116151120.23031.9576273880387199540@vcs2.savannah.gnu.org>
[not found] ` <20220428155832.00202C01683@vcs2.savannah.gnu.org>
2022-04-28 16:38 ` master 9b762c35a1: Add Sefirot to Omer counting Stefan Monnier
2022-04-28 16:50 ` Eli Zaretskii
2022-04-28 17:21 ` Stefan Monnier
2022-05-04 8:27 ` Madhu
2022-05-05 18:37 ` Richard Stallman
2022-05-05 19:10 ` Eli Zaretskii
2022-05-06 23:18 ` Richard Stallman
2022-05-07 6:06 ` Eli Zaretskii
2022-05-07 14:16 ` Madhu
2022-05-07 23:08 ` Richard Stallman
2022-05-08 5:27 ` Eli Zaretskii
2022-05-08 23:39 ` Richard Stallman
2022-05-09 2:24 ` Madhu
2022-05-09 11:34 ` Eric Brown
2022-05-09 12:20 ` Eli Zaretskii
2022-05-09 14:41 ` Eric Brown
2022-05-09 14:52 ` Eric Brown
2022-05-09 18:53 ` Sam Steingold
2022-05-09 23:20 ` Richard Stallman [this message]
2022-05-10 2:31 ` Eli Zaretskii
2022-05-11 9:04 ` Richard Stallman
2022-05-11 11:49 ` Eli Zaretskii
2022-05-13 15:09 ` Richard Stallman
2022-05-13 15:41 ` Eli Zaretskii
2022-05-09 23:21 ` Richard Stallman
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=E1noCfh-0002lu-P6@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ecbrown@ericcbrown.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.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 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).