Re: [vim/vim] Gvim: ligatures are reshaped when cursor moves across constituent characters (Issue #20916)
Foxe Chen (Vim Github Repository) <[email protected]> Sun, 02 Aug 2026 13:29:21 -0700
| Newsgroups | gmane.editors.vim.devel |
|---|---|
| Message-ID | <vim/vim/issues/20916/[email protected]> |
----==_mimepart_6a6fa8a19c00a_e21160111294 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 64-bitman left a comment (vim/vim#20916) @mao-yining In your expected behaviour video, I don't think that would be p= ossible (e.g. the ligature staying intact as cursor moves over it). This is= because the cursor is rendered as a "cell" just like other text with a bac= kground. Currently text with different backgrounds are rendered separately,= meaning ligatures cannot connect over background boundaries. It could be p= ossible, but I'm not sure how complicated that would be. --=20 Reply to this email directly or view it on GitHub: https://github.com/vim/vim/issues/20916#issuecomment-5160198758 You are receiving this because you are subscribed to this thread. Message ID: <vim/vim/issues/20916/[email protected]> --=20 --=20 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 ---=20 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 e= mail to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/vim= /vim/issues/20916/5160198758%40github.com. ----==_mimepart_6a6fa8a19c00a_e21160111294 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div style=3D"display: flex; flex-wrap: wrap; white-space: pre-wrap; align-= items: center; "><img height=3D"20" width=3D"20" style=3D"border-radius:50%= ; margin-right: 4px;" decoding=3D"async" src=3D"https://avatars.githubuserc= ontent.com/u/60551350" /><strong>64-bitman</strong> left a comment <a href= =3D"https://github.com/vim/vim/issues/20916#issuecomment-5160198758">(vim/v= im#20916)</a></div> <p dir=3D"auto"><a class=3D"user-mention notranslate" data-hovercard-type= =3D"user" data-hovercard-url=3D"/users/mao-yining/hovercard" data-octo-clic= k=3D"hovercard-link-click" data-octo-dimensions=3D"link_type:self" href=3D"= https://github.com/mao-yining">@mao-yining</a> In your expected behaviour v= ideo, I don't think that would be possible (e.g. the ligature staying intac= t as cursor moves over it). This is because the cursor is rendered as a "ce= ll" just like other text with a background. Currently text with different b= ackgrounds are rendered separately, meaning ligatures cannot connect over b= ackground boundaries. It could be possible, but I'm not sure how complicate= d that would be.</p> <p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda= sh;<br />Reply to this email directly, <a href=3D"https://github.com/vim/vi= m/issues/20916#issuecomment-5160198758">view it on GitHub</a>, or <a href= =3D"https://github.com/notifications/unsubscribe-auth/ACY5DGHD6YJY233LSPESL= PL5H6QCDAVCNFSNUABEKJSXA33TNF2G64TZHM2DAOJZG42DQMR3JFZXG5LFHM2TAMZZGEZDINJS= GGQXMAQ">unsubscribe</a>.<br />Triage notifications, keep track of coding a= gent tasks and review pull requests on the go with GitHub Mobile for <a hre= f=3D"https://github.com/notifications/mobile/ios/ACY5DGB6ZTLXSDJWZ55FSBD5H6= QCDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGAYTSOBXGU4KM= 4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ">iOS</a> and <a hre= f=3D"https://github.com/notifications/mobile/android/ACY5DGBHJ22EFU5SFL2IW5= T5H6QCDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJWGAYTSOBXG= U4KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ">Android<= /a>. Download it today! <br />You are receiving this because you are subscribed to this thread.<img= src=3D"https://github.com/notifications/beacon/ACY5DGGVY2YQ65LVRSGNSE35H6Q= CDBFCNFSM6AAAAAC4WB347OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3= TUL5UWJTYAAAAACM4SMJTKM4TFMFZW63VKON2WE43DOJUWEZLE.gif" height=3D"1" width= =3D"1" alt=3D"" /><span style=3D"color: transparent; font-size: 0; display:= none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: = 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><vim/vi= m/issues/20916/5160198758</span><span>@</span><span>github</span><span>.</s= pan><span>com></span></span></p> <script type=3D"application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/vim/vim/issues/20916#issuecomment-5160198758"= , "url": "https://github.com/vim/vim/issues/20916#issuecomment-5160198758", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script> <p></p> -- <br /> -- <br /> You received this message from the "vim_dev" maillist.<br /> Do not top-post! Type your reply below the text you are replying to.<br /> For more information, visit <a href=3D"http://www.vim.org/maillist.php">htt= p://www.vim.org/maillist.php</a><br /> <br /> --- <br /> You received this message because you are subscribed to the Google Groups &= quot;vim_dev" group.<br /> To unsubscribe from this group and stop receiving emails from it, send an e= mail to <a href=3D"mailto:[email protected]">vim_dev+uns= [email protected]</a>.<br /> To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/= vim_dev/vim/vim/issues/20916/5160198758%40github.com?utm_medium=3Demail&utm= _source=3Dfooter">https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/= 20916/5160198758%40github.com</a>.<br /> ----==_mimepart_6a6fa8a19c00a_e21160111294--