emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: exporting typefaces
Date: Wed, 7 Jun 2006 12:21:46 +0200	[thread overview]
Message-ID: <8520217f0c56f24481f460dcc4b64fd2@science.uva.nl> (raw)
In-Reply-To: <44859756.2040307@gmail.com>


On Jun 6, 2006, at 16:55, Austin Frank wrote:
>
> Looking through a few O'Reilly books on my shelf, I see that different
> books use constant-width bold (<b><pre>text</pre></b>) and
> constant-width italics (<i><pre>text</pre></i>) to indicate where a 
> user
> should enter input in example code.

Yes, that is true, O'Reilly books use some excessive styling - I guess 
it makes sense in these cases.

Generalizing the emphasis stuff is tricky, and I am worried that the 
regular expressions will match unintentionally.

However, I have now made this configurable, a test version is at

http://www.astro.uva.nl/~dominik/Tools/org/org-testemphasize.zip

In this version you can configure your own text styling through the 
option `org-emphasis-alist'.  Before I release this, some tweaking of 
the other new option `org-emphasis-regexp-components' might be 
necessary.  In that option you can also define the number of newlines 
you wish to allow in a single emphasized expression (default is one for 
now, don't increase this too much because of a potentially significant 
performance penalty).  Also you can ask for stacked styling in that 
variable.

For now, stacked styling is turned off by default.

- Carsten

      reply	other threads:[~2006-06-07 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 14:26 exporting typefaces Austin Frank
2006-06-06 14:33 ` Carsten Dominik
2006-06-06 14:55   ` Austin Frank
2006-06-07 10:21     ` Carsten Dominik [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=8520217f0c56f24481f460dcc4b64fd2@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=austin.frank@gmail.com \
    --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).