Nicolas Goaziou writes:
> Hello,
>
> Brady Trainor writes:
>
>> Speaking of COMMENT, I had noticed some strange behavior if I have a state
>> like COMMENTED_OUT.
>>
>> If I have a header like =#+TODO: TODO COMMENTED_OUT | DONE=, and cycle
>> through state with S-, it gets pretty wonky.
>
> Cou
Hello,
Nicolas Goaziou writes:
> Hello,
>
> Brady Trainor writes:
>
>> Speaking of COMMENT, I had noticed some strange behavior if I have a
>> state like COMMENTED_OUT.
>>
>> If I have a header like =#+TODO: TODO COMMENTED_OUT | DONE=, and cycle
>> through state with S-, it gets pretty wonky.
>
Hello,
Brady Trainor writes:
> Speaking of COMMENT, I had noticed some strange behavior if I have a state
> like COMMENTED_OUT.
>
> If I have a header like =#+TODO: TODO COMMENTED_OUT | DONE=, and cycle
> through state with S-, it gets pretty wonky.
Could you elaborate a bit? I cannot reprodu
Speaking of COMMENT, I had noticed some strange behavior if I have a state like
COMMENTED_OUT.
If I have a header like =#+TODO: TODO COMMENTED_OUT | DONE=, and cycle through
state with S-, it gets pretty wonky. For now, I simply use COMMENT
when I have a section I want to consider as commented
Hi,
I removed `org-html-use-unicode-chars'.
Thanks,
--
Bastien
Andreas Leha writes:
> So, even if there is probably not a high risk for the COMMENT keyword to
> be dropped I just wanted to express my support for it.
COMMENT will stay, for sure.
--
Bastien
Andreas Leha writes:
> [ deleted: discussion on beatification ]
>
>> My initial reaction was to kill it as well. But I might feel like this a
>> bit to often (I feel the same way about headline keywords like COMMENT).
>
> There has been repeated 'bashing' of the COMMENT keyword lately on this
> l
Hi,
[ deleted: discussion on beatification ]
>
> My initial reaction was to kill it as well. But I might feel like this a
> bit to often (I feel the same way about headline keywords like COMMENT).
There has been repeated 'bashing' of the COMMENT keyword lately on this
list. Let me just raise a
Nicolas Goaziou writes:
>> OK. I added it to plain-text as well. What is an example of a plain-text
>> that would need beautification?
>
> To tell the truth, I don't know why we need beautification in the first
> place. Bastien introduced it, so he may be able to answer.
To this extend; me nei
> OK. I added it to plain-text as well. What is an example of a plain-text
> that would need beautification?
To tell the truth, I don't know why we need beautification in the first
place. Bastien introduced it, so he may be able to answer.
> Should we apply it to snippets as well? In the spiri
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Vladimir Alexiev writes:
>>
>>> I've set org-html-use-unicode-chars since I want ox-html to leave IRIs as
>>> IRIs.
>>> But this has another undesired effect: it breaks references in code,
>>> since it doesn't escape the brackets.
>>
>>
Hello,
Rasmus writes:
> Vladimir Alexiev writes:
>
>> I've set org-html-use-unicode-chars since I want ox-html to leave IRIs as
>> IRIs.
>> But this has another undesired effect: it breaks references in code,
>> since it doesn't escape the brackets.
>
> I think this should only apply to entit
Hi,
Vladimir Alexiev writes:
> I've set org-html-use-unicode-chars since I want ox-html to leave IRIs as
> IRIs.
> But this has another undesired effect: it breaks references in code,
> since it doesn't escape the brackets.
I think this should only apply to entities. Any reason to do it on t
13 matches
Mail list logo
