emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Idea, configurable markup
Date: Mon, 19 Sep 2011 21:12:01 +0200	[thread overview]
Message-ID: <80k494wdmm.fsf@somewhere.org> (raw)
In-Reply-To: <CA++fsGEE+aRLGCvT=bDvXjVEESm3R2+XWxVqnrqBbPY9=TbEaw@mail.gmail.com>

Hi Dov,

Dov Grobgeld wrote:
> I got the following idea regarding the use of markup characters in org-mode.
> Currently it is possible to use *bold*, /italic/ and ~verbose~ and a few
> other markups. I would have liked to have this extended as follows:
>    - Allow the toggling of the display of the "formatting" characters, *, ~,
>    /, etc.

It's already in there:

1. Choose to get them hidden by default with:

   #+begin_src emacs-lisp
     (setq org-hide-emphasis-markers t)

2. Make them (dis-)appear by toggling visible-mode.

>    - Allow a system that allows the user to invent his own formatting. E.g.
>    «variable», 〈function〉, $math$, ⌞string⌟, or whatever the user fancies. All
>    these modes should be defined in an org-mode variable and the display
>    attributes should be configurable, just like any other custom org-mode font.
>    If the user wants to expand beyond ASCII it should be up to him.
>    - Alternately, use a system like "<var>variable</var>" where the tag var
>    is user definable, just like the magic characters above. The display of the
>    tags should be toggable. Just like for [file:foo.bar] where the [] character
>    are hidden, should the tags be hidden until someone erases one of the two
>    delimiters.
> Note that this is nothing more than ideas at the moment, and I'll probably
> never get around to implement any of it. Still I thought I'd share it if
> someone would like to have a go.

Regarding inventing new formatting and having them correctly exported, this is
already there as well:


- `org-emphasis-alist' for face in Emacs and code to HTML
- `org-export-latex-emphasis-alist' for code to LaTeX

So, already done (by others!).

Just a comment on this: I would be in favor of having one or two extra formats
_by default_ -- so that it's not relying on my .emacs config file; in fact, as
much as in TeXinfo...

Currently, as "special" formats[1], we only have:

- org-code, and
- org-verbatim.

And the use case is not that clear to me (how do you code a URL, a filename,
an argument or a key binding?), as both finally gets resolved to the same
appearance (in HTML, and almost the same in LaTeX).

In TeXinfo, it seems to me we have at least:

- url,
- code,
- key binding,

not speaking of internal references.

I'd be glad if we could get the same "expressivety", by default, as the one we
have in TeXinfo[2].

Best regards,


[1] I mean: other than bold, italic, underline and striken-through.
[2] Never wrote any line in TeXinfo, but simply had to read a couple.

Sebastien Vauban

  parent reply	other threads:[~2011-09-19 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 18:38 Dov Grobgeld
2011-09-19 18:47 ` Eric Schulte
2011-09-19 19:12 ` Sebastien Vauban [this message]
2011-09-20 15:04   ` Darlan Cavalcante Moreira

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=80k494wdmm.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).