So how would a definition of a sentence text object look like? > Am 09.10.2019 um 12:57 schrieb Ainar Garipov (Vim Github Repository) > <vim-dev-git...@256bit.org>: > > Is your feature request related something that is currently hard to do? > Please describe > Currently, the definition of the sentence text object cannot be changed. This > prevents users from doing several useful things: > > Using sentence text objects with emoticons (e.g. :-)) as sentence-ending > punctuation. Note that while it is possible to require users to add a “real” > punctuation after the emoticon, some designers recommend against it. Example: > > Hey there :-) I hope you're all right. > > Using sentence text object with emojis (e.g. ☺) as sentence-ending > punctuation. Same as the above. Example: > > Hey there ☺ I hope you're all right. > > Using additional punctuation provided in Unicode, e.g. the “interrobang” mark > (‽). Example: > > Did they really do that‽ I can't believe it! > > Using American style of punctuation ordering with Unicode quotes. Example: > > “I don't like sand,” he said, “It gets everywhere.” She didn't respond. > > (A continuation of the pevious point.) Using Unicode quotes in Russian etc. > texts. Example: > > Я спросил: «Как дела?» Он мне не ответил. > > Using the Greek question mark in Greek texts. Example: > > Τι κάνεις; Όλα καλά; > > Describe the solution you'd like > An ability to redefine the sentence-ending markers would solve all these > issues. > > Describe alternatives you've considered > One alternative would be creating your own text object and remapping every > sentence-related movement. That sounds like an overkill to me, although it is > probably a working solution. > > Another alternative would be adding all those cases as “corner cases” into > the still-non-redefinable sentence text object. This sounds bad, since it > probably won't be a single change, but an ever-increasing number of changes > and complications. > > Additional context > None, I guess? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vim_dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/5035%40github.com.
-- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/2C31FD59-0B12-4E55-8C49-C6F81DC6F9A9%40256bit.org.
