emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Ed Hirgelt" <ehirgelt@gmail.com>
To: Alex Bochannek <alexb@juniper.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Orgmode] Emphasis font-lock question.
Date: Fri, 8 Sep 2006 10:09:16 -0700	[thread overview]
Message-ID: <44d0d9630609081009p3dd25905m9969d458f51520b2@mail.gmail.com> (raw)
In-Reply-To: <uu03ie1cz.fsf@juniper.net>

[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]

On 9/8/06, Alex Bochannek <alexb@juniper.net> 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.

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.

Ed Hirgelt

Discovery consists of seeing what everybody has seen
and thinking what nobody has thought.

[-- Attachment #1.2: Type: text/html, Size: 1098 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

Emacs-orgmode mailing list

  reply	other threads:[~2006-09-08 17:09 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 [this message]
2006-09-08 17:50       ` Alex Bochannek

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=44d0d9630609081009p3dd25905m9969d458f51520b2@mail.gmail.com \
    --to=ehirgelt@gmail.com \
    --cc=alexb@juniper.net \
    --cc=emacs-orgmode@gnu.org \


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