-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Change Textobj: Consider extending {notifyNotFound=false}
to indentation object's warning "Current line is not indented"
#97
Comments
It could be opinionated though because this isn't the same kind of "not found within n lines" message as the one disabled by Alternative idea: some kinda |
Ah yes, those two were simply overlooked. Can you make a PR adding notifyNotFound as conditional to those two notifications? (I'm not at home for a bit but I have Github mobile access, where accepting PRs is ready though) |
Thanks, yeah I can make one and good to know my request made perfect sense :) |
Although are there more cases related to this? Examples:
Edit: Yeah the reason it is the way it is is because the only place where notifyNotFound is checked against is here: nvim-various-textobjs/lua/various-textobjs/utils.lua Lines 28 to 35 in b8f7e97
So I'm wondering whether we want to wrap other warnings in a similar util function and check it there too, or if there's a need to have more granularity (a second quietflag)? |
fixed all cases |
Astonishing. Thank you very much 😄 |
Change requested
I'd prefer to have all warnings turned off when there's nothing to be done, so would feel consistent if for example
dii
on an unindented line wouldn't give a warning message either whennotifyNotFound=false
Looks like there's also a warning "No indented line found." (code) associated with indentation textobj, but I haven't found in what situation that emits. But most likely my request concerns that too.
Relevant PR where
notifyNotFound
was added: #85Sample Text
Press
dii
Gives warning
"Current line is not indented."
But could it be quiet?
Checklist
The text was updated successfully, but these errors were encountered: