From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jon Degenhardt <jondegenhardt@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Export to Latex - Incorrect output for list items starting with left bracket [8.2.3c (8.2.3c-elpa @ /Users/jdegenhardt/.emacs.d/elpa/org-20131115/)]
Date: Tue, 14 Jan 2014 19:42:40 +0100 [thread overview]
Message-ID: <87zjmyl80v.fsf@gmail.com> (raw)
In-Reply-To: <87lhyiv7pt.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 14 Jan 2014 16:39:10 +0000")
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> I very often make use of the [] feature in itemised lists to change
> individual bullet points, for instance. I would not like this feature
> to disappear: it would break many of my documents, especially my beamer
> presentations.
I sometimes use this feature, too. But, admittedly, it is a hack.
I though about escaping first opening square bracket, but only if the
item doesn't start with an export snippet. E.g,
- [item --> \item\relax [item
but,
- @@latex:[\blacktriangle]@@ item --> \item [\blacktriangle]
Unfortunately, I can't see how to not break your documents if we fix the
problem.
> In fact, I had started preparing an email to ask the check lists make
> use of this feature to make these lists look nicer when exported to
> LaTeX. For instance, if we have
>
> - [ ] not yet done
> - [X] this has been done
>
> the exporter currently generates
>
> \item $\square$ not yet done
> \item $\boxtimes$ this has been done
>
> I would like to have this instead which looks much nicer:
>
> \item [$\square$] not yet done
> \item [$\boxtimes$] this has been done
>
> Try it and see how much nicer the list looks...
This is orthogonal to the issue at hand. The problem is not the checkbox
but what comes after. IOW, this feature can be implemented with or
without fixing the bug above (also, a filter can do the job).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-01-14 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 21:18 Bug: Export to Latex - Incorrect output for list items starting with left bracket [8.2.3c (8.2.3c-elpa @ /Users/jdegenhardt/.emacs.d/elpa/org-20131115/)] Jon Degenhardt
2014-01-13 0:26 ` Vladimir Lomov
2014-01-13 16:51 ` Nicolas Goaziou
2014-01-13 23:56 ` Vladimir Lomov
2014-01-14 16:39 ` Eric S Fraga
2014-01-14 18:42 ` Nicolas Goaziou [this message]
2014-01-14 19:54 ` Eric S Fraga
2014-01-14 20:52 ` Nicolas Goaziou
2014-01-15 8:35 ` Eric S Fraga
2014-01-15 13:18 ` Nicolas Goaziou
2014-01-16 9:55 ` Eric S Fraga
2014-01-16 12:03 ` Sebastien Vauban
2014-01-16 15:10 ` Eric S Fraga
2014-01-16 15:15 ` Nicolas Goaziou
[not found] ` <87ha94vtyj.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-16 15:24 ` Sebastien Vauban
2014-01-16 16:42 ` Eric S Fraga
2014-08-03 7:57 ` Nicolas Goaziou
2014-01-16 14:54 ` Nicolas Goaziou
2014-01-18 20:06 ` Jon Degenhardt
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=87zjmyl80v.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jondegenhardt@yahoo.com \
/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).