From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Display-level automatic subtree numbering
Date: Sun, 28 Oct 2018 00:36:04 +0200 [thread overview]
Message-ID: <8736srggq3.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <8736sugjc5.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 25 Oct 2018 17:02:50 +0200")
On 2018/10/25 at 17:02, Nicolas Goaziou wrote:
> "Garreau, Alexandre" <galex-713@galex-713.eu> writes:
>> Le 24/10/2018 à 13h40, Nicolas Goaziou a écrit :
>>> But you don't need to number the whole buffer, do you?
>>
>> At least the screen.
>>
>>> A breadcrumb like feature could be enough. E.g., you hit <SPC> at the
>>> beginning of a headline and get the numbering in addition to the
>>> outline path.
>>
>> I’d prefer. I find sad that all export backend supports this while raw
>> emacs doesn’t.
>
> Output from export back-ends is static. A currently-edited Org document
> isn't.
That’s why it’d require special font-lock-like and lazy update
facilities : when you insert (or move) a node, you need to update the
same-level following nodes (or exchange numbering with the near node).
>> It is neat to see, and to, just by looking at the
>> screen, which section has which number.
>
> You may be interested in "org-outline-numbering" package, then. It seems
> to implement what you want.
No it doesn’t update anything, and doesn’t color number compatibly with
outlining. Also it’s not integrated in org and only available in melpa,
unsigned.
next prev parent reply other threads:[~2018-10-27 22:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 18:29 Display-level automatic subtree numbering Garreau, Alexandre
2018-10-23 18:33 ` John Kitchin
2018-10-23 19:58 ` Garreau, Alexandre
2018-10-24 7:38 ` Nicolas Goaziou
2018-10-24 8:54 ` Garreau, Alexandre
2018-10-24 11:40 ` Nicolas Goaziou
2018-10-24 11:49 ` Garreau, Alexandre
2018-10-25 15:02 ` Nicolas Goaziou
2018-10-27 22:36 ` Garreau, Alexandre [this message]
2018-11-01 17:49 ` Nicolas Goaziou
2018-11-02 6:51 ` Eric S Fraga
2018-11-02 7:12 ` Marco Wahl
2018-11-04 5:09 ` Amin Bandali
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=8736srggq3.fsf@portable.galex-713.eu \
--to=galex-713@galex-713.eu \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).