From: Kaushal Modi <kaushal.modi@gmail.com>
To: Carsten Dominik <dominik@uva.nl>, Adam Porter <adam@alphapapa.net>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: ANN: org-sticky-header
Date: Tue, 18 Apr 2017 13:57:14 +0000 [thread overview]
Message-ID: <CAFyQvY1ErL6kjpa8siuivWRO-Xfi4grN64LQdAAbcqde+oyvhg@mail.gmail.com> (raw)
In-Reply-To: <CADn3Z2LpGjdKu1_AJ=Pt5i-BXQc7zoctNV_7Qb8r0Oa63tO6eg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]
On Tue, Apr 18, 2017 at 9:30 AM Carsten Dominik <dominik@uva.nl> wrote:
> Hi Adam,
>
> this is great, I love it!
>
> I am wondering if you would consider the possibility to show on only the
> most recent heading, but, space permitting, the outline path - maybe in
> reverse order as to keep the sticky heading itself in the left-most column.
>
> Something like
>
> *** current level | ** level above | * top level
>
> you could use `org-get-outline-path' to get the other headings up the tree.
>
> I don't necessarily think it should be the default, but it could be an
> option.
>
> Cheers
>
On that note, there is also org-eldoc.el in contrib/ that sort of does what
you want.
"sort of" because:
- Shows the breadcrumbs in the echo area instead of in header.
- Shows that only when point is on an org heading, not when in the body.
[image: pasted1]
--
Kaushal Modi
[-- Attachment #1.2: Type: text/html, Size: 1557 bytes --]
[-- Attachment #2: pasted1 --]
[-- Type: image/png, Size: 13349 bytes --]
next prev parent reply other threads:[~2017-04-18 13:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 23:41 ANN: org-sticky-header Adam Porter
2017-04-18 3:28 ` Eric Abrahamsen
2017-04-18 23:10 ` Adam Porter
2017-04-18 13:29 ` Carsten Dominik
2017-04-18 13:51 ` John Kitchin
2017-04-18 13:55 ` Carsten Dominik
[not found] ` <2357163c15c549d3a13e923dc7d5f6ea@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-18 17:22 ` Eric S Fraga
2017-04-18 19:16 ` Leslie Watter
2017-04-18 23:09 ` Adam Porter
2017-04-18 23:07 ` Adam Porter
2017-04-18 13:57 ` Kaushal Modi [this message]
2017-04-18 23:06 ` Adam Porter
2017-04-19 5:46 ` Carsten Dominik
2017-04-19 5:52 ` Carsten Dominik
2017-04-19 6:11 ` Carsten Dominik
2017-04-19 16:44 ` Adam Porter
2017-04-19 21:33 ` Adam Porter
2017-04-23 0:06 ` Charles C. Berry
2017-04-24 5:37 ` Infinite loop with org-inlinetask and org-sticky-header [was Re: ANN: org-sticky-header] Adam Porter
2017-04-18 23:51 ` ANN: org-sticky-header Adam Porter
[not found] <a8497792e3994095a9867e508a90bb3f@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-18 7:21 ` Eric S Fraga
2017-04-18 23:53 ` Adam Porter
[not found] ` <ea4543fad79c4e9687992e41ef77062e@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-19 6:07 ` Eric S Fraga
2017-04-19 15:03 ` Carsten Dominik
2017-04-19 16:40 ` Adam Porter
2017-04-19 21:33 ` Adam Porter
[not found] ` <7a7a9e1653114a578dcb91186e8a4cab@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-24 6:38 ` Eric S Fraga
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=CAFyQvY1ErL6kjpa8siuivWRO-Xfi4grN64LQdAAbcqde+oyvhg@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=adam@alphapapa.net \
--cc=dominik@uva.nl \
--cc=emacs-orgmode@gnu.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).