org-agenda-current-time-string partly fontified with emphasis

org-agenda-current-time-string partly fontified with emphasis

[Samuel Wales]

in the new release, org-agenda-current-time-string is partly fontified
if it contains emphasis like "=== test ===".  my guess is best to not
fontify as it is not possible to
fix unless you turn it off for the entire buffer.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: org-agenda-current-time-string partly fontified with emphasis

[Samuel Wales]

On 9/6/17, Samuel Wales <samologist@gmail.com> wrote:
> in the new release, org-agenda-current-time-string is partly fontified
> if it contains emphasis like "=== test ===".  my guess is best to not
> fontify as it is not possible to
> fix unless you turn it off for the entire buffer.

the above is correct, but the cause is possibly related to the fact
that there is an emphasis change from 9.0.

before, "===" in the outline would not be fontified.  now it is.

can this be turned off?  i use "===" specifically in the outline and
would prefer it in a default font, while preserving =this emphasis=.

Re: org-agenda-current-time-string partly fontified with emphasis

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> On 9/6/17, Samuel Wales <samologist@gmail.com> wrote:
>> in the new release, org-agenda-current-time-string is partly fontified
>> if it contains emphasis like "=== test ===".  my guess is best to not
>> fontify as it is not possible to
>> fix unless you turn it off for the entire buffer.
>
> the above is correct, but the cause is possibly related to the fact
> that there is an emphasis change from 9.0.
>
> before, "===" in the outline would not be fontified.  now it is.

Indeed. === really means "=" character in verbatim markup.

> can this be turned off?

You may be able to tweak fontification to ignore this special case. See
`org-font-lock-set-keywords-hook' to install a special rule for.

It will work as long as you don't export the document. For that case,
you could write a filter turning multiple "=" into "\equal".

Regards,

-- 
Nicolas Goaziou

Re: org-agenda-current-time-string partly fontified with emphasis

[Samuel Wales]

On 9/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Indeed. === really means "=" character in verbatim markup.

fyi but not in all of the agenda current time string.  just the first
part in my example.

> You may be able to tweak fontification to ignore this special case. See
> `org-font-lock-set-keywords-hook' to install a special rule for.

are there examples of the usage of this?

> It will work as long as you don't export the document. For that case,
> you could write a filter turning multiple "=" into "\equal".

is there a filter that will change instances /before/ they get
converted by a backend?  depending on the backend sometimes i want ===
and sometimes a suitable short centered separator.  i don't want to
use hyphens, and org's separator is page-wide.

Re: org-agenda-current-time-string partly fontified with emphasis

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

>> You may be able to tweak fontification to ignore this special case. See
>> `org-font-lock-set-keywords-hook' to install a special rule for.
>
> are there examples of the usage of this?

There is one in "contrib/lisp/org-wikinodes.el".

>> It will work as long as you don't export the document. For that case,
>> you could write a filter turning multiple "=" into "\equal".
>
> is there a filter that will change instances /before/ they get
> converted by a backend?

There are two of them: `org-export-before-processing-hook' and
`org-export-before-parsing-hook'.

> i don't want to use hyphens, and org's separator is page-wide.

It depends on the export back-end. You can control the width of the
separator in "latex" and "ascii" back-ends.

Regards,

-- 
Nicolas Goaziou