emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nathan Neff <nathan.neff@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Configure Helm Source from org-tags-view
Date: Fri, 9 Aug 2019 12:57:28 -0500	[thread overview]
Message-ID: <CAC=HedA3ZUUjM9VhiKv-dTHa+JsEZE7P34x_Oo-2WCsp5v0LrQ@mail.gmail.com> (raw)
In-Reply-To: <87zhki61h0.fsf@alphapapa.net>

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

<whine>I know, but rifle has sooooo many dependencies</whine>

Rifle is truly awesome, I just have to convince myself to trust
f.el and d.el or whatever those one-letter libraries are :-)

Thanks,
--Nate


On Fri, Aug 9, 2019 at 6:10 AM Adam Porter <adam@alphapapa.net> wrote:

> Nathan Neff <nathan.neff@gmail.com> writes:
>
> > 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.
> >
> > I think I would need to copy quite a bit of code from org-tags-view into
> a different
> > function to create a Helm source.  Am I missing something?
> >
> > Has anyone else done something similar?
>
> That's what helm-org-rifle is for.  For example, later in the thread you
> mentioned searching for a "staff" tag.  That would be very easy:
>
> 1.  M-x helm-org-rifle-agenda-files RET (I have it bound to a key).
> 2.  Type ":staff:".
> 3.  See results.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2033 bytes --]

  reply	other threads:[~2019-08-09 17:57 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
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 [this message]
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='CAC=HedA3ZUUjM9VhiKv-dTHa+JsEZE7P34x_Oo-2WCsp5v0LrQ@mail.gmail.com' \
    --to=nathan.neff@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).