Questions about the Nimbus format and custom arguments

[LucyI]

I'm running the windows cli thru the cmd prompt. Attempting to convert notes exported from Nimbus (Fusebase) to markdown. I had thought that the program would allow me to convert files, store them locally, and then import them in a later step, but the only process seems to import immediately to Joplin.

I'm also trying to customize, but neither of these custom arguments have worked:
jimmy-cli-windows: error: unrecognized arguments: --frontmatter joplin
jimmy-cli-windows: error: unrecognized arguments: --output-folder nimbus_note

Should I be able to output to a folder, for instance to use if I want to import into a different note app besides Joplin? I was hoping to import into Obsidian too...

Also, should the frontmatter argument work? What would be the structure of the command if I wanted to save the conversion to another folder and/or include frontmatter?

OS
Win 11

[marph91]

The arguments look technically correct. Could you check that you are using the latest release (v0.0.28)?

With this release it's possible to convert the notes to a folder and then import to Joplin or Obsidian. Frontmatter should work, too. The final command could look like: jimmy-cli-windows nimbus_note/Example/ --format nimbus_note --output-folder nimbus_note --frontmatter joplin.

Side note: There is only a simple test file for NimbusNote, so the conversion might need some tweaking. If there are any problems, you can write here.

[LucyI]

Thank you I'll try again using the download you just linked, as I'm not sure which versions I have already. (I had downloaded two versions already; one didn't work at all. I looked in properties for each of those .exe files but there is nothing in the details listed for version number. Is there another way on a Windows 11 machine to view the version #?)

Question about your example command: You show the first directory in the path as "nimbus_note", which is identical to the format command, so I'm wondering if that is just coincidence or if it's a requirement that my exported Nimbus files be located in a folder called "nimbus_note"?

[marph91]

The version is printed in the log, like INFO Jimmy 0.0.28 (Pandoc 3.4) (but only in newer versions, though). In general it's best to use the latest release as it contains fixes and more test data.

The output folder name can be (almost) arbitrary. The name nimbus_note was just taken from your previous example.

[LucyI]

This was the result with the most recent version:

C:\Users\lucy>jimmy-cli-windows NimbusExportZipped --format nimbus_note --output-folder nimbus_note  --frontmatter joplin
Traceback (most recent call last):
  File "jimmy_cli.py", line 130, in <module>
  File "jimmy_cli.py", line 126, in main
  File "jimmy.py", line 109, in jimmy
  File "pypandoc\__init__.py", line 641, in get_pandoc_version
  File "pypandoc\__init__.py", line 797, in _ensure_pandoc_path
OSError: No pandoc was found: either install pandoc and add it
to your PATH or or call pypandoc.download_pandoc(...) or
install pypandoc wheels with included pandoc.
[PYI-23644:ERROR] Failed to execute script 'jimmy_cli' due to unhandled exception!

[marph91]

Hmm, might be an issue with Windows 11. It works in my VM and in the CI, but both use Windows 10. I will try to setup a Windows 11 VM, but it might take some time.

Edit: It wasn't an issue with Windows 11, but with the build system. It should be fixed with the latest release (0.0.29).