The "move to next sentence" command gets stuck when it gets to a tab character. This means, for example, that it gets stuck on any indented bullet points (if you have the editor set to "indent using tabs" rather than spaces)

It may seem too granular to move individual words around, but I actually find myself wishing I could whenever I'm fiddling with sentences. Would this too be possible someday maybe?

I love this plugin, and I find myself wanting "Select to end of sentence" and "Select to beginning of sentence," for the same reasons that "Delete to end of sentence" and "Delete to beginning of sentence" are useful.

Just a thought.

Thank you for making this plug-in!

I realize this plugin is focused mainly on manipulation of sentences but I was wondering if selecting to the end/beginning of a paragraph would fit into the scope of this plugin.

ex:

Lorem ipsum dolor sit amet, consectetur adipiscing elit<cursor here>. Vivamus gravida sagittis maximus. Nam vel lobortis lectus. Morbi rutrum ex nec risus rutrum, at ultrices libero pellentesque. Vestibulum lacinia, odio non sagittis ornare, diam nibh malesuada nulla, eget ultricies quam sapien sed diam. Aenean non viverra quam. Donec bibendum consectetur laoreet. Pellentesque et semper libero. Nulla nec metus eleifend, dapibus diam ac, porta sapien. Nulla sagittis sollicitudin pellentesque.

• so in this example, if select to end of paragraph were invoked. everything after Lorem ipsum dolor sit amet, consectetur adipiscing elit would be selected.
• inversely, if the select to beginning of paragraph were invoked. Only Lorem ipsum dolor sit amet, consectetur adipiscing elit would be selected.

Let me know if you have any thoughts

Is it possible to work on this on Windows at all? The Marcus Olsson guide to writing plugins suggests running npm run dev to compile it. That complains that there is no "dev" script. npm run build gives an error message which suggests that it's looking in the directories under npm, rather than here.

I think that by plundering and reusing the utils and actions scripts from your editor plugin I might make some progress, but not if I can't get anything to run at all.

It would be really nice if when you navigate to the beginning of the sentence and then navigate back again, it would take you to the previous bullet. When you go forward at the end of a bullet, it does take you to the next one.

I think this functionality is being blocked by the Outliner plugin, which prevents you from going to the bullet when going to the beginning of a line. Unfortunately, Outliner is a super useful plugin (and very widely used), so I can't disable it.

I understand if you don't want to solve a problem caused by another plugin, but if this is something that you'd consider, I'd appreciate it :).

Best,
Dan

Firstly, thank you so much for this plugin and the time you've taken to develop it.
I end up doing a lot of editing of long-form text for publishers and have a few suggestions which may be useful.

In no particular order:

• Delete to last/next punctuation. Don't often need to remove a whole sentence, sometimes, it's just a clause you need to adjust.

• Some capitalisation options that work alongside the existing delete sentence functionality. For example, delete from end of previous sentence to cursor, and then capitalise word at cursor. Really great for editing the starts of sentences quickly, so you can chop off words that lead up to where the start of the sentence should be.

• zoom to sentence. Sometimes, I just want to see just the current sentence so it can be re-written without any of the surrounding text in a kind of sentence scratch-pad to try new versions, see how things sound when expressed differently, etc. Imagine being able to zoom into a current sentence, try a few different versions/re-writes, and then zoom out to see your selected modification in context of the rest of your text. A bit like a sandbox for sentences.

Thank you!

I just started using this plugin and found the select current sentence feature to be neat, but the first sentence I tried it with was a bulleted list item, and I found that by default the Regex will select the list bullet. I have managed to fix this by changing the regex to:
[^.!?\-\*\+\s][^.!?]*(?:[.!?](?!['"]?\s|$)[^.!?]*)*[.!?]?['"]?(?=\s|$) (adds \-\*\+ in the first negated set)

I can put this in a PR for constants.ts if you'd like, though perhaps a better option (that I know far too little to work on myself) would be adding 'presets' to the settings page, with human-readable descriptions of a few different methods/expressions.

Note: I'm not the best with Regex but as far as I'm aware this doesn't have any glaring issues with it. Feel free to correct me if this would mess with anything.

Another issue I found is when the sentence you're selecting is at the end of a paragraph. I'm not that great with javascript/typescript but it seems like the issue is in actions.ts where the plugin tries to select the space after a sentence. If the sentence is at the end of a paragraph, though, this will select the next line below. This causes two issues:

If there is no line below what you're selecting, an "Uncaught RangeError" occurs in the console. Removing the +1 from line 170 prevents the error from occurring. I don't think this actually affects anything, but it's still nice to avoid.

Additionally, All characters in the found sentence following the character you're currently selecting will be moved to a new line, along with your editing caret. Removing the +1 from line 170 also prevents this from happening.

I personally don't see the value in selecting the space after the sentence, but it was put there intentionally so I understand you probably have reasons for doing so. The only reason I can think of for doing it would be to delete the sentence in its entirety, which is a good use of the select sentence feature, but could also be moved to its own command. A more user-friendly solution might be to not select the space afterwards, but to remember that it's there until an action is performed. If the delete key is pressed, then delete the space. This means users who were bolding/italicizing/quoting don't have to move their formatting.

Again, I'm not exactly able to do that myself, but I can create a PR for removing the +1 from line 170 in actions.ts if you'd like me to.

P.s. Thanks for all your work on this plugin! It fixes some annoying things with selection/deletion on macOS which can be very inconsistent otherwise, and I imagine it's even nicer to have on Windows/Linux which don't have the paragraph select feature AFAIK

As a writer, this plug-in has potential to make Obsidian the preferred writing application.

The commands work well, but the Move to next sentence moves directly to the next block, skipping other sentences.

Thank you.

Firstly, thank you for making such an amazing plugin, which is really convenient. I modified the varibale in constant.ts to satisfy my requirement. But I'm afraid that this plugin's update in the future will overlay my change. So is there a solution to avoid this?

Thank you.