emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Manfred Lotz <manfred.lotz@arcor.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: export to man page problem
Date: Sun, 07 Sep 2014 10:14:59 +0200	[thread overview]
Message-ID: <87ha0jc0e4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20140907094531.0ebbc90b@arcor.com> (Manfred Lotz's message of "Sun, 7 Sep 2014 09:45:31 +0200")

Manfred Lotz <manfred.lotz@arcor.de> writes:

> Take this
>
> <--------------snip---------------->
> #+TITLE: mycmd
> * NAME
> mycmd - does very important things
> * SYNOPSIS
> mycmd.pl -u bla [-R] [-A] [-n] [-a] 
> * DESCRIPTION
> mycmd could be configured by setting environment variable MYCMD_OPT
> <--------------snap---------------->
>
> The man page looks like this:
>
> mycmd(1)                                         General Commands
> Manual                                         mycmd(1)
>
>
>
> NAME
>        mycmd - does very important things
>
> SYNOPSIS
>        mycmd.pl -u bla [-R] [-A] [-n] [-a]
>
> DESCRIPTION
>        mycmd could be configured by setting environment variable
> MYCMDOPT
>
>
>
> As you can see the _ (underscore) in MYCMD_OPT vanished.

In this case, "_OPT" is a subscript, which is translated into
"MYCMD\d\s-2OPT\s+2\u". For some reason, groff doesn't recognize this
markup.

Anyway, you probably don't want a subscript here. Locally, you can use
a macro instead:

  MYCMD\under{}OPT

or simply disable subscript (and superscript) for the whole document:

  #+OPTIONS: ^:nil


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-09-07  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07  6:56 export to man page problem Manfred Lotz
2014-09-07  7:12 ` Nicolas Goaziou
2014-09-07  7:45   ` Manfred Lotz
2014-09-07  8:14     ` Nicolas Goaziou [this message]
2014-09-07 14:53       ` Manfred Lotz

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=87ha0jc0e4.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=manfred.lotz@arcor.de \
    /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).