Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help text of apy list-from-file -h is formatted wrong on console #93

Closed
camoz opened this issue May 31, 2024 · 2 comments
Closed

Help text of apy list-from-file -h is formatted wrong on console #93

camoz opened this issue May 31, 2024 · 2 comments

Comments

@camoz
Copy link
Contributor

camoz commented May 31, 2024

The help text of apy list-from-file -h is formatted wrong on console, see below.

I think the solution is adding /b to those paragraphs that should not wrap: https://click.palletsprojects.com/en/8.1.x/documentation/#preventing-rewrapping

Usage: apy add-from-file [OPTIONS] FILE

  Add notes from Markdown file.

  The example below should adequately specify the syntax. Any initial "key:
  value" pairs specify default values for all the following notes. The
  following keys are accepted:

  * model:    The note model (required) * tags:     The note model (optional)
  * deck:     Which deck the note should be added to (optional) * markdown:
  Set to "false" or "no" if apy should not use a markdown converter while
  converting the input note to an Anki note. (optional)

  Here is the example Markdown input:

      // example.md     model: Basic     tags: marked

      # Note 1     ## Front     Question?

      ## Back     Answer.

      # Note 2     tag: silly-tag

      ## Front     Question?

      ## Back     Answer

      # Note 3     model: NewModel     markdown: false (default is true)

      ## NewFront     FieldOne

      ## NewBack     FieldTwo

      ## FieldThree     FieldThree

@lervag
Copy link
Owner

lervag commented Jun 1, 2024

Sorry, but could you specify more clearly what is wrong with the formatting here?

@lervag
Copy link
Owner

lervag commented Jun 1, 2024

Ah, I noticed. Thanks, this should be fixed in the latest version on master and will be part of the next release.

@lervag lervag closed this as completed Jun 1, 2024
lervag added a commit that referenced this issue Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants