From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: What is a week?
Date: Tue, 11 Apr 2023 18:34:47 +0700 [thread overview]
Message-ID: <u13gko$8so$1@ciao.gmane.io> (raw)
In-Reply-To: <87ile2u3v9.fsf@localhost>
On 11/04/2023 17:09, Ihor Radchenko wrote:
> Max Nikulin writes:
>> So at least some people expect 7, not 0. I would say, both variants
>> should be acceptable.
>
> Would you be interested to make a patch?
Not really. I expect something like
> (let* ((ws (mod (or wstart 1) 7))
> (diff (+ (* -7 shift) (- dow ws) (if (> dow ws) 0 7))))
I have realized that current behavior may be considered as a feature.
Agenda obtained on Sunday allows to review previous working week. So
:weekstart 0 and :weekstart 7 might behave differently. However to make
it full-fledged feature, it is necessary to introduce first_workday in
addition to first_weekday. See properties reported by
locale -k LC_TIME
next prev parent reply other threads:[~2023-04-11 11:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 3:35 What is a week? Marcin Borkowski
2023-04-10 4:03 ` Marcin Borkowski
2023-04-10 6:04 ` Jude DaShiell
2023-04-10 7:46 ` Ihor Radchenko
2023-04-10 11:51 ` Max Nikulin
2023-04-10 12:07 ` Tim Landscheidt
2023-04-11 10:08 ` Ihor Radchenko
2023-04-24 15:47 ` Max Nikulin
2023-04-11 10:09 ` Ihor Radchenko
2023-04-11 11:34 ` Max Nikulin [this message]
2023-04-11 14:21 ` Marcin Borkowski
2023-04-23 17:57 ` Ihor Radchenko
2023-04-23 19:06 ` Marcin Borkowski
2023-04-23 19:18 ` Ihor Radchenko
2023-04-24 4:13 ` Marcin Borkowski
2023-04-24 6:26 ` Ihor Radchenko
2023-04-24 19:44 ` Marcin Borkowski
2023-04-24 20:05 ` Ihor Radchenko
2023-08-06 18:29 ` Bastien Guerry
2023-04-25 14:43 ` [PATCH] org-clock.el: Fix week start != 1 Max Nikulin
2023-05-07 8:06 ` Ihor Radchenko
2023-08-06 18:27 ` What is a week? Bastien
2023-04-24 15:13 ` Max Nikulin
2023-04-24 19:26 ` Marcin Borkowski
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='u13gko$8so$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).