On Thursday, 15 September 2016 15:01:35 UTC+1, mcepl wrote: > On 2016-09-15, 12:33 GMT, manuelschiller.pimail via vim_dev wrote: > > Hi Matěj, Christian, > > > > I've added the value which is equivalent to the previous patch, i.e. > > > > " this should keep character 0-31 (control characters), and > > " [0-9A-Za-z] flowing through the glyph cache, and the rest > > " < 128 will bypass it > > let g:gtk_nocache=[0x00000000, 0xfc00ffff, 0xf8000001, 0x78000001]
Hi, > I had to make some typo or something, because when copying this > line into my ~/.vimrc I got it working as before. Thank you! glad that's sorted. :) > > About the criticism that this is not the most user-friendly > > option to set: That's a very valid point. My reasoning was > > thus: > > That was not my problem. Read > http://www.joelonsoftware.com/uibook/chapters/fog0000000059.html > > # Every time you provide an option, you're asking the user > # to make a decision. > > I would even say, “you force the user to make decision”. And he > will be grumpy for that. You should apologize every time you > force user to do anything else than why he started to use your > program in the first place. Interesting read. Thanks for the pointer. > Which is why I said, that if you need this during the > development, then I don't care. However, if normal user ever > sees it, she will get fits and she would be right. Well, I was thinking along the lines that using these special ligature glyphs is definitely a matter of preference. (For example, Bram had a pretty strong opinion about ">=/<=" and how he would not like to see ligatures for these combinations, I seem to remember.) I thought that not setting any option in .vimrc will produce usable output (without ligatures) which is fine for the majority of people who don't care about ligatures. No choice involved for the unsuspecting user, it'll just work, and produce unsurprising output for a hassle-free editing session (albeit without the ligature eye-candy... ;). For those who want ligatures, they'll have to look at the patch at the moment, and set a variable in their .vimrc. In the long run, we should have a nice front end for that, and provide documentation, so it becomes easier to see what needs to be put into .vimrc. I didn't know about the article when I wrote this, but the logic of the previous two paragraphs seems to tie in with the spirit of the article's last paragraph or so. Displaying ligatures (or not) is a matter of preference, and options should allow users to fine-tune what they would like to see. For people who don't care, they don't need to set anything, and get vim's old (ligature-less) behaviour that they're used to. I'll do a more careful reading of the article tonight, in case I missed something important (which could well be - feel free to point it out, since I only skimmed the article so far). > > - The "user-facing part" depends very much on what people > > would like to have. > > “Nothing” is the only possible answer, I think. > > > That said, I'm very happy for suggestions (or patches), and > > will try to have a draft ready soonish when suggestions do > > trickle in. :) > > Thank you very much for your work, despite my criticism. I appreciate the criticism! You haven't convinced me yet to change the default, but I'm willing to be convinced by the right argument. From what I've grasped from the article, I tend to lean more towards the current implementation (although I think we need something more user-friendly for the users who want ligatures). But ultimately, what we come up with will have to convince the rest of the community, so it doesn't matter that much what I think, anyway. :) So keep the arguments coming... Cheers, and thanks, Manuel > Matěj > > -- > https://matej.ceplovi.cz/blog/, Jabber: [email protected] > GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 > > Quod fuimus, estis; quod sumus, vos eritis. -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
