Hi jeff,

Thank you for letting me know. That is not intentional change. Could
you file an issue to github please?
I'll fix it soon.


FYI: We've provided `app.add_lexer()` API since v0.6. It would be
better to use it on install a lexer.

Thank,
Takeshi KOMIYA

2019年6月16日(日) 5:31 Jeff McKenna <[email protected]>:
>
> In our case, we extend the lexers dictionary (this has worked since around 
> 2008) such as:
>
>   def setup(app):
>       from sphinx.highlighting import lexers
>       lexers['myalias'] = MyLexer()
>
> which since the 2.1.0 release causes these warnings and doesn't trigger the 
> highlighting:
>
>   WARNING: Could not lex literal_block as "myalias".  Highlighting skipped.
>
>
> -jeff
>
>
>
>
> On Mon, Jun 3, 2019 at 1:40 PM Komiya Takeshi <[email protected]> wrote:
>>
>> Hi,
>>
>> Thank you for comment.
>>
>> > What's the rationale for taking a class rather than an instance?
>>
>> Since 2.1, we added `:force:` option to some directives for
>> code-blocks. As a result, we need to control the option of lexers for
>> each code-block.
>> It is hard to control for already instantiated lexers. So they don't
>> use the option.
>> This is why I need the not instantiated lexers.
>>
>> Note: I though the support will be dropped since 4.0, not 3.0. (Is my
>> English in changes correct?)
>>
>> >It seems that one might have a lexer class with options and one might want 
>> >to instantiate it with specific options before handing it to Sphinx.
>>
>> Could you let me know what option do you pass to lexers? I will
>> reconsider how to incorporate it to sphinx-core.
>>
>> Thanks,
>> Takeshi KOMIYA
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "sphinx-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at https://groups.google.com/group/sphinx-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sphinx-users/CAFmkQAP0czmSD2UNM6P50--jSHtYbujgh%2BK%2BcPfN%2BDQd4ZmpKg%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sphinx-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/sphinx-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sphinx-users/CAPGmwqD%2BkiSbem6yGBaqb6VDTwwnSU%3DR6sP4Ub3sZAkaZ2LJwQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sphinx-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sphinx-users/CAFmkQAOUYxcv4c_a2Lt%2BYa7dV80KJxEfSZ2rhov%3DpZyb9uigBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to