emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tom Alexander" <tom@fizz.buzz>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: COUNTER-SET for alphabetical ordered lists ignored for utf-8 exporter
Date: Wed, 11 Oct 2023 10:28:09 -0400	[thread overview]
Message-ID: <2c9a6cbd-21c0-45bf-8fbb-4f7eccac4ae7@app.fastmail.com> (raw)
In-Reply-To: <87o7hazpxg.fsf@localhost>

Thanks!

> We aim to reduce config-dependent Org syntax in the long term.

Thats wonderful news! Sometimes this stuff can really surprise you. For example, the structure of the document created by running `echo "1. foo\n 1.bar\n        1.baz\n\t1.lorem"` changes based on the user's **tab-width**!!

If tab-width is less than 8 then this is:
```text
1. foo
  1. bar
    1. baz
  2. lorem
```

If tab-width is 8 then this is:
```text
1. foo
  1. bar
    1. baz
    2. lorem
```

and if tab-width is greater than 8 this is:
```text
1. foo
  1. bar
    1. baz
      1. lorem
```

Absolute madness! I always considered tab-width to be a personal aesthetic choice and not something that would functionally change how documents other people wrote will be parsed.

Idk if its been discussed, but personally if I were given dictatorship over org-mode I would take all of these emacs variables that are defined outside of the document, and instead of having them influence org-mode directly, I would *only* use them to pre-populate values for in-buffer settings templates.

For example, if a user had set `org-odd-levels-only` then I wouldn't have that impact ANY existing document they open, but if they open a new document then I would have it auto-insert `#+STARTUP: odd` at the top of the fresh document.

Otherwise it seems like org-mode is unsuitable for multi-person collaboration without dictating the contents of everyone's `.emacs` file.

--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc


  reply	other threads:[~2023-10-11 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 18:16 COUNTER-SET for alphabetical ordered lists ignored for utf-8 exporter Tom Alexander
2023-10-07 10:29 ` Ihor Radchenko
2023-10-11 14:28   ` Tom Alexander [this message]
2023-10-20 10:15     ` [PATCH] [DISCUSSION] Force `tab-width' to be 8 in Org mode (was: COUNTER-SET for alphabetical ordered lists ignored for utf-8 exporter) Ihor Radchenko
2023-12-05 13:13       ` Ihor Radchenko
2023-10-20 10:18     ` COUNTER-SET for alphabetical ordered lists ignored for utf-8 exporter Ihor Radchenko
2024-04-05 17:06   ` Stacey Marshall
2024-04-06 12:02     ` Ihor Radchenko
2024-04-06 12:25       ` Stacey Marshall

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=2c9a6cbd-21c0-45bf-8fbb-4f7eccac4ae7@app.fastmail.com \
    --to=tom@fizz.buzz \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.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).