emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Robert Goldman <rpgoldman@sift.info>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Bug in latex export of <<links>>
Date: Sun, 01 May 2011 11:22:44 -0500	[thread overview]
Message-ID: <4DBD88D4.1080803@sift.info> (raw)
In-Reply-To: <4DBB2891.80004@sift.info>

On 4/29/11 Apr 29 -4:07 PM, Robert Goldman wrote:
> I have this header in my org-mode file:
> 
> **** Documentation <<documentationPseudoProp>>
> 
> it gets translated into the following, which formats poorly:
> 
> \item Documentation \label{documentationPseudoProp}documentationPseudoProp\\
> 
> Any idea why this would happen?  Seems like a bona fide bug, but perhaps
> I'm just doing something wrong.

This block of org-latex seems to have the problem in it:

  (while (re-search-forward
	  (concat "<<<?" org-export-latex-all-targets-re
		  ">>>?\\((INVISIBLE)\\)?") nil t)
    (org-if-unprotected-at (+ (match-beginning 0) 2)
      (replace-match
       (concat
	(org-export-latex-protect-string
	 (format "\\label{%s}" (save-match-data (org-solidify-link-text
						 (match-string 1)))))
*	(if (match-string 2) "" (match-string 1)))
       t t)))

I suspect that the "INVISIBLE" up there indicates some way I am supposed
to flag this as a non-printing link, but there's no documentation
(AFAICT) about this.  Anyone know what that's supposed to do?

The manual suggests putting these targets in comments, but that only
works for HTML export --- if you do that in LaTeX export, the \label{}
command gets commented out!  Finding a solution that works equally well
in HTML and LaTeX export would be a good thing, I think.

Commenting out the starred s-expression in the block above would
probably fix my problem, but I have no way of telling what collateral
damage there might be.  Can anyone clarify?

If someone can fill me in, I will supply a patch to either the manual or
the code, whichever is appropriate

thanks!
r

     prev parent reply	other threads:[~2011-05-01 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 21:07 Bug in latex export of <<links>> Robert Goldman
2011-05-01 16:22 ` Robert Goldman [this message]

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=4DBD88D4.1080803@sift.info \
    --to=rpgoldman@sift.info \
    --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

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).