emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Fri, 30 Aug 2019 17:20:20 -0700	[thread overview]
Message-ID: <CAJcAo8s8S_=k=PLtifYYCkVybPbyCU7TLJkvOr6zhAnjuUrHfQ@mail.gmail.com> (raw)
In-Reply-To: <87o907kk4i.fsf@alphapapa.net>

thanks, looks gorgeous!  i will file it for a possible future time
when i can run it, diff it with existing agenda to make sure it's the
same for me, and just switch over to it.  (i use 2d and 7d agendas and
text search view with and without inactive.)

i'll ask a couple of questions.

a while back i posted some notes on something that i was going to
implement (but wasn't able to), because somebody asked for it, hoping
that the notes would help him/her.

the idea was that we can resurrect the timeline view, for all agenda
files instead of only one, merely by a use of a text search custom
agenda view.  timestamps go where categories currently go.  sorted by
that ts.

if an entry has more than one ts (active bare, inactive bare including
on header, or planning -- other stuff requires org support), then it
will get more than one agenda line.

so this requires modifying that list that is there for the user to
modify tasks before displaying them.

can any of this stuff do that?

i keep wanting this feature: do a text search and have all matching
org-agenda-files outline entries show, with more than one agenda line
if more than one ts in entry, sorted by that ts.

so for example you search for "melatonin" (or even "." meaning all
entries, such as for an agenda restriction) and then you get to see
the most recent thing you did for melatonin or in that restriction at
the top.  and everything else you did below.  (assuming reverse sort.)

i can post more accurate and precise details if needed, but i wanted
to know if you think your work can support this.

also, does it support all the usual variables for leaders and faces and so on?

it all sounds promising.

more speed and beautiful sexps!  what more could we ask for?  :)


On 8/30/19, Adam Porter <adam@alphapapa.net> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
>> i have been watching these developments with interest.  i want a
>> faster 2-day agenda, and really like the idea of a lisp syntax for
>> querying, perhaps one that can combine text search with structured.
>>
>> so just so it's known that there is otherwise silent interest.
>> limited in computer use so cannot switch but following.
>
> I appreciate the feedback nonetheless.
>
> A two-day agenda could be done something like this:
>
>     (org-ql-agenda (org-agenda-files)
>       (and (or (deadline :from today :to +1)
>                (scheduled :from today :to +1)
>                (ts-active :from today :to +1))
>            (not (done)))
>       :sort (date priority todo)
>       :super-groups ((:auto-planning t)))
>
> To show deadlined entries taking org-deadline-warning-days into account,
> more like the traditional Org Agenda, use (deadline auto), like:
>
>     (org-ql-agenda (org-agenda-files)
>       (and (or (deadline auto)
>                (scheduled :from today :to +1)
>                (ts-active :from today :to +1))
>            (not (done)))
>       :sort (date priority todo)
>       :super-groups ((:auto-planning t)))
>
> Grouping by date in this example is done with the org-super-agenda
> :auto-planning selector, which uses the earliest planning timestamp in
> an entry.  So it's not exactly like Org Agenda, but it approximates what
> you're asking for, and org-ql's built-in caching may provide a speedup
> for subsequent calls.
>
> Here's an example that's similar to the Org Agenda's Log Mode:
>
>     (org-ql-agenda
>       (or (and (not (done))
>                (or (habit)
>                    (deadline auto)
>                    (scheduled :to today)
>                    (ts-active :on today)))
>           (closed :on today))
>       :sort (date priority todo))
>
>
>
>


-- 
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.

  reply	other threads:[~2019-08-31  0:20 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 [this message]
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
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='CAJcAo8s8S_=k=PLtifYYCkVybPbyCU7TLJkvOr6zhAnjuUrHfQ@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).