emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 23 Oct 2018 21:58:06 +0200	[thread overview]
Message-ID: <87bm7kjv01.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <CAJ51ETr0W5DL7HyaxAbkvxGLEJx66rSioyizdCXS5LP0o6oPwQ@mail.gmail.com> (John Kitchin's message of "Tue, 23 Oct 2018 14:33:47 -0400")

On 2018-10-23 at 14:33, John Kitchin wrote:
> There are some answers at
> https://emacs.stackexchange.com/questions/32396/complete-path-numbering-of-org-mode-headlines-and-plain-lists

Interesting.  Thank you (I’m unfortunately not very friend with search
engines): that also raises altogether the question of tables of contents.

But that doesn’t answer the question: why “doesn’t it exist”? shouldn’t
these functions be mainlined, if legally permitted?

Btw, since I read overlays create slowness proportional to their
numbers, and that’s surely a lot of overlays, wouldn’t it be better
using text properties?  these support `display' as well, and, I checked,
even for strings of different length: is there a particular reasons they
wouldn’t work as well?

  reply	other threads:[~2018-10-23 19:58 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 [this message]
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
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=87bm7kjv01.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).