emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@uva.nl>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: setting local variables
Date: Wed, 20 Sep 2017 18:17:34 +0200	[thread overview]
Message-ID: <CADn3Z2+KvtVbasNaYRQbRYJStoZVLigu0yC04fQzsyVQMmW3Dw@mail.gmail.com> (raw)
In-Reply-To: <87bmmm4kny.fsf@ericabrahamsen.net>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen <eric@ericabrahamsen.net>
wrote:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>
> [...]
>
> > So, any objection to have all major back-ends ignoring unnumbered trees
> > from TOC, and make that an Org specificity?
>


Hi Nicolas,

OK, now I have read this thread.

I do object to removing unnumbered headers from the toc.  It breaks
documented and used behaviour and aI see no pressing reason to change it. I
find, for compact documents, it works extremely well to have a toc that has
no numbers - in fact, in many cases I find numbered tocs even annoying.  In
particular, it works really well in websites, where I use it constantly.

I am sorry that I did not see this earlier - but I really think this change
should be reverted.  If there is a desire to have sections that are not put
into the toc, it should be separated from the num: and toc: switches and
depend, for example on properties instead.

The fact that in LaTeX "unnumbered" is linked to the question if something
is in the toc is some kind of mistake, this behaviour is very specific to
LaTeX-like systems (including TeXInfo), but it is not a very logical system
IMO.

Carsten


>
> Sounds good!
>
>
>

[-- Attachment #2: Type: text/html, Size: 1961 bytes --]

  parent reply	other threads:[~2017-09-20 16:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 21:53 setting local variables Eric Abrahamsen
2017-08-02 22:10 ` Kaushal Modi
2017-08-02 22:15   ` Eric Abrahamsen
2017-08-03 10:52 ` Nicolas Goaziou
2017-08-03 16:11   ` Eric Abrahamsen
2017-08-03 22:02     ` Nicolas Goaziou
2017-08-03 22:49       ` Eric Abrahamsen
2017-08-04  0:42         ` Eric Abrahamsen
2017-08-04 15:37           ` Nicolas Goaziou
2017-08-05  1:06             ` Eric Abrahamsen
2017-08-05  8:50               ` Nicolas Goaziou
2017-08-05 19:14                 ` Eric Abrahamsen
2017-09-05 11:48     ` Rasmus
2017-09-05 16:57       ` Eric Abrahamsen
2017-09-06  8:56         ` Rasmus
2017-09-06 10:38           ` Nicolas Goaziou
2017-09-06 12:42             ` Rasmus
2017-09-06 13:08               ` Nicolas Goaziou
2017-09-06 16:33                 ` Eric Abrahamsen
2017-09-06 16:57                   ` Nicolas Goaziou
2017-09-06 17:44                     ` Eric Abrahamsen
2017-09-07  8:56                     ` Rasmus
2017-09-07 12:48                       ` Nicolas Goaziou
2017-09-07 15:01                         ` Eric Abrahamsen
2017-09-10 13:55                           ` Nicolas Goaziou
2017-09-20 16:17                           ` Carsten Dominik [this message]
2017-09-20 18:42                             ` Scott Randby
2017-09-20 23:16                               ` Kaushal Modi
2017-09-21  8:38                                 ` Carsten Dominik
2017-09-21  9:39                                   ` Rasmus
2017-09-21  9:58                                     ` Carsten Dominik
2017-09-21 19:21                                       ` Nicolas Goaziou
2017-09-21 21:25                                         ` Kaushal Modi
2017-09-22  7:22                                         ` Carsten Dominik
2017-09-22  9:09                                         ` Rasmus
2017-09-21 13:00                                 ` Scott Randby
2017-09-21  7:45                               ` 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=CADn3Z2+KvtVbasNaYRQbRYJStoZVLigu0yC04fQzsyVQMmW3Dw@mail.gmail.com \
    --to=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).