emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brian Carlson <hacker@abutilize.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: LaTeX output of numbered TODO plain list items lose numbering. [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/27.0.50/lisp/org/)]
Date: Sat, 9 Nov 2019 18:03:55 -0500	[thread overview]
Message-ID: <718295d8-518f-3e31-dde1-acbf57c001f1@abutilize.com> (raw)
In-Reply-To: <87v9rtuuod.fsf@ucl.ac.uk>

On 11/9/19 6:59 AM, Fraga, Eric wrote:

> On Friday,  8 Nov 2019 at 21:28, Brian Carlson wrote:
>> So it seems that the numbering of numbered items in a plain list are not
>> maintained when the numbered item is also a TODO plain list item.
> This is a "feature", not a bug.  The intention was to export check box
> lists nicely to LaTeX, showing which were done and which were not.  This
> doesn't mix well with any other type of list except for simple bullet
> points unfortunately.

This is, indeed, a very odd "feature." Why change the numbering to not match what the org file shows? 

This is especially problematic if you use internal links...

--8<---------------cut here---------------start------------->8---
* My tasks
  1. one item
  2. Something interesting
     1. [X] <<target>> another item
  3. A note that isn't really a ToDo
     1. Here we refer to item [[target]] saying it's related.
     2. another item

--8<---------------cut here---------------end--------------->8---

That file give the following LaTeX output. (I've omitted the Table of Contents). 
Notice that the reference is to "2." The actual reference is to 2.1 but since 
it's a plain list todo so it references the WRONG item.
--8<---------------cut here---------------start------------->8---

1 My tasks
  1. one item
  2. Something interesting
    [X] another item
  3. A note that isn't really a ToDo
    (a) Here we refer to item 2 saying it's related
    (b) another item
--8<---------------cut here---------------end--------------->8---

This is inconsistent with the org mode content. It is also inconsistent 
with the HTML output, which IMHO matches the intent of the org mode file:
--8<---------------cut here---------------start------------->8---

1 My tasks
  1. one item
  2. Something interesting
     1. [X] another item
  3. A note that isn't really a ToDo
     1. Here we refer to item 2.1 saying it's related.
     2. another item
--8<---------------cut here---------------end--------------->8---



This change in behavior, err 'feature', should at least be documented 
in that it is shocking to a user. The full ramification of the change
may require quite a few documented use cases. Perhaps the "feature creator"
or someone who understands the reasoning wouldn't mind documenting this 
inconsistency in LaTeX exports (but not other Export targets)?

In the mean time, I guess I'll just have to add some "override" lisp to my 
init file to do the sane and expected thing. This is very unfortunate since
org-latex-item is pretty big. I don't think I can easily just advise this
function. <sigh>

> The only way around it is to have them as separate lists (e.g. two empty
> lines between the check box item and the numbered items) and start the
> numbered list with the desired number ([@2], I believe).

But I don't want separate lists. I want a "todo list" that's numbered but 
doesn't change the numbering when I add a comment or wish to refer to another
 task in that list.  Having to constantly update the numbering every time I 
change my list seems sort of contrary to the whole simplicity of Org Mode.  

I find this a very odd exception to just the LaTeX export.

Thanks, 
;-b

  reply	other threads:[~2019-11-09 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09  2:28 Bug: LaTeX output of numbered TODO plain list items lose numbering. [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/27.0.50/lisp/org/)] Brian Carlson
2019-11-09 11:59 ` Fraga, Eric
2019-11-09 23:03   ` Brian Carlson [this message]
2020-02-05  8:20     ` Bastien
2020-02-11 11:30 ` Bastien

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=718295d8-518f-3e31-dde1-acbf57c001f1@abutilize.com \
    --to=hacker@abutilize.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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).