-
Notifications
You must be signed in to change notification settings - Fork 16
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
No line wrap #25
Comments
Came here looking to see if someone else has this issue and I'm glad someone else posted it. When in writing mode, there doesn't appear to be any line-wrapping for files ending in .cook - which would "activate" the Cooklang spec in read mode. Read mode renders fine, but when in writing mode, the line keeps scrolling off the right past the pane edge, which makes things difficult to work with directly in Obsidian. My workaround has been to manually edit or create .cook files in the vault with a text editor. |
Looks like something might have changed in Obsidian that's causing this issue. I found if I changed this line in - lineWrapping: (this.app.vault as any).getConfig('lineWrap'),
+ lineWrapping: true, From what I can uncover, it looks like this used to be a configurable setting but it was removed in 1.02. I could create a pull request to apply this fix, or alternatively add the setting into the Cooklang plugin settings so it's still an option if people want it, but it's not clear to me that this project is being closely maintained. Footnotes |
Honestly, the path of least resistance, as I'm not a developer and would have difficulty getting an environment set up sufficiently to apply the fix myself, and then build the plugin myself, and install it. Thank you for debugging this and finding a solution! Edit: I've discovered where to patch this if you already have it installed as a plugin.
It should look something like this:
|
Wrapping works fine in my .md files. Perhaps it is an issue introduced in a newer Obsidian version since this plugin was released?
The text was updated successfully, but these errors were encountered: