From: Samuel Wales <samologist@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Bastien <bastien.guerry@wikimedia.fr>,
emacs-orgmode@gnu.org, Vinh Nguyen <vinhdizzo@gmail.com>
Subject: Re: text color + highlight
Date: Mon, 9 Aug 2010 00:05:20 -0700 [thread overview]
Message-ID: <AANLkTikzhn9BvNv8ebqOXk3co4Pefcd_EP3kFFT79yS2@mail.gmail.com> (raw)
In-Reply-To: <87vd7k8e86.fsf@gmail.com>
Hi Eric,
Did you read my proposals in detail?
Samuel
On 2010-08-08, Eric Schulte <schulte.eric@gmail.com> wrote:
> Hi,
>
> The attached patch implements in-buffer coloring and html export using
> the syntax proposed below.
>
> While I think this is an improvement over my previous patch, this idea
> still has some shortcoming including the fact that
> - nested color specifications aren't working for export (and could be
> tricky to implement)
> - when using a dark-background Emacs theme colors that look good in the
> buffer generally don't look good in the html export and vise versa
>
> The following Org-mode buffer demonstrates this patch
> --8<---------------cut here---------------start------------->8---
> #+Title: A Buffer with Color
>
> * top
> Some colors [color[green]are] green, and [color[red]also] red, and even html
> colors
> like [color[#610B5E]these others] sometimes subtler colors.
>
> These can also be [background[yellow]highlighted].
> --8<---------------cut here---------------end--------------->8---
>
> Cheers -- Eric
>
>
--
Q: How many CDC "scientists" does it take to change a lightbulb?
A: "You only think it's dark." [CDC has denied a deadly disease for 25 years]
==========
Retrovirus: http://www.wpinstitute.org/xmrv/index.html -- PLEASE DONATE
===
PNAS must publish the original Lo and Alter NIH/FDA XMRV paper
verbatim along with the new paper.
next prev parent reply other threads:[~2010-08-09 7:05 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
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 [this message]
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=AANLkTikzhn9BvNv8ebqOXk3co4Pefcd_EP3kFFT79yS2@mail.gmail.com \
--to=samologist@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--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).