"Roland Winkler" writes:
> On Sun Feb 10 2013 Bastien wrote:
>> Please provide a patch.
>
> I'd much appreciate if the org developers could do that. I have
> enough such things on my own emacs agenda,
Done in Org's git repository, thanks.
--
Bastien
On Sun Feb 10 2013 Bastien wrote:
> Please provide a patch.
I'd much appreciate if the org developers could do that. I have
enough such things on my own emacs agenda,
"Roland Winkler" writes:
> I do not find the info nodes on "Structural markup elements"
> particularly overloaded. The node "Emphasis and monospace" is just
> one short paragraph, and org-fontify-emphasized-text could esily be
> mentioned there -- unless this variable also affects other things,
>
On Sun Feb 10 2013 Bastien wrote:
> > Why put this in a separate FAQ? Aren't the info pages the first
> > source of information for such things?
>
> Depends. We try to keep the info manual readable, and it's already
> quite long. If you can find a good place in the manual, please send
> a patch.
Hi Roland,
"Roland Winkler" writes:
> There are spaces both between the 2nd and 3rd line, and between the
> 5th and 6th line. -- Possibly, the regexp matcher could distinguish
> in a smarter way between word constituents and no word constituents.
Sorry I wasn't clear: by default, space is not
On Sun Feb 10 2013 Bastien wrote:
> > But it appears to me that this feature could use a
> > more sophisticated regexp matcher. Note that the 5th and 6th line
> > are not striked through.
>
> Because the space isn't allowed within +...+ fontified constructs.
There are spaces both between the 2nd
Hi Roland,
"Roland Winkler" writes:
> visit the following org file with emacs -Q
>
> cat > foo.org < * foo
> bar (+.2 to .5)
> baz (+.2 to .5)
>
> bar (+.2 to .5)
> baz +.2 to .5)
> EOF
>
> Why are part of the second and third line striked through?
Because "+" tries to add fontificatio
