From: Sharon Kimble <boudiccas@skimble09.plus.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Broken numerical ordered list when exported to latex
Date: Mon, 02 Jan 2023 12:56:55 +0000 [thread overview]
Message-ID: <87k025m6w8.fsf@skimble09.plus.com> (raw)
In-Reply-To: <87y1qm5ody.fsf@localhost> (Ihor Radchenko's message of "Sun, 01 Jan 2023 14:18:49 +0000")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Ihor Radchenko <yantar92@posteo.net> writes:
> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> My org file is attached, and the original source was a web-page, a straight copy and paste, so its inheriting the same list structure as the original.
>
> This is expected. Lists are numbered from 1. all the time unless you
> explicitly state otherwise. See
> https://orgmode.org/manual/Plain-Lists.html
>
> You need something like
>
> 10. [@10] Life and/or death. There's little else of such significance. Have you had a near-death experience? What is your experience of witnessing birth or death?
>
> in your Org source.
Brilliant, thank you Ihor, it works a treat!
Could the manual be amended to show how to use it with an example like the one you showed above please?
Thanks
Sharon.
- --
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 11.5, fluxbox 1.3.7, emacs 29.0.60, org 9.5.5
-----BEGIN PGP SIGNATURE-----
iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmOy1JcdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1t5xQ//YQbbox9yMN35KxBB
lq7OuA7BVozedxhI8QtjFOdkViF5qiCl+IL7Ge/DW8UccOpQn7FeV/PEHaKS9Zc9
TXbI787WoseimfCB3M6mHyDUFt+ty+xKEcEu2GZFYjlFjBoF5ixgwAlbVHA95EeT
GxU3lWOLGQa56c5KqLIE+H/UiUkJw1tSr89FD6IBeX/VDomsGKQcMDEtduSMcKp1
9Rmuo47xgW3WiY+w5xUvPutRA9G9UHEeVLmx0mC/beuBjA9c6zs4iQyCucVXsXbb
jiiVMGHMDp86yd9xeGdC+jUIo+bSEGCbPiUx5VnfaJcmmTkCMO59N/DD73mKBBs7
RB5+Dw8k2EPJU43etgzkXq5C6dgjVX0vEiVJgb9+tGtazQn83JCXgkEWHzkqDmow
JrDw4ZiamIGD/xsdSkMz19TzmLVDF2AGuHdYybl6+0/1olPQxi5CZ6g5DzkKfWxF
63yPavbjgwtNZH148+OdCLjjys6PhCb33TRRsHhKUyGv+4e6RRm2PYPuCMAE0rMW
7HJ01u6NUWAdobd/tQL0wCDaqjt0kSJEr0qqjFkRN3r6H0yKavinRelRd+HJagpj
WznRYr906mrFoadR9UAfQyssSUxklILVCNvzPEPPRYhSREWW/Yby/FQ7m2z5NP32
pNclfAeiqvUePpGbHgPNuvF1qQw=
=Ajfl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2023-01-02 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 17:59 Broken numerical ordered list when exported to latex Sharon Kimble
2022-12-31 13:43 ` Ihor Radchenko
2023-01-01 14:05 ` Sharon Kimble
2023-01-01 14:18 ` Ihor Radchenko
2023-01-02 12:56 ` Sharon Kimble [this message]
2023-01-03 7:52 ` Ihor Radchenko
2024-04-05 11:34 ` Ihor Radchenko
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=87k025m6w8.fsf@skimble09.plus.com \
--to=boudiccas@skimble09.plus.com \
--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).