From: Philip Kaludercic <firstname.lastname@example.org>
Subject: Some feature requests/questions
Date: Tue, 19 Apr 2022 15:49:12 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
I was wondering if someone could help me out to solve these annoyances I
have been having with Org:
1. Most things I would like to clock are related to Emacs, but I often
forget to check my agenda first, clock in, then clock out. Is there
some way I can automatically manage clocking when I enter a
directory/kill the last buffer?
2. Capturing is configured by describing what keys should do via
`org-capture-templates'. Is there some way to use bookmark-like
strings and completing-read?
3. Related to the previous point, is there a way to configure capture
templates /in/ org files? That would make it easier to dynamically
add notes, without having to do so centrally, in my configuration
4. Limiting until when events may repeat, without having to duplicate
timestamps manually (or via `org-clone-subtree-with-time-shift').
Better yet being able to do so for an entire subtree/file, and have
the property inherit itself.
All of these issues I have encountered by trying to use Org for the last
few years at University, managing courses, notes, assignment due dates,
appointments, etc. The friction that these issues cause often have me
become sloppy after a while, which defeats the entire purpose.
I have little experience with the Org codebase, but would be interested
in helping to implement these features, in so far they don't just exist
and I haven't found out about them.
next reply other threads:[~2022-04-19 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:49 Philip Kaludercic [this message]
2022-04-19 16:34 ` Eric S Fraga
2022-04-27 0:52 ` Tim Cross
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).