still not what i am saying. nefver mind. thanks.
On 2/16/21, Tim Cross wrote:
>
> Samuel Wales writes:
>
>> hi tim,
>>
>> tanks for your replies.
>>
>> 1. the same problem occurs without any * in the buffer.
>
> It will occur with any of the markup special characters e.g. *, =, _, +, /
>
>>
>
Samuel Wales writes:
> hi tim,
>
> tanks for your replies.
>
> 1. the same problem occurs without any * in the buffer.
It will occur with any of the markup special characters e.g. *, =, _, +, /
>
> 2. the emphasis regexps are supposed to be limited to a few lines.
Are they? What is 'a few'
to understant, perahsp try to look at the op and remove the line that says *hi*?
On 2/16/21, Samuel Wales wrote:
> hi tim,
>
> tanks for your replies.
>
> 1. the same problem occurs without any * in the buffer.
>
> 2. the emphasis regexps are supposed to be limited to a few lines.
>
> 3. they
hi tim,
tanks for your replies.
1. the same problem occurs without any * in the buffer.
2. the emphasis regexps are supposed to be limited to a few lines.
3. they are also supposed to not try to match dissimilar delimiiters.
the problem is that
hi =something
stops all emphasis of all type
Samuel Wales writes:
> to answer your question: i expected it to just skip the non-emphasis.
> not emphasizing the rest of the buffer seemed quite unusual.
>
I guess the problem is the same - how does org know when it is just a *
and when it is the beginning of some emphasis text? We could mak
Samuel Wales writes:
> hi tim,
>
> it isn't malformed, so definitely not looking to be told it's
> malformed. it is just text that is not emphasis.
>
> if you think the function works as expected by skipping the rest of
> the buffer, then never mind.
>
> i was, in that case, just emphasizing t
to answer your question: i expected it to just skip the non-emphasis.
not emphasizing the rest of the buffer seemed quite unusual.
On 2/16/21, Samuel Wales wrote:
> hi tim,
>
> it isn't malformed, so definitely not looking to be told it's
> malformed. it is just text that is not emphasis.
>
> i
hi tim,
it isn't malformed, so definitely not looking to be told it's
malformed. it is just text that is not emphasis.
if you think the function works as expected by skipping the rest of
the buffer, then never mind.
i was, in that case, just emphasizing that the code floating around
that is use
Samuel Wales writes:
> in fundamental mode [to eliminate any extra stuff]:
>
> ===
> hi
> /hi/
> hi =test
> hi
> hi
> hi
> /hi/
> hi
> *hi*
> hi
> hi
> hi
> ===
>
> m-: (org-do-emphasis-faces nil) RET
>
> everything after =test does not get emphasized.
>
> there is code floating around that cal
in fundamental mode [to eliminate any extra stuff]:
===
hi
/hi/
hi =test
hi
hi
hi
/hi/
hi
*hi*
hi
hi
hi
===
m-: (org-do-emphasis-faces nil) RET
everything after =test does not get emphasized.
there is code floating around that calls hte function directly instead
of via font lock. so even if fo
10 matches
Mail list logo
