Open stukev opened 7 months ago
Yihaa, thank you for reporting me this issue and to let me improve Yarle!
Hi @stukev , So does it just hang if you start it via npx? Do you have any crash logs?
Hey @akosbalasko Not hanging from the looks of it, it simply doesn't start the conversion. GUI neither crashed nor did anything after waiting for around 2 hours. On NPX after the log I posted above it simply outputs nothing else after for now close to 2h too. Is there some debugging or verbose flag I can activate for more output?
Edit: I think the npx command might actually be doing something. The output folder is being filled up with .md and image files. I guess it's working but simply not giving any output to the console or GUI?
So upon watching the output folder with du -sh obsidian_output
I can confirm it is converting the files and I can also check when it's done by running the command repeatedly until there are no more changes in file size. There's still one problem though that I don't know how many (if any) notes failed conversion. Any ideas?
Hi @stukev , It should be something around your notes, try to localize the issue by searching for specific and/or strange note names/content in Evernote. Exclude webclips first, those can lead strange behaviours too.
Hello. I've tried the latest .deb and everything works until I click on "Start conversion". Nothing happens. I'm trying to convert Evernote ENEX files to Obsidian with the standard config (no changes).
Afterwards I used the config file from the UI installer and ran the command line, got this output but I'm unsure if it's even doing anything now? Should it not give some kind of progress or other reports? I'm very confused by this tool.
npx -p yarle-evernote-to-md@latest yarle --configFile ../obsidian_output/yarle_20240213_130542.config Need to install the following packages: yarle-evernote-to-md@latest Ok to proceed? (y) y npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead npm WARN deprecated domexception@4.0.0: Use your platform's native DOMException instead
I believe this is likely the same issue as in #436 .