From: Vinh Nguyen <vinhdizzo@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: text color + highlight
Date: Fri, 6 Aug 2010 16:42:44 -0700 [thread overview]
Message-ID: <AANLkTimooXhPwAb4TMaBHejNonmnMB+T9EHPSs4Z0=Bh@mail.gmail.com> (raw)
In-Reply-To: <87mxszcsuv.fsf@gmail.com>
Thanks Eric, this works. I do agree that the implemented syntax is
not org-like but more latex-like. To be more org-like, could we use
parentheses or curly braces like how links are implemented? They
aren't taken, are they? For example,
((red)(this text is red))
{{yellow}{this text is highlighted yellow}} ## see
http://answers.yahoo.com/question/index?qid=20080316135432AANXSJc
What do you think? How hard would it be to change your code to this?
Can this be merged into the development branch?
Thanks,
Vinh
On Fri, Aug 6, 2010 at 2:51 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> Hi,
>
> I've recently seen similar requests on this list.
>
> The attached patch provides a first pass at this support implementing
> both in-buffer coloring given the following syntax, and html export (I
> don't know the correct LaTeX syntax, but it shouldn't be hard to extend
> this to LaTeX as well). This uses something like the LaTeX Beamer
> \color{}{} directive, for example...
>
> My name is \color{red}{eric} schulte.
>
> Would result in the word "eric" appearing in red. Even though I
> implemented the syntax above, I'm *not* recommending this syntax, it
> feels decidedly more like "latex" than "org", it was simply the only
> obvious option for this initial implementation.
>
> -- Eric
>
next prev parent reply other threads:[~2010-08-06 23:43 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 [this message]
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
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='AANLkTimooXhPwAb4TMaBHejNonmnMB+T9EHPSs4Z0=Bh@mail.gmail.com' \
--to=vinhdizzo@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).