-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On June 4, 2014 3:48:42 PM GMT+03:00, Ingo Karkat <sw...@ingo-karkat.de> wrote: >On 04-Jun-2014 13:34 +0200, Axel Bender wrote: > >> I'd already be happy if virtcol() would take into account the length >of the showbreak string. I'm otherwise prepared to work with UTF-8 >characters... > >Character widths are not directly related to this, but that little >incorrectness in your otherwise precise and welcome bug report >shouldn't >have provoked such a rant. Sorry. > >> I consider this a flaw (well maybe a bug?) that should be fixed. > >I can reproduce this issue with 7.4.264. Even worse, :set linebreak >also >affects the virtcol() value and makes it wrong (when such wrap occurs). >So, one only gets correct values out of virtcol() with :set sbr= nolbr; >which indeed should be fixed! I am not sure it is a bug. Most likely it is absolutely correct behavior: pretend you need to know on which virtual line of the current line cursor is located and on which virtual column on this virtual line. Please describe how you will solve this with current behavior of virtcol() and with proposed one. Discussing whether this behavior is a bug or not is pointless without showing the use-case. I know that the above task may only be solved with "bugged" virtcol(), otherwise you will have to do option parsing for yourself which is a waste of time. I though think that virtcol() behavior is not a bug, but documentation is incorrect (it says "the last screen position occupied by the character at that position, when the screen would be of **unlimited width**" which obviously contradicts with the current behavior: no wraps are possible on the screen with unlimited width hence these options may not apply). > >-- regards, ingo -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQI1BAEBCgAfBQJTjzDRGBxaeVggPHp5eC52aW1AZ21haWwuY29tPgAKCRCf3UKj HhHSvg4uEAClhxgkmHRrWOvApOa70j8Zzw560RRQA6xRspJWg9UiyOEEsc2e+7O1 3gMy2HBr3kdPz7dwtWpe3azoDPvvIQe2+cznn1HPuqxtsQfGy/bWntGbBknpNhff 3V3AAD2DfmjU+0mu9gUs5+9NG7ROZg0PfHSgRkbfa759cD7GUG1fsVBPsbPy+aYM jjEV27/X61pkKsF5JgyyFpNG7pYXYrAEl9JiH0/QSuXYYjt9ptwHoEdrdwF9CFVi Ums+bp74pGwyOCMlVoVUImJT3MrHk6yiUFAgGBZqZsFWUsRYTvFluxWMTD6pLeJz +wL6WCnVxqRIZxvKFtySmZeAgRF1aRWVbFOEFz0IUjv1yhCleNWNVSdCK7FAFmvO Z6aSfyxTcgaKw9SEOxBtwysl8+BrmERv26zGt4Mfo6zxHLgPEV6eGA6e7wdWmy0z 9Cb4VKl395aLvlH2BqTQdKCp5OPhYt9wiVTHtB8LVM6DIMkyGOsscbLFNRiLedfx SovSVnsl2jzszxeOzKtmHW5uKMrrutNS3dVilZCMs1j/qm45+b0O+KGpiMwNTNHP wxJYU5jpXGEjZePZ98F5nUmopRFKDmNNfiMJQCuxVCNUJN6HKA2NfTWRiVb98HQx F05yoz1yfjEVtkWJjt+7Tg8JXCta55BkW8QhyRTgJNQLDFNUWJOQZA== =5tsG -----END PGP SIGNATURE----- -- -- 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. For more options, visit https://groups.google.com/d/optout.
