Hi Kazunobu, On Tuesday, 9 August 2016 15:46:38 UTC+2, Kazunobu Kuriyama wrote: > Hi Manuel > > 2016-08-09 20:06 GMT+09:00 manuelschiller.pimail via vim_dev > <vim...@googlegroups.com>: > > > Dear Kazunobu, > > If you don't mind, please consider using friendlier 'Hi' instead of 'Dear.' > It's OK to me even if you omit greeting itself. >
Done. :) Now I just have to remember... > > On Tuesday, 9 August 2016 12:03:47 UTC+2, Kazunobu Kuriyama wrote: > > > Hi Manual, > > I'm sorry about my writing your name wrongly. > I get that about once a week to every two weeks in my inbox, and actually consider it a bit of a compliment when people compare me to the fine manual which each and every one of the of course has read most dilligently, intentionally or otherwise... ;) So: No worries, as long as I get that you're trying to send me a message, it's all good... > > > [...] > > > Okay, fair enough. :) It might take some time though, since I'll be moving > > to a different country to start a new job in the coming month. > > I see. You are busy for a while. > > > Actually, that gives me its own convenience. It gives me some time to make > > myself get accustomed to ligature fonts and their usage on Vim. Nothing > > wrong. > Have fun. Just be careful, you might not want to go back to something truely monospaced... ;) > > > What direction would you like to see things heading? I'll most likely be no > > good at finding the ultimate patch that gets everything right because I'm > > not enough of an expert in the font rendering library field - it only > > dawned on me what was going wrong in that code recently. > > > > If you'd want the ultimate ligature-clean solution, I anticipate one would > > need to revamp much of the gtk display code to update the right bits of the > > screen and keep the relation between glyph and characters, especially for > > the cursor drawing routines, so the right bit gets redrawn. That's a tall > > order, and I feel my C and gtk/pango skills are a bit too much in the range > > from non-existant to rusty for that. (My C++ is good, but that doesn't help > > here. ;) Moreovwe, we may want to use a patch along the lines I suggested > > to gain a bit of experience to learn about what's important in this > > business before we try and design the patch that solves all ligature > > issues... It may involve bug reports, and users asking for features, but > > that's very good feedback once we understand where the problem is, guiding > > us toward a better solution. > > If you don't have any clear direction on that, how about rethinking all the > issues that have been raised in this thread so far. You might find some of > them needed to be fixed or might get a better idea to address them. > > Doing that would tell us (hints of) what we need to know and what we have to > do. > Well, I'll see what I can do. For non-latin and non-greek alphabets, there's not much I can do because I know too little about those writing systems to know how things should look, though... I will need help (and potentially an expert) on that front. > > > In the meantime, I may be able to clean up the glyph cache for ascii codes > > < 128, for example, by having a shaping call per character code, so we only > > need to store a single glyph in the cache, if you feel that would help. One > > could also think about making the ascii code range which passes through the > > glyph cache configurable, if you guys would prefer that over the static > > list like the one I took over from the original patch proposition. > > I think it's worth a try. Even if an effort fails, that will help us > understand why the current way is not bad. > Okay. > > Is there anything else I can do that you or others would feel is valuable > > to have? Feel free to keep the suggestions coming... > > I'd also like to hear the voices of people who want to see ligatures on Vim. > I agree. I'm just not sure how many we'll attract from off-list (or how many people on-list are interested) without having a demonstrator patch out there for which people can hand in suggestions. But we can cross that bridge when we have to. Cool, that sounds like a plan. Cheers, Manuel > > Best regards, > Kazunobu > > > > > All the best, > > > > Manuel > > > > > > > > > Kind regards, and enjoy your vacation, > > > > > > > > > > > > Thanks, > > > Kazunobu > > > > > > > > > Manuel > > > > > > > > > > > > > Best, > > > > > > > Kazunobu > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Regarding your question about the range of ascii characters to which the > > > tabulated cache is applied: Restricting this to subranges of [0,127] that > > > I mentioned should get you most of the speed improvement that can be had > > > from bypassing pango's shaping, and from what I understood, the space ' ' > > > is especially important, since it's used to clear the screen. > > > > > > > > > > > > > > > > > > > > > > > > > > > > But the restriction to those subranges also means that strings containing > > > the popular "programming ligatures" like "<=", ">=", "!=", "->" etc. will > > > be subject to pango's shaping, thus ligatures are displayed... In a way, > > > we're selectively disabling the "shaping bypass" for less obvious > > > character ranges where ligatures are more likely (and more likely to be > > > missed by programmers). > > > > > > > > > > > > > > > > > > > > > > > > > > > > I hope this clarifies things a bit. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for the interest, > > > > > > > > > > > > > > > > > > > > > > > > > > > > Manuel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > 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+u...@googlegroups.com. > > > > > > > > > > > > > > > > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > -- > > > > > > -- > > > > > > 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+u...@googlegroups.com. > > > > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > -- > > 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+u...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- -- 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.
