From: Mats Kindahl <mats.kindahl@oracle.com>
To: Juan Pechiar <juan@pechiar.com>, emacs-orgmode@gnu.org
Subject: Re: Filter in Captured Column View
Date: Tue, 18 Mar 2014 15:19:18 +0100 [thread overview]
Message-ID: <532855E6.9010605@oracle.com> (raw)
In-Reply-To: <20140318140848.GA13287@soloJazz.com>
Thanks Juan,
It seems to work, so I'll use that for now, but having some sort of
filtering supported would be a great feature.
I'll play around a little and see if that can be added.
Best wishes,
Mats Kindahl
On 03/18/2014 03:08 PM, Juan Pechiar wrote:
> Hi Mats,
>
> You can add
>
> :skip-empty-rows t
>
> to the columnview header, so that rows with no Status property will
> not show.
>
> This, however, will also hide the "Release" headers. Workaround is to
> add a dummy 'Status' property to these.
>
> Doc here: http://orgmode.org/manual/Capturing-column-view.html
>
> .j.
>
> On Tue, Mar 18, 2014 at 12:38:52PM +0100, Mats Kindahl wrote:
>> I am using the capture column view to capture the contents of a subtree
>> at the beginning of the subtree. However, there are a lot of sections
>> that do not contain anything interesting for the capture in question, so
>> I would like to filter out anything except trees with certain tags.
>>
>> So, for the example below, it shows some headers at the beginning that I
>> would like to avoid showing. Only in information on the individual
>> releases should be shown as groups.
>>
>> Best wishes,
>> Mats Kindahl
>>
>> * Report
>> :PROPERTIES:
>> :COLUMNS: %ITEM %Status
>> :END:
>>
>> #+BEGIN: columnview :hlines 3 :id local
>> | ITEM | Status |
>> |--------------------------+-----------|
>> | * Report | |
>> |--------------------------+-----------|
>> | ** Uninteresting summary | |
>> |--------------------------+-----------|
>> | ** Details | |
>> |--------------------------+-----------|
>> | *** Release 1 | |
>> | **** Feature #1 | Design |
>> |--------------------------+-----------|
>> | *** Release 2 | |
>> | **** Feature #2 | Confused |
>> | **** Feature #3 | Completed |
>> | **** Feature #4 | Coding |
>> |--------------------------+-----------|
>> | *** Release 3 | |
>> | **** Feature #5 | Baffled |
>> #+END:
>>
>> ** Uninteresting summary
>> ** Details
>> *** Release 1
>>
>> **** Feature #1
>> :PROPERTIES:
>> :Status: Design
>> :END:
>>
>> *** Release 2
>>
>> **** Feature #2
>> :PROPERTIES:
>> :Status: Confused
>> :END:
>>
>> **** Feature #3
>> :PROPERTIES:
>> :Status: Completed
>> :END:
>>
>> **** Feature #4
>> :PROPERTIES:
>> :Status: Coding
>> :END:
>>
>> *** Release 3
>>
>> **** Feature #5
>> :PROPERTIES:
>> :Status: Baffled
>> :END:
--
Senior Principal Software Developer
Oracle, MySQL Department
prev parent reply other threads:[~2014-03-18 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 11:38 Filter in Captured Column View Mats Kindahl
2014-03-18 14:08 ` Juan Pechiar
2014-03-18 14:19 ` Mats Kindahl [this message]
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=532855E6.9010605@oracle.com \
--to=mats.kindahl@oracle.com \
--cc=emacs-orgmode@gnu.org \
--cc=juan@pechiar.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).