From: Uwe Brauer <email@example.com>
Subject: Re: TODO or checkboxes in org tables
Date: Sat, 02 May 2020 21:33:41 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
>>> "AK" == Axel Kielhorn <email@example.com> writes:
I am not sure my first answer made it, so I apologize for a possible
> Hi Uwe,
>> I have an orgtable with a lot of useful information, I would like to add
>> a column either for TODOS or checkboxes but it seems not work any idea
>> whether such an addon package exist or any change that such a feature
>> will be implemented?
> I use a different approach.
> I store the information in a normal org structure with TODO keywords.
> I hide the checkboxes (and other meta information) in a drawer.
I thought about this as well, but the table is an import form an excel
documente and contains a row of 70 different persons, so to transform
this to a normal org structure would require some work, I presume.
In any case, thanks for you example I will try it out.
> From this I generate a column view to present the information in a table.
> You can generate different column views from the same data set.
> I used the second version for years but recently discovered the :match argument.
> If you mark the actual data as :noexport: only the table will be printed.
A last question, which the command to generate the table
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-05-02 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:28 TODO or checkboxes in org tables Uwe Brauer
2020-05-02 8:46 ` Axel Kielhorn
2020-05-02 19:33 ` Uwe Brauer [this message]
2020-05-03 7:05 ` Axel Kielhorn
2020-05-07 17:05 ` Uwe Brauer
2020-05-08 4:37 ` Axel Kielhorn
2020-05-08 9:21 ` Uwe Brauer
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).