emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eppo Math <eppolito.math@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-agenda-span treats 7 differently [9.4.6 (9.4.6-g3ba46c @ ~/.emacs.d/straight/build/org/)]
Date: Fri, 13 Jan 2023 09:25:50 +0000	[thread overview]
Message-ID: <878ri67plt.fsf@localhost> (raw)
In-Reply-To: <62a2389f-cf1f-9caa-7266-015f3e05d734@gmail.com>

Eppo Math <eppolito.math@gmail.com> writes:

> Many thanks in advance for taking the time to read this!
>
> Issue: In an org agenda block (fed to org-agenda-custom-commands), the
> number 7 passed to org-agenda-span causes the resulting block to begin
> on the first day of the week, ignoring org-agenda-start-day.
>
> Expected Behaviour: org-agenda-start-day and org-agenda-span should be
> options with independent behaviours.
>
> Actual Behaviour: When org-agenda-span is set to 7, the given argument
> org-agenda-start-day is ignored.

This is because of `org-agenda-start-on-weekday' defaulting to 1.
You can bind it to nil in your custom agenda view.

I think we can update the docstrings for `org-agenda-start-day' and
`org-agenda-start-on-weekday' explaining that the latter takes
precedence when agenda span is a week or more.

Will it be enough for you?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-01-13  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 18:09 [BUG] org-agenda-span treats 7 differently [9.4.6 (9.4.6-g3ba46c @ ~/.emacs.d/straight/build/org/)] Eppo Math
2023-01-13  9:25 ` Ihor Radchenko [this message]
     [not found]   ` <01e57c89-e570-ff4d-5286-ff4c0a17f703@gmail.com>
     [not found]     ` <87fscc88lj.fsf@localhost>
2023-01-16 10:46       ` Ihor Radchenko

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=878ri67plt.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=eppolito.math@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/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).