emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: "Alain.Cochard@unistra.fr" <Alain.Cochard@unistra.fr>
Cc: Rob Sargent <rsargent@xmission.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: tex export overshoots right margin with mixed fonts
Date: Fri, 24 Feb 2023 11:03:18 +0000	[thread overview]
Message-ID: <87sfevz5op.fsf@ucl.ac.uk> (raw)
In-Reply-To: <25592.38020.591168.169869@gargle.gargle.HOWL> (Alain Cochard's message of "Fri, 24 Feb 2023 11:42:12 +0100")

On Friday, 24 Feb 2023 at 11:42, Alain.Cochard@unistra.fr wrote:
> Now, is there a way to tell Org to export _=MappingInstruction=_ as
> \ul{\texttt{MappingInstruction}}?

Well, I found I never used strike-through but definitely wanted to be
able to highlight text.  So, I redefined the +...+ markup to generate
\hl{} with the following in my custom variables:

   '((bold . "\\textbf{%s}")
     (code . protectedtexttt)
     (italic . "\\emph{%s}")
     (strike-through . "\\hl{%s}")
     (underline . "\\uline{%s}")
     (verbatim . protectedtexttt)))

(and equivalent for HTML export).  You could do similar for _..._?

I also changed the face used so that +...+ was highlighted by

   '(("*" bold)
     ("/" italic)
     ("_" underline)
     ("=" org-verbatim verbatim)
     ("~" org-code verbatim)
     ("+" highlight)))
I did these changes years ago and have never found the lack of
strike-through an issue but do use highlighting all the time, especially
when sharing work-in-progress documents (PDF) with others.


: Eric S Fraga, with org release_9.6.1-250-ge6353d in Emacs 30.0.50

      reply	other threads:[~2023-02-24 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 23:25 tex export overshoots right margin with mixed fonts Rob Sargent
2023-02-24  8:06 ` Fraga, Eric
2023-02-24 10:42   ` Alain.Cochard
2023-02-24 11:03     ` Fraga, Eric [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:

  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=87sfevz5op.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=Alain.Cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rsargent@xmission.com \


* 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


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