Releases: jonjampen/obsidian-xournalpp
v1.1.2
Added
- Added confirmation modal before enabling the auto-export setting due to potential overwriting (PR #20).
Fixed
Contributors
Thank you, @JacobASorensen and @AstyCX, for reporting and implementing these changes.
v1.1.2-beta
Release Notes
This is a pre-release to v1.1.2 which is expected to be released next Friday (20.06.2025). To beta test this new version, check out this guide.
Added
- Added confirmation modal before enabling the auto-export setting due to potential overwriting (PR #20).
Fixed
Contributors
Thank you, @JacobASorensen and @AstyCX, for reporting and implementing these changes.
v1.1.1
Added
- Added Quick-Switcher like command to search through all Xournal++ files in the vault and opening them in Xournal++ or their corresponding PDF in Obsidian.
- Updating all link references to
.xoppfiles and their corresponding.pdffile when using the "Rename PDF & Xournal++" feature (closes #18). - Added second button in Xournal++ file creation modal to directly open the new file in Xournal++ after creation (closes #17).
v1.1.1-beta
Release Notes
This is a pre-release to v1.1.1 which is expected to be released next Thursday (15.05.2025). To beta test this new version, check out this guide.
Added
- Added Quick-Switcher like command to search through all Xournal++ files in the vault and opening them in Xournal++ or their corresponding PDF in Obsidian.
- Updating all link references to
.xoppfiles and their corresponding.pdffile when using the "Rename PDF & Xournal++" feature (closes #18). - Added second button in Xournal++ file creation modal to directly open the new file in Xournal++ after creation (closes #17).
v1.1.0
⚠️ Breaking Changes
- If the user-set Xournal++ installation path contains spaces, the user now has to manually add double quotes (
") around the installation path. This fixes an issue with commands with multiple parameters (see below).
Migration Guide
If your Xournal++ installation path contains spaces in the path, you must manually add double quotes (") around it in the plugin settings. If you however use a command as your installation path (like with flatpak-spawn ...) that includes spaces, you do not want to add double quotes around it. This ensures correct command interpretation. To check whether your selection will work, you can open a terminal and enter the command YOUR_XOURNALPP_INSTALLATION_PATH --version which should return the version of Xournal++ without an error.
Fixed
- Fixed user-set Xournal++ installation path not working when consisting of multiple parameters with spaces (fixes #13, PR #16).
- Fixed start-up error when file explorer is closed (fixes #12).
Improved
- Improved plugin startup efficiency by only exporting Xournal++ files to PDF that have since changed (fixes #14, PR #15).
Contributors
Big thanks to @diam0ndkiller and @JacobASorensen for implementing these fixes and improvements!
v1.0.11
v1.0.10
Added
- Added option to delete both XOPP and corresponding PDF file from the file menu and the commands.
- Added option to rename both XOPP and corresponding PDF file from the file menu and the commands.
Improved
- When selecting a folder for a new file the default folder is no longer set as the default input value but as the top option.
Contributors
Thanks to @AstyCX for suggesting these features and providing implementation ideas.
v1.0.9
v1.0.8
Added
- Fuzzy suggest for selecting the folder when creating new files.
- Added command to insert embedded PDF after file creation (#7).
- Separate modal for setting a folder and naming the new file (#7).
Fixed
X++button didn't show immediately on app startup and threw an error. Now it appears right away when the app starts (#7).
Contributors
Thank you to @AstyCX for implementing the new features from #7 and fixing the bug.
v1.0.7
Added
- Added commands to insert links for PDF, XOPP, or both after file creation (#4).
- Added setting to specify a default folder for new Xournal++ files (#4).
Improved
- Added information to documentation for setting the installation path if both Obsidian and Xournal++ are installed through Flatpack (#2).
Contributors
Thanks to @Susrex for the feature requests, and @lguenth, @aerits, and @mathmd for suggesting an installation path when using Flatpack.