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: Wed, 24 Oct 2018 10:54:52 +0200 [thread overview]
Message-ID: <874ldbhggz.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <87h8hbyeu5.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 24 Oct 2018 09:38:10 +0200")
Le 24/10/2018 à 09h38, Nicolas Goaziou a écrit :
> Hello,
>
> "Garreau, Alexandre" <galex-713@galex-713.eu> writes:
>
>> But that doesn’t answer the question: why “doesn’t it exist”? shouldn’t
>> these functions be mainlined, if legally permitted?
>
> What kind of numbering are we talking about? A semi-permanent (i.e.,
> togglable) naive numbering (e.g., not taking into account UNNUMBERED
> property) for every headline?
Yes. Didn’t know about UNNUMBERED, thanks, it is of interest for this issue.
> Could you explain what are the use cases for that?
As said in the previously mentioned stackoverflow question: helps
seeing where you are and how much sections are there. To me it is
especially useful to avoid writing manually the number of the section to
know I’m currently in “exercice 8” or something alike.
Btw, some desirable feature as well would be automatic naming (as I
already do sometimes in LaTeX), such as appending whole “Exercice 8” or
“Section 8” for a desired specific level, instead of just a number.
next prev parent reply other threads:[~2018-10-24 8:55 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 [this message]
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=874ldbhggz.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).