emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, Titus von der Malsburg <malsburg@posteo.de>
Subject: Re: Feature request: lists with letters
Date: Fri, 03 Feb 2017 09:50:29 +0100	[thread overview]
Message-ID: <m2inorvesq.fsf@krugs.de> (raw)
In-Reply-To: <87bmukcqnn.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 02 Feb 2017 20:57:00 +0100")

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

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Titus von der Malsburg <malsburg@posteo.de> writes:
>
>> One issue with org-list-allow-alphabetical is that we get numbers
>> instead of letters when we export to HTML and LaTeX.  I saw the earlier
>> thread [0] that gives the reasoning for this but I find it
>> unsatisfying.  If Org allows us to distinguish between -, +, 1., 1), a.,
>> A., a), A), this should also be honored by the exporter.
>
> This is also why I dislike the feature.
>
>> Otherwise it’s rather pointless to allow that distinction in the first
>> place.
>
> Exactly.
>
>> IMHO, a clean solution would be to either drop everything but - and
>> 1. or to keep all these and make the exporters honor them.  The former
>> would breaks existing documents and is therefore out of the
>> question.  This leaves us with the second solution.
>
> I wouldn't rule that out. Breaking changes happen. We can provide tools
> to fix existing documents.
>
> Actually, I like the idea of keeping only "-" and "1.". We could
> implement other bullet types as overlays.
>
>> Any chance you are willing to reconsider the decision to ignore
>> allow-alphabetical during export?
>
> I still agree with Carsten in the thread you pointed out. Org document
> is about structure. The bullet in about typesetting.

I must admit, I haven't read the thread mentioned, and I am sure
Carsten's point was correct, but orgmode is more and more used for
non-structure tasks. As an example I see the whole field of reproductive
research and scientific paper writing, which, in my opinion, has many
more elements than structure. Another example are html emails (like them
or not - I also dislike them) which people compose in org, or org as a
LaTeX frontend.

Exporting, i.e. typesetting and sharing, becomes much more important
these days and possibly as important as the structure.

In a nutshell: I agree with Titus' point and also would love to have
alphabetical bullets.

But it is for me not that important if they are alphabetical or numeric
in org - a simple command / which I could put in front of the list, and
*which could be interpreted by the exporter* to do the right thing for
this list would be fine, simmilar to bold, verbtin, ...
The implementation would then be in the exporter.

Cheers,

Rainer

>
>> I think it would be very useful to have that. I know there are other
>> ways to get alphabetical bullets in exported documents but they are
>> all specific to certain export targets and the beauty of Org mode is
>> precisely that we can export to many different targets.
>
> The beauty of Org is also to allow to control different export targets
> in the same document.
>
> I think this is a non-issue.
>
> Regards,

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

  parent reply	other threads:[~2017-02-03  8:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 17:28 Feature request: lists with letters Titus von der Malsburg
2017-02-02 17:55 ` Nicolas Goaziou
2017-02-02 19:42   ` Titus von der Malsburg
2017-02-02 19:57     ` Nicolas Goaziou
2017-02-02 20:05       ` Titus von der Malsburg
2017-02-02 20:19         ` Nicolas Goaziou
2017-02-02 20:33           ` Eric Abrahamsen
2017-02-03  8:50       ` Rainer M Krug [this message]
2017-02-03 16:22         ` William Denton
  -- strict thread matches above, loose matches on Subject: below --
2017-02-03 11:37 Titus von der Malsburg
     [not found] <1622a63fda844eb1aa553fdcd19a5758@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-03 12:40 ` Eric S Fraga
2017-02-03 13:47   ` Titus von der Malsburg
2017-02-06 15:34     ` Rasmus
2017-02-06 19:59       ` Titus von der Malsburg
2017-02-09  9:29         ` Rasmus
2017-02-10 10:58           ` Titus von der Malsburg
2017-02-11  1:20             ` Nicolas Goaziou
2017-02-13 10:51               ` Rasmus
2017-02-13 13:47                 ` Nicolas Goaziou
2017-02-13 16:55                   ` Rasmus
2017-02-13 20:39                     ` Nicolas Goaziou
2017-02-14 11:25                       ` Rasmus
2017-02-14 12:57                         ` Nicolas Goaziou
     [not found]             ` <9385a1ca2a23417399fb441d6d85795d@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-02-11 12:39               ` 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=m2inorvesq.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=malsburg@posteo.de \
    /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).