Hady Osman

Thanks for making this change. My original preference for solving this was not exposing the new "file location path" as a preference so users are not given too much complexity...

You will also need to manually bump the plugin version in order for it to be published as a new version. This needs to be done in `manifest.json` and `package.json`.

@smarquez1 I originally wanted to give the PR's author the opportunity to contribute a change to the plugin so I haven't implemented this myself. I will likely fix this myself...

> I'm told that after attempting to import the clippings file again, the 'file already exists' How are you told that? In a pop-up? Can you turn on your Developers...

`path="Books\BookHighlights\.md` looks suspiciously dodgy to me. Did you customised the File Name template field? It is possible that the field does not have any unique field variables there (e.g. book...

Thanks for raising this. I'll rename and keep this issue open. I think it would be good to add some safeguards to either prevent a bad template name to be...

@adampick99 I haven't been able to recreate this issue at my end. Do you mind if you share the template you had which created this problem?

Thanks for raising this. You are running into an issue with the "smarts" that's been built in the plugin to truncate long book titles in a meaningful way (regardless if...

> Would it be possible to have a configuration option to disable the truncation altogether? You should be able to use the existing feature of using `{{longTitle}}` as a variable...

This has now been fixed in [1.6.9][1]. Can you try it out and let me know if this fix or the previous solution I suggested have helped you achieve what...