Fix #1837 -- nikola new_post --available-compilers

[Kwpolska]

This is #1837.

Also accessible as -F, and in nikola new_page.

Sample output (from my own blog):

$ nikola new_post --available-compilers
Available input formats:

 NAME      EXTENSIONS

 html      .html, .htm
 rest      .txt, .rst
!ipynb     .ipynb
!markdown  .md, .mdown, .markdown
~pandoc    (disabled: not in COMPILERS)
~php       (disabled: not in COMPILERS)

More compilers are available in the Plugins Index.

Compilers marked with ! and ~ require additional configuration:
    ! not in the PAGES/POSTS tuples (unused)
    ~ not in the COMPILERS dict (disabled)
Read more: https://getnikola.com/handbook.html#configuring-other-input-formats

(there is no “friendly name” field, cannot do that)

Signed-off-by: Chris Warrick kwpolska@gmail.com

[ralsina]

We can add a friendly name field for plugins, then :-)

[ralsina]

Also, we should classify plugins per type, I think. It can be done inspecting the code.

[Kwpolska]

What sort of “type” do you mean?

[Kwpolska]

@ralsina: are we okay with an API change here (drop =None)?

[Kwpolska]

Friendly names added. Note that the API for filter_post_pages changed substantially.

[ralsina]

Compiler/task/rest extension/etc.

[Kwpolska]

I'm not sure I understand… This plugin adds a new feature that handles
installed compilers only. What do you want to be done?

Chris Warrick https://chriswarrick.com
Sent from my Galaxy S3.
On 21 Jun 2015 22:49, "Roberto Alsina" notifications@github.com wrote:

Compiler/task/rest extension/etc.

—
Reply to this email directly or view it on GitHub
#1840 (comment).

[ralsina]

@Kwpolska this sends the user to the plugins site looking for compiler plugins. We have enough plugins that actually finding the compilers takes a little while.

[Kwpolska]

We could just add a new field to .plugin files and let users filter by that. Should not be hard to implement (but I’m not taking it, at least for now)