From: Jean Louis <bugs@gnu.support>
To: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Configure Helm Source from org-tags-view
Date: Thu, 8 Aug 2019 21:13:13 +0200 [thread overview]
Message-ID: <20190808191313.GW23122@protected.rcdrun.com> (raw)
In-Reply-To: <CAC=HedDoz-dhW-nZbGJzXoTQp_-SfRcm4h1EoOLzLC0Wws5eBA@mail.gmail.com>
* Nathan Neff <nathan.neff@gmail.com> [2019-08-08 18:50]:
> Hello all,
>
> Has anyone created a Helm source from the results of org-agenda?
>
> Specifically org-tags-view I think would be a cool Helm source to
> configure where the headings that have certain tags could be displayed
> by Helm.
>
> I looked @ the code for org-tags-view and it's fairly straight
> forward - however, I think that the function itself is tightly
> coupled between finding the results and displaying the results. In
> other words, there's no easy function that I see which would provide
> headings that match a tags search that I could use as a Helm source.
If tag is 'staff, this below will give structure out:
(org-scan-tags 'agenda '(staff lambda (todo tags-list level) (progn
(setq org-cached-props nil) (or (and (member staff tags-list)))))
org--matcher-tags-todo-only)
Now `org-scan-tags` could be inspected if it constructs some lists,
alist, that are somewhat nicer than such output.
But that output can be converted to HELM completion.
Jean
next prev parent reply other threads:[~2019-08-08 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 16:49 Configure Helm Source from org-tags-view Nathan Neff
2019-08-08 19:00 ` Jean Louis
2019-08-08 19:13 ` Jean Louis [this message]
2019-08-08 20:03 ` Nathan Neff
2019-08-08 20:23 ` Nathan Neff
2019-08-08 20:30 ` Jean Louis
2019-08-08 20:46 ` Nathan Neff
2019-08-08 21:20 ` Jean Louis
2019-08-08 20:29 ` Jean Louis
2019-08-09 11:07 ` Adam Porter
2019-08-09 17:57 ` Nathan Neff
2019-08-09 19:13 ` Adam Porter
2019-08-09 21:20 ` Nathan Neff
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=20190808191313.GW23122@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=nathan.neff@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).