From: Samuel Wales <samologist@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: ANN: org-ql agenda block support
Date: Sat, 7 Sep 2019 17:46:43 -0700 [thread overview]
Message-ID: <CAJcAo8u3NC=fB3=Xuz2pYXydZB-RtD9X7NbMeiMbcYVZaMo8XQ@mail.gmail.com> (raw)
In-Reply-To: <87k1akgory.fsf@alphapapa.net>
thanks for your clarification. i had thought that it did the
daily/weekly agenda also. that's the one that is slow for me.
On 9/7/19, Adam Porter <adam@alphapapa.net> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
>> i was merely trying to get a sense of the degree to which it is a
>> drop-in replacement (which i think you have said it is not).
>
> Right, it doesn't do everything Org Agenda does. Since Org Agenda does
> also serve as a kind of "search view," org-ql can largely serve as a
> replacement for that aspect of it, providing several advantages. But it
> doesn't implement the daily/weekly-style agenda view, so it doesn't
> replace that part of it.
>
> I'll probably refactor and rename it soon, removing "agenda" from the
> name to reduce confusion. In the future I may work on an a
> daily/weekly-style view as well, which might again be called
> org-ql-agenda.
>
>> the question is whether the display can be made similar enough to a
>> highly customized traditional agenda so that diff of the agenda buffer
>> can find any bugs in either traditional or ql agenda.
>
> In some cases, perhaps, but while I do want to add more features from
> Org Agenda, my goal isn't necessarily to reproduce it in every aspect.
>
>> respecting things like org-agenda-inactive-leader will reduce the need
>> to munge in order to make them similar enough. not a big deal.
>
> That's an interesting feature. If I do support it in the future, it
> will probably come after implementing a more complex Agenda-like view
> that will be quite different from Org Agenda.
>
>> adding text properties like the agenda does is great for that too as a
>> lot of user code likely uses them. so that will stop actual breakage.
>
> Yes, with respect to text properties, I do intend to copy what Org
> Agenda does, for the most part.
>
> Thanks for your feedback.
>
>
>
--
The Kafka Pandemic
What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.
next prev parent reply other threads:[~2019-09-08 0:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 15:07 ANN: org-ql agenda block support Adam Porter
2019-08-12 15:39 ` Mikhail Skorzhinskii
2019-08-31 5:20 ` Adam Porter
2019-09-12 19:19 ` Mikhail Skorzhinskii
2019-09-17 4:36 ` Adam Porter
2019-08-25 17:38 ` Milan Zamazal
2019-08-25 18:18 ` Samuel Wales
2019-08-30 10:44 ` Adam Porter
2019-08-31 0:20 ` Samuel Wales
2019-08-31 5:01 ` Adam Porter
2019-09-07 0:43 ` Samuel Wales
2019-09-07 14:32 ` Adam Porter
2019-09-08 0:46 ` Samuel Wales [this message]
2019-08-30 9:19 ` Adam Porter
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='CAJcAo8u3NC=fB3=Xuz2pYXydZB-RtD9X7NbMeiMbcYVZaMo8XQ@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=adam@alphapapa.net \
--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).