From: Alex Bochannek <email@example.com>
To: Ed Hirgelt <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: [Orgmode] Emphasis font-lock question.
Date: Fri, 08 Sep 2006 10:50:46 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Ed Hirgelt's message of "Fri, 8 Sep 2006 10:09:16 -0700")
"Ed Hirgelt" <firstname.lastname@example.org> writes:
> On 9/8/06, Alex Bochannek <email@example.com> wrote:
> It's OK to me if */foo/* means italic and bold (this is how Gnus
> rendered your example), but */foo/bar* shouldn't. Markers, stacked or
> otherwise, should come in symmetrical pairs.
> Nice example because there is a symmetric pair there. I have always thought
> that this was a very ambiguous notation. I can see */foo/bar* meaning that foo
> is in bold italic and bar is just bold with the two words run together.
I am perfectly happy to restrict this notation to require identical
marker clusters surrounding the emphasized text. If you want to have
text with different emphasis styles run togeter, the below notation
> For this reason (pesky slashes in path names, + as bullet characters,
> underscores in names) I've abandoned this notation. The @<> is more verbose,
> but unambiguous.
The less typing the better for me. I used to use enriched-mode and the
sequences did get a bit tedious.
prev parent reply other threads:[~2006-09-08 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 6:59 [Orgmode] Emphasis font-lock question Alex Bochannek
2006-09-08 12:27 ` Carsten Dominik
2006-09-08 17:04 ` Alex Bochannek
2006-09-08 17:09 ` Ed Hirgelt
2006-09-08 17:50 ` Alex Bochannek [this message]
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 \
* 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).