emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eddward DeVilla" <eddward@gmail.com>
To: "Daniel J. Sinder" <djsinder@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Emphasis and bold in quotation
Date: Wed, 7 Nov 2007 21:45:31 -0600	[thread overview]
Message-ID: <b71b18520711071945o766f3ddi465747e7cb201220@mail.gmail.com> (raw)
In-Reply-To: <47324691.3090903@gmail.com>

On Nov 7, 2007 5:13 PM, Daniel J. Sinder <djsinder@gmail.com> wrote:
> On 11/07/2007 10:16 AM, Eddward DeVilla wrote:
> > Say:
> >  [*|This is [/|really] important!].  No. [*/_|Really!]
>
> @<i>Why not @<b>@<u> re-use @</u>@</b> a markup that's @<u> already
> in use @</u>@</i>.

I don't export much myself.  I like it to be readable (and hopefully
pretty) in the org-mode buffer.  I've never considered vanilla html
code readable.  It's pretty nice how font lock handles the current
way.  It just seems to have too many corner cases.  I was trying to
think of something that could present well in the org buffer using
font-lock and/or whatever magic links and timestamps use while also
exporting well to all the exportable formats, including but not
limited to html.  I am assuming that font-lock can handle matching
braces.

My first thought was to use something like *[text-n-stuff] but though
that was ugly.  It struck me that links do magic with [hidden|visible]
and though that the markup could be in the hidden area and affect the
face of the visible area.  I figure someone will eventually ask for
nesting so I suggested it upfront figure it would be shot down
immediately for technical limitations or be consider for future
enhancement.

> I say bring the simple, single-character markup back to the original
> incarnation:  *one* word /only/.

Well, that would fix the corner cases.  I'm not sure that's what most
people would want.  I'd guess most  people using the feature would
prefer to keep the text formating with its current warts rather than
go back to simple word mark up.  I could be wrong.  In any case, this
markup stuff seem to be an unruly stepchild in the org-mode tool kit
and it might be worth fixing with some finality, even if it is to go
back to just go back to single word markup.

Edd

  reply	other threads:[~2007-11-08  3:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 17:12 Emphasis and bold in quotation Daniel Clemente
2007-11-07 18:16 ` Eddward DeVilla
2007-11-07 23:13   ` Daniel J. Sinder
2007-11-08  3:45     ` Eddward DeVilla [this message]
2007-11-13  7:12     ` Carsten Dominik
2007-11-07 18:17 ` Bastien
2007-11-13  7:15 ` Carsten Dominik

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=b71b18520711071945o766f3ddi465747e7cb201220@mail.gmail.com \
    --to=eddward@gmail.com \
    --cc=djsinder@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).