On 08/11/2010 01:14 AM, Samuel Wales wrote:
> i suggest begin-end pairs, not putting text in the syntax itself.
> though you could, if you want, using quotes.
>
> $[class begin :title animals]Some text about animals$[class end
> :title animals]
>
Why not allow both? If I want to highlight one
Christian Moe writes:
[...]
>
> Admittedly, though, all the currently defined link types mean "do
> something when clicked", which a =color:red= link does not.
>
well this may be trivial, but at least it's an action
--8<---cut here---start->8---
(org-add-link-
i suggest begin-end pairs, not putting text in the syntax itself.
though you could, if you want, using quotes.
$[class begin :title animals]Some text about animals$[class end
:title animals]
i wrote the following long ago, but never sent it to
the list. it is not polished at all -- needs more
I wrote (against my own suggestion):
A drawback with using links for markup is that the user sees things that
look like links, but do nothing when clicked, except give error messages.
David Maus wrote:
It's not just a drawback but a more fundamental problem: This solution
abolishes the semanti
Christian Moe wrote:
>Hi, Eric,
>Thanks for trying this out -- I should have taken the trouble to write
>out sample code myself.
>> Just for completeness I'm adding an example of a color handler which can
>> be added to a users config to enable colorization of exported text to
>> html and latex.
Hi, Eric,
Thanks for trying this out -- I should have taken the trouble to write
out sample code myself.
Just for completeness I'm adding an example of a color handler which can
be added to a users config to enable colorization of exported text to
html and latex.
--8<---cut here-
Hi Christian,
Christian Moe writes:
> Hi,
>
> I'm sorry my point was buried in quoted text. I did read Samuel's
> post. But my question was whether we couldn't *avoid inventing new
> syntaxes*, by using the already existing link syntax with custom links
> and export handlers (plus possibly some
Hi,
I'm sorry my point was buried in quoted text. I did read Samuel's post.
But my question was whether we couldn't *avoid inventing new syntaxes*,
by using the already existing link syntax with custom links and export
handlers (plus possibly some some new functionality to user-customize
the
Hi,
Can we please first read Samuels post about extensible syntax? Before
we invent 20 other new syntaxes?
http://thread.gmane.org/gmane.emacs.orgmode/10204/focus=10204
Thanks!
On Aug 10, 2010, at 8:14 AM, Christian Moe wrote:
Hi,
>>
>> - this would be extensible, e.g.
>>
>> [backgroun
Hi,
>>
>> - this would be extensible, e.g.
>>
>> [background[yellow] highlighted text]
>>
>> could export to the following html
>>
>> highlighted text
>>
>> - this would avoid "{}"s
>>
>> - this would look more "org-like" than the pure latex solution
>>
>> the only issue with the above is that
Am 09.08.2010, 09:37 Uhr, schrieb Robert Klein :
Sorry dropped something on the keyboard and sent the message early :(
Am 09.08.2010, 08:28 Uhr, schrieb Carsten Dominik
:
Nope, I am against this syntax. If we introduce a more general syntax,
then it should be done in the way Samuel proposed.
Am 09.08.2010, 08:28 Uhr, schrieb Carsten Dominik
:
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 t
On Aug 8, 2010, at 11:00 PM, Eric Schulte wrote:
Vinh Nguyen writes:
On Fri, Aug 6, 2010 at 8:15 PM, Eric Schulte
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
Hi Eric,
Did you read my proposals in detail?
Samuel
On 2010-08-08, Eric Schulte 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 short
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
t
Vinh Nguyen writes:
> On Fri, Aug 6, 2010 at 8:15 PM, Eric Schulte 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,
>> al
Hi all,
I do, very strongly, propose extensible syntax. Thanks for bringing it up, Dan.
I have much more on this but cannot type now.
Samuel
--
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]
==
"Eric Schulte" writes:
> 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 e
On Fri, Aug 6, 2010 at 8:15 PM, Eric Schulte 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
Eric Schulte 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 e
Hi Vinh,
Vinh Nguyen writes:
> Thanks Eric, this works.
Great,
> 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
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 highligh
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
On Fri, Aug 6, 2010 at 2:18 AM, Bastien wrote:
> Hi Vinh,
>
> Vinh Nguyen writes:
>
>> I was wondering if there is an easy way to markup the color of the
>> text for html output (and highlight as well). When I prepare meeting
>> minutes I'd like to color some things and highlight certain things.
Hi Vinh,
Vinh Nguyen writes:
> I was wondering if there is an easy way to markup the color of the
> text for html output (and highlight as well). When I prepare meeting
> minutes I'd like to color some things and highlight certain things.
> Right now, I am using emphasizing a major portion of t
Dear list,
I was wondering if there is an easy way to markup the color of the
text for html output (and highlight as well). When I prepare meeting
minutes I'd like to color some things and highlight certain things.
Right now, I am using emphasizing a major portion of the text. It
would be great
26 matches
Mail list logo
