-
Notifications
You must be signed in to change notification settings - Fork 13
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
Give a count to bold/italic/strike mappings #103
Comments
Hi again @victorkristof, you are on 🔥 my man, I like it! 👍 I think this should also not be too hard to implement and would make sense indeed, thank you for yet another good suggestion <3 |
Glad to hear! By the way, currently <prefix>b is applied on a Vim In fact:
becomes
when I press <prefix>b. But I was expecting
|
It depends on how |
@victorkristof yoho! Been working on this a little bit, I think #104 supports all the behavior in this PR and a bit more and actually also fixes some small deficiencies I noticed while testing. You can pull master / update mkdx normally to check it out, let me know if anything doesn't work properly for you, otherwise I think this one can be closed :) |
See my comment in #101 :) |
@victorkristof if you update again it should be fixed, re-merged all features I removed before |
Awesome! The count works perfectly and will be super useful. Thank you! |
Aight, with that I'll close this one, let me know if you see any more issues, feel free to reopen if you do! Cheers for the suggestion, I may end up using this one myself now as well :) |
I really like how wrapping works, it makes it so easy to add markup to text. Most of the time I want to mark in bold or italic a single word only, so using <prefix>b is really convenient. But when I want to do it for several words, I need to visually select them first.
Would it make sense to add a count to these actions, such that [count]<prefix>b would mark the word under cursor and the
[count]
following words in bold?Example
Cursor location indicated by
^
.I press 2<prefix>b to obtain
The text was updated successfully, but these errors were encountered: