From: "Robert Klein" <roklein@roklein.de>
To: Eric Schulte <schulte.eric@gmail.com>,
Carsten Dominik <carsten.dominik@gmail.com>,
Robert Klein <roklein@roklein.de>
Cc: Bastien <bastien.guerry@wikimedia.fr>,
emacs-orgmode@gnu.org, Vinh Nguyen <vinhdizzo@gmail.com>
Subject: Re: text color + highlight
Date: Mon, 09 Aug 2010 09:40:48 +0200 [thread overview]
Message-ID: <op.vg5uaadun9zmcv@pckr105.mpip-mainz.mpg.de> (raw)
In-Reply-To: <op.vg5t4cidn9zmcv@pckr105.mpip-mainz.mpg.de>
Am 09.08.2010, 09:37 Uhr, schrieb Robert Klein <roklein@roklein.de>:
Sorry dropped something on the keyboard and sent the message early :(
Am 09.08.2010, 08:28 Uhr, schrieb Carsten Dominik
<carsten.dominik@gmail.com>:
> Nope, I am against this syntax. If we introduce a more general syntax,
> then it should be done in the way Samuel proposed. WHich means
> we firs get a keyword indtroducing the piece, and then properties.
>
> Like
>
> $[style :color red the red text]
>
> or
>
> $[face :color :italic t red the red text]
>
> Something like the $ before "[" also would seem critical to disambiguate
> from other uses of "[".
I'd prefer this kind of syntax, too. Btw, shouldn't the syntax be:
$[face :color red :italic t the red italic text]
?? (i.e. the red following the :color keyword, not the ':italic t')
I didn't find a canonical way to make a paragraph or a longer text
passage italic, so I'd love an easy way to get it.
BTW, if simply '$[' is free, why not use this for style, e.g.:
$[:italic t :bold nil :color teal My italic and teal text]
(sorry for the double mail)
Best regards
Robert
>
> However, I am not too excited about extra syntax to get this kind of
> thing.
> Would not oppose it, but probably never use it.
>
> - Carsten
>
next prev parent reply other threads:[~2010-08-09 7:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 20:42 text color + highlight Vinh Nguyen
2010-08-06 9:18 ` Bastien
2010-08-06 16:47 ` Vinh Nguyen
2010-08-06 20:28 ` Seweryn
2010-08-06 21:51 ` Eric Schulte
2010-08-06 23:42 ` Vinh Nguyen
2010-08-07 3:15 ` Eric Schulte
2010-08-07 3:57 ` Dan Davison
2010-08-08 14:59 ` Vinh Nguyen
2010-08-08 21:00 ` Eric Schulte
2010-08-09 6:28 ` Carsten Dominik
2010-08-09 7:37 ` Robert Klein
2010-08-09 7:40 ` Robert Klein [this message]
2010-08-10 6:14 ` Christian Moe
2010-08-10 7:06 ` Carsten Dominik
2010-08-10 9:30 ` Christian Moe
2010-08-10 15:06 ` Eric Schulte
2010-08-10 18:38 ` Christian Moe
2010-08-10 21:39 ` David Maus
2010-08-10 23:02 ` Christian Moe
2010-08-10 23:47 ` Eric Schulte
2010-08-11 6:48 ` Dan Davison
2010-08-11 14:32 ` Samuel Wales
2010-08-10 23:14 ` Samuel Wales
2010-08-11 6:03 ` Jan Böcker
2010-08-09 6:58 ` Eric Schulte
2010-08-09 7:05 ` Samuel Wales
2010-08-09 5:17 ` Jambunathan K
2010-08-09 5:52 ` Noorul Islam K M
2010-08-07 4:52 ` Nick Dokos
2010-08-07 12:17 ` Sebastian Rose
2010-08-08 17:46 ` Samuel Wales
2010-09-09 16:15 ` Vinh Nguyen
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=op.vg5uaadun9zmcv@pckr105.mpip-mainz.mpg.de \
--to=roklein@roklein.de \
--cc=bastien.guerry@wikimedia.fr \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
--cc=vinhdizzo@gmail.com \
/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).