From: "Eric Schulte" <schulte.eric@gmail.com>
To: Vinh Nguyen <vinhdizzo@gmail.com>
Cc: emacs-orgmode@gnu.org, Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: text color + highlight
Date: Sun, 08 Aug 2010 15:00:50 -0600 [thread overview]
Message-ID: <87iq3kkef1.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTinvbFrdzjoA7E4UwZ+feG9L+_VYJPh-KZcRPQEv@mail.gmail.com> (Vinh Nguyen's message of "Sun, 8 Aug 2010 07:59:49 -0700")
Vinh Nguyen <vinhdizzo@gmail.com> writes:
> On Fri, Aug 6, 2010 at 8:15 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
>> In playing with the patched code I sent out, I noticed that it may be
>> doing weird things to my headings (#+Title: etc...) in some Org-mode
>> files, so probably it could use some more tweaking before any merge,
>> also I'd not want to rush what could be a reasonably large change into
>> Org-mode without more discussion, but I agree I'd ultimately like to see
>> some form of this functionality appear in Org-mode.
>>
>> Best -- Eric
>
> Eric, so are you tweaking the code to give it a more org-like syntax?
> If not, I'll have to get dirty with your patch to figure out the lisp
> code.
>
> You're right the regular parentheses will probably be mixed up with
> lisp code. Sebastian also brought up that curly braces are hard to
> type on a German keyboard. Just googled up the layout -- don't even
> seen them.
>
> What syntax to use...
I've thought briefly about the following syntax
[color[red] text to be colored red]
- this would be extensible, e.g.
[background[yellow] highlighted text]
could export to the following html
<span "style=background:yellow;">highlighted text</span>
- this would avoid "{}"s
- this would look more "org-like" than the pure latex solution
the only issue with the above is that it may conflate a new /markup/
syntax with org-mode's existing /link/ syntax.
Thoughts? -- Eric
next prev parent reply other threads:[~2010-08-08 21:00 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 [this message]
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=87iq3kkef1.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--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).