From: Karl Fogel <email@example.com>
Subject: Re: [PROPOSAL] New function `org-headings-to-point' and displayer.
Date: Tue, 03 Dec 2019 17:34:40 -0600 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Adam Porter's message of "Tue, 03 Dec 2019 16:06:30 -0600")
On 03 Dec 2019, Adam Porter wrote:
>This seems to duplicate functionality from org-get-outline-path. As
>well, org-eldoc displays in the minibuffer the outline path for the
>heading at point.
Thank you, Adam -- I didn't know about those. I had searched for something like that before implementing my own, but I think I searched using the term "heading" or something instead of "outline", unfortunately, so I never found them.
Now that I know about `org-display-outline-path', the one improvement I'd like to make is to enable it to display the headings with per-level indentation, and treat the first level specially (with an anchoring dot instead of a directional arrow), as my code did. It's a lot more readable that way displayed in the minibuffer.
I suppose I would implement this by adding two new optional arguments to `org-display-outline-path':
* `per-level-indentation': add a newline followed by <this string LEVEL-1 times> in front of each SEPARATOR
* `level-1-prefix': a special prefix for the first level's heading
...and make corresponding changes to the helper functions of course. There should also be some way to access the new functionality interactively; the solution might be a new interactive wrapper function with its own name, or maybe some new variables? I don't know; I haven't thought it all the way through yet.
Is there any interest in or opposition to such a patch? I'd like to get a sense of whether it would be able to land in Org Mode before I start working on it.
next prev parent reply other threads:[~2019-12-03 23:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 2:56 [PROPOSAL] New function `org-headings-to-point' and displayer Karl Fogel
2019-12-03 7:30 ` Diego Zamboni
2019-12-03 8:47 ` Cheong Yiu Fung
2019-12-03 22:06 ` Adam Porter
2019-12-03 23:34 ` Karl Fogel [this message]
2019-12-04 2:38 ` Adam Porter
2019-12-05 3:04 ` Karl Fogel
2019-12-05 8:42 ` Adam Porter
2019-12-05 8:47 ` Adam Porter
2019-12-05 22:36 ` Karl Fogel
2019-12-03 23:36 ` Karl Fogel
2019-12-04 2:20 ` Adam Porter
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).