From: Arthur Miller <arthur.miller@live.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Checkboxes in headings - opinions wanted
Date: Tue, 04 May 2021 12:47:25 +0200 [thread overview]
Message-ID: <AM9PR09MB49778D498F3714B63AD802B4965A9@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <871ran190g.fsf@localhost> (Ihor Radchenko's message of "Tue, 04 May 2021 11:18:55 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> Arthur Miller <arthur.miller@live.com> writes:
>> ... Example can be seen in attached screenshot from
>> my init file where I use org headings to form a list of packages to
>> install, and checkboxes to indicate if a package configuration is used
>> or not.
>
> Depending on details of your workflow, you might also use
> org-toggle-comment for indication of configuration usage. As a bonus, if
Actually I am thinking of re-purposing TODO for "pin to repository"
purpose, so that is why I needed a more general checkbox independent of
TODO states. I am using planning on using tags for some other stuff.
> you use literate config, commenting the heading will also disable
> tangling for that heading.
>
I don't use tangling
from org-mode, I tangle all code myself. I have written a small
optimizer so I am generating actual init file from the literal config,
it is a small application in org-mode. You can see hacked TODO (per
file) in "Generator" section below the ";; og hacks" comment of
init.org, if you are interested.
https://github.com/amno1/.emacs.d
next prev parent reply other threads:[~2021-05-04 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 7:00 Checkboxes in headings - opinions wanted Arthur Miller
2021-05-03 8:32 ` Bastien
2021-05-03 8:42 ` Timothy
2021-05-03 15:25 ` Arthur Miller
2021-05-03 15:21 ` Arthur Miller
2021-05-04 3:18 ` Ihor Radchenko
2021-05-04 10:47 ` Arthur Miller [this message]
2021-05-03 15:50 ` Russell Adams
2021-05-03 18:28 ` Arthur Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM9PR09MB49778D498F3714B63AD802B4965A9@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.