Continued maintenance?

[scallaway]

trafficstars

I've been looking for a plugin pretty much exactly like this to improve my composing experience in Obsidian but it doesn't look as though this plugin works anymore?

I wanted to ask briefly whether there was any intention of reviving this, given it's not been updated in a good few years.

I was also wondering whether there were any changes surrounding the Obsidian API that would make the Automatic breaking that you've listed in the original README possible.

If none of this is possible, I'll endeavor to build on what already exists here with a fork of the plugin myself!

[bkis]

Hi there! I am happy to hear you find this useful. It's true - I didn't find the time to maintain this for quite a while. I just checked and for me the plugin seems to be still working fine with Obsidian 1.5.12.

Before running the "Hard Breaks" command (all text selected):

After running the "Hard Breaks" command (all text selected):

I agree that the original idea of being able to "switch on" the plugin to just convert soft line breaks into hard ones as you type would be much better than what the plugin does now. It's just that I kind of underestimated the technical implications you have to deal with when going down this route. I remember it was quite tricky to cover some edge cases and I just didn't have the time to implement it right. That's why I made peace with this "simple" approach of just adding a command that converts all the breaks that are currently there.

That being said, if you want to improve/extend this plugin, you're very welcome to do so! You're free to create your own fork, of course (it's open source software, so go ahead) - but it might also be a good idea to just work on this project here, as new features would instantly get to whoever has the plugin already installed. With ~4,5k Downloads it's not overwhelmingly popular, but it's not nothing, I guess.

So do as you like - create PRs, create a fork, it's your call. If you're really committed to this I could even transfer the repo to you, but then I don't know how the Obsidian plugin registry will/can handle this case, as the releases are just pulled from Github. I don't know if it'd be enough to change the repo reference and continue working on this or if it'd have to be registered as a "new plugin".

I hope this helps!