From: Reuben Thomas <rrt@sc3d.org>
To: emacs-orgmode@gnu.org
Subject: Bug: Confusing example in "Advanced configuration" [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]
Date: Thu, 14 Sep 2017 15:19:48 +0100 [thread overview]
Message-ID: <878thhweez.fsf@sc3d.org> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
The page http://orgmode.org/manual/Advanced-configuration.html has the following example:
Here is an example filter that replaces non-breaking spaces ~ in the Org buffer with _ for the LaTeX back-end.
(defun my-latex-filter-nobreaks (text backend info)
"Ensure \"_\" are properly handled in LaTeX export."
(when (org-export-derived-backend-p backend 'latex)
(replace-regexp-in-string "_" "~" text)))
(add-to-list 'org-export-filter-plain-text-functions
'my-latex-filter-nobreaks)
This is confusing in several ways. First, the replacement is made the
other way around (that is, _ is replaced by ~). Secondly, “_” does not
denote a non-breaking space in org-mode, as far as I can see. Does the
text mean “LaTeX non-breaking spaces”? Finally, underscore has a
particular meaning in Org, namely, subscript.
Is this an example that used to make sense but doesn’t any longer?
Emacs : GNU Emacs 25.2.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
of 2017-09-12
Package: Org mode version 9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)
--
https://rrt.sc3d.org/
next reply other threads:[~2017-09-14 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 14:19 Reuben Thomas [this message]
2017-09-14 14:57 ` Bug: Confusing example in "Advanced configuration" [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)] Rasmus
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=878thhweez.fsf@sc3d.org \
--to=rrt@sc3d.org \
--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).