From: Ihor Radchenko <yantar92@posteo.net>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix org-agenda-skip-scheduled-if-deadline-is-shown bug
Date: Wed, 17 Jan 2024 13:10:00 +0000 [thread overview]
Message-ID: <87wms8hzrr.fsf@localhost> (raw)
In-Reply-To: <CH3PR84MB3424F0C09265426ADEB9912CC5732@CH3PR84MB3424.NAMPRD84.PROD.OUTLOOK.COM>
Morgan Smith <Morgan.J.Smith@outlook.com> writes:
> Maybe we could create some data-structure that represents an agenda and
> allow the user to manipulate that directly. I'm not really a fan of
> having a ton of variables controlling the agenda. Although I imagine I
> might gain some respect for it if I tried to implement this feature.
Agenda is one of the oldest codes we have in Org mode. It can certainly
see improvements and simplifications.
If you have ideas about providing better agenda customization, feel free
to share them.
>> Nothing is stagnated. I am just waiting for Bastien to chime in, if he
>> decides to. He is the person who can provide important context.
>> We allow up to one month for people to reply on the mailing list.
>> See https://orgmode.org/worg/org-mailing-list.html#org474747a
>>
> I was unaware of the one month policy. Thank you for letting me know.
> Due to that lack of a bug tracking system I have a fear that things on
> the mailing list would get lost. Maybe this fear is unfounded?
We do have a bug tracker - https://tracker.orgmode.org/bugs
Although it is still experimental.
In any case, I keep track of all the bugs and patches in my Org notes.
--
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>
next prev parent reply other threads:[~2024-01-17 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 20:45 [PATCH] Fix org-agenda-skip-scheduled-if-deadline-is-shown bug Morgan Smith
2023-12-31 14:32 ` Ihor Radchenko
2024-01-02 20:25 ` Morgan Smith
2024-01-03 15:29 ` Ihor Radchenko
2024-01-03 17:06 ` Morgan Smith
2024-01-04 14:04 ` Ihor Radchenko
2024-01-16 16:45 ` Morgan Smith
2024-01-16 18:52 ` Ihor Radchenko
2024-01-16 20:37 ` Morgan Smith
2024-01-17 13:10 ` Ihor Radchenko [this message]
2024-02-07 12:27 ` Ihor Radchenko
2024-02-07 16:15 ` Bastien Guerry
2024-02-07 16:25 ` 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=87wms8hzrr.fsf@localhost \
--to=yantar92@posteo.net \
--cc=Morgan.J.Smith@outlook.com \
--cc=bzg@gnu.org \
--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).