From: Ihor Radchenko <yantar92@gmail.com>
To: Eduardo Suarez <esuarez@itccanarias.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Planning links to tasks
Date: Mon, 03 Oct 2022 13:37:56 +0800 [thread overview]
Message-ID: <87o7utxya3.fsf@localhost> (raw)
In-Reply-To: <20221002193038.GA12424@itccanarias.org>
Eduardo Suarez <esuarez@itccanarias.org> writes:
> Hi, I have just implemented an approach to creating a hierarchy of links to
> tasks, so the hierarchy can be thought of a dependency tree (something like a
> Gantt but with no dates). This approach may be suitable if your org hierarchy
> is not already based on todo dependencies, and there are too many tasks to
> review them often.
>
> The idea is to be able to:
>
> - easily add an item to a plain list in a section named (e.g.)
> "Planning/Unplanned tasks", consisting of a link to a task in the same
> buffer (=org-plk-insert=),
>
> - move by text editing this list item into a hierarchy of items in a section
> named (e.g.) "Planning/Planned tasks", so hierarchy means dependency
> (somehow).
Have you been using your code for some time now or is it just an
experiment implementing your idea?
> Some improvements would be great:
> - update link description at point,
> - nice looking planning links (fontify?, have no idea),
> - use another flag for planning link instead of suffix,
> - check for planning links duplicates.
It would be helpful if you provide a more detailed demonstration of your
approach. I imagine something similar (in terms of presentation) to
https://blog.jethro.dev/posts/capturing_inbox/
It is hard to comment anything on your ideas without seeing how your
code actually works.
Also, if you want to hear suggestions about particular parts of the
code, please provide those parts instead of throwing the whole code - it
will make things easier for people who are only interested to answer a
specific question of yours.
> (defun edu/org-plk-description-from-id (target-id)
> "Planning link description from Link ID"
> (catch 'found
> (org-map-entries
> ;; break on first element found
> #'(throw 'found (edu/org-plk-format-description))
This is not a valid Elisp syntax.
Check out 13.7 Anonymous Functions section of Elisp manual.
> (let ((shift 0))
> ;; map over all links in the buffer
> (org-element-map (org-element-parse-buffer) 'link
> (lambda (link)
> (when (edu/org-plk-p link shift) ;; filter-in plk's
> (let* ((new-desc-text
> (edu/org-plk-description-from-id (org-element-property :path link)))
> ;; shifted because of previous description updates in this run
> (old-desc-start (+ shift (org-element-property :contents-begin link)))
> (old-desc-end (+ shift (org-element-property :contents-end link))))
You can also use a simple re-search-forward and not bother with `shift'.
Or use org-element-cache-map from the latest main.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-10-03 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 19:30 Planning links to tasks Eduardo Suarez
2022-10-02 19:42 ` Eduardo Suarez Santana
2022-10-03 5:37 ` Ihor Radchenko [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=87o7utxya3.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=esuarez@itccanarias.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).