Re: gvim and ASCII glyphs

On Sunday, April 20, 2014 at 11:55:22 AM UTC-4, François Gannaz wrote: > Hello > > In a few words, here is a patch that makes gvim work better with ligatures > in fonts, which can be useful even for programmers. Details follow. > > I tried to use a Hasklig[^1], a font with ligatures intended for

Re: gvim and ASCII glyphs

On 2016-10-27, 21:01 GMT, Charles E Campbell wrote: > Well, I don't intend to spend hours re-inventing my scripts > which do a lot of housekeeping and are responsible for > updating my website, and which work with vimballs. Nor am > I about to start keeping your and other's git repositories >

Re: gvim and ASCII glyphs

Matěj Cepl wrote: > On 2016-10-27, 11:58 GMT, Tony Mechelynck wrote: >> Ohhh, so that's what you mean. Well, here is another try: Not >> being imitated, or not being a copycat himself, don't >> necessarily mean that Dr. Chip is wrong, especially with Vim, >> which prides himself about allowing

Re: gvim and ASCII glyphs

On 2016-10-27, 11:58 GMT, Tony Mechelynck wrote: > Ohhh, so that's what you mean. Well, here is another try: Not > being imitated, or not being a copycat himself, don't > necessarily mean that Dr. Chip is wrong, especially with Vim, > which prides himself about allowing the users to obtain the

Re: gvim and ASCII glyphs

On Thu, Oct 27, 2016 at 2:08 AM, Matěj Cepl wrote: > On 2016-10-26, 22:23 GMT, Tony Mechelynck wrote: >> Don't make the too frequent error to believe that everyone >> else, or at least most of them, has the same preferences as >> you. The fact that we hardly ever see a post about

Re: gvim and ASCII glyphs

On 2016-10-26, 22:23 GMT, Tony Mechelynck wrote: > Don't make the too frequent error to believe that everyone > else, or at least most of them, has the same preferences as > you. The fact that we hardly ever see a post about whether or > not vimballs are the way to go does not necessarily mean

Re: gvim and ASCII glyphs

On Wed, Oct 26, 2016 at 8:32 PM, Matěj Cepl wrote: > On 2016-10-26, 17:26 GMT, Charles E Campbell wrote: >> If you're using utf-8, its easy to get the glyph transform >> with mathmenu.vim (comes with >> http://www.drchip.org/astronaut/vim/index.html#MATH): type >=, select >> with

Re: gvim and ASCII glyphs

On 2016-10-26, 17:26 GMT, Charles E Campbell wrote: > If you're using utf-8, its easy to get the glyph transform > with mathmenu.vim (comes with > http://www.drchip.org/astronaut/vim/index.html#MATH): type >=, select > with visual-block (ctrl-v), then press the "&" key. Same sort of thing >

Re: gvim and ASCII glyphs

Matěj Cepl wrote: > So, for example how to make >= and <= be included so that they > translate into (glyphs from :digraphs): > > =< ≤ 8804 > >= ≥ 8805 > > Matěj > Hello: If you're using utf-8, its easy to get the glyph transform with mathmenu.vim (comes with

Re: gvim and ASCII glyphs

On 2016-09-15, 16:42 GMT, Matěj Cepl wrote: > That’s probably a good point: looking at issues on > https://github.com/tonsky/FiraCode/issues and > https://github.com/tonsky/FiraCode/wiki it seems there is > truly not The Right Way™ how to do it (especially, if Haskell > people get involved,

Re: gvim and ASCII glyphs

On 2016-09-15, 14:52 GMT, manuelschiller.pimail via vim_dev wrote: > 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

Re: gvim and ASCII glyphs

2016-09-15 23:31 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > On Thursday, 15 September 2016 15:14:03 UTC+1, Kazunobu Kuriyama wrote: > > 2016-09-15 22:43 GMT+09:00 manuelschiller.pimail via vim_dev < > vim...@googlegroups.com>: > > > > > > Hi Kazunobu, > > > > > >

Re: gvim and ASCII glyphs

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),

Re: gvim and ASCII glyphs

On Thursday, 15 September 2016 15:14:03 UTC+1, Kazunobu Kuriyama wrote: > 2016-09-15 22:43 GMT+09:00 manuelschiller.pimail via vim_dev > : > > > Hi Kazunobu, > > > > On Thursday, 15 September 2016 14:33:48 UTC+1, Kazunobu Kuriyama  wrote: > > > Hi Manuel, > > > >

Re: gvim and ASCII glyphs

2016-09-15 22:43 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > Hi Kazunobu, > > On Thursday, 15 September 2016 14:33:48 UTC+1, Kazunobu Kuriyama wrote: > > Hi Manuel, > > > > 2016-09-15 21:33 GMT+09:00 manuelschiller.pimail via vim_dev < > vim...@googlegroups.com>: >

Re: gvim and ASCII glyphs

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 > " <

Re: gvim and ASCII glyphs

Hi Kazunobu, On Thursday, 15 September 2016 14:33:48 UTC+1, Kazunobu Kuriyama wrote: > Hi Manuel, > > 2016-09-15 21:33 GMT+09:00 manuelschiller.pimail via vim_dev > : > > > > > On Wednesday, 14 September 2016 20:38:27 UTC+1, Christian Brabandt  wrote: > > > Hi, >

Re: gvim and ASCII glyphs

Hi Manuel, 2016-09-15 21:33 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > On Wednesday, 14 September 2016 20:38:27 UTC+1, Christian Brabandt wrote: > > Hi, > > > > On Mi, 14 Sep 2016, manuelschiller.pimail via vim_dev wrote: > > > > > > > > let

Re: gvim and ASCII glyphs

On Wednesday, 14 September 2016 20:38:27 UTC+1, Christian Brabandt wrote: > Hi, > > On Mi, 14 Sep 2016, manuelschiller.pimail via vim_dev wrote: > > > > > let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801] > > > > This contains a bitmap for each character < 128, which has the

Re: gvim and ASCII glyphs

On 2016-09-14, 13:28 GMT, manuelschiller.pimail via vim_dev wrote: > It allows users to hand-tune for which characters they want to > bypass the glyph cache by putting a line in .vimrc, e.g. > > let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801] Tell me, please, you have never

Re: gvim and ASCII glyphs

On 2016-09-14, 13:28 GMT, manuelschiller.pimail via vim_dev wrote: > It allows users to hand-tune for which characters they want to > bypass the glyph cache by putting a line in .vimrc, e.g. > > let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801] > > This contains a bitmap for each

Re: gvim and ASCII glyphs

2016-09-14 6:09 GMT+09:00 Matěj Cepl : > On 2016-08-11, 15:40 GMT, Kazunobu Kuriyama wrote: > >> Screenshot attached. (I haven't try PragmataPro.) > > > > I don't either for an obvious reason..Isn't there a free version? :) > > Would https://github.com/tonsky/FiraCode/ work? > >

Re: gvim and ASCII glyphs

On Tuesday, 13 September 2016 23:21:01 UTC+1, mcepl wrote: > On 2016-08-08, 12:50 GMT, Tony Mechelynck wrote: > > You should see, in that order, the glyphs for ff fi fl ft st > > ffi ffl. > > I absolutely don't like them (in the monospaced fonts that > > have them; in serif or sans-serif fonts

Re: gvim and ASCII glyphs

On 2016-08-11, 15:40 GMT, Kazunobu Kuriyama wrote: >> Screenshot attached. (I haven't try PragmataPro.) > > I don't either for an obvious reason..Isn't there a free version? :) Would https://github.com/tonsky/FiraCode/ work? Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz

Re: gvim and ASCII glyphs

On 2016-08-08, 12:50 GMT, Tony Mechelynck wrote: > You should see, in that order, the glyphs for ff fi fl ft st > ffi ffl. > I absolutely don't like them (in the monospaced fonts that > have them; in serif or sans-serif fonts it's different, > especially in serif italic). OTOH, I think that

Re: gvim and ASCII glyphs

On 2016-08-07, 11:27 GMT, manuelschiller.pimail via vim_dev wrote: > Please let me know if it would be possible to include this, > and if not, at least the patch is public now where people can > find it if they want it. https://github.com/vim/vim/issues/418#issuecomment-246748135 and the

Re: gvim and ASCII glyphs

On Saturday, 13 August 2016 22:27:33 UTC+2, manuelschi...@googlemail.com wrote: > On Saturday, 13 August 2016 19:55:23 UTC+2, manuelschi...@googlemail.com > wrote: > > On Thursday, 11 August 2016 19:30:57 UTC+2, Stefan Schwarzer wrote: > > > On 2016-08-11 17:40, Kazunobu Kuriyama wrote: > > >

Re: gvim and ASCII glyphs

On Saturday, 13 August 2016 19:55:23 UTC+2, manuelschi...@googlemail.com wrote: > On Thursday, 11 August 2016 19:30:57 UTC+2, Stefan Schwarzer wrote: > > On 2016-08-11 17:40, Kazunobu Kuriyama wrote: > > > 2016-08-11 23:44 GMT+09:00 Ken Takata : > > >> Screenshot

Re: gvim and ASCII glyphs

On Thursday, 11 August 2016 19:30:57 UTC+2, Stefan Schwarzer wrote: > On 2016-08-11 17:40, Kazunobu Kuriyama wrote: > > 2016-08-11 23:44 GMT+09:00 Ken Takata : > >> Screenshot attached. (I haven't try PragmataPro.) > > > > I don't either for an obvious reason..Isn't

Re: gvim and ASCII glyphs

On 2016-08-11 17:40, Kazunobu Kuriyama wrote: > 2016-08-11 23:44 GMT+09:00 Ken Takata : >> Screenshot attached. (I haven't try PragmataPro.) > > I don't either for an obvious reason..Isn't there a free version? :) As far as I know there's no free version. The cheapest is

Re: gvim and ASCII glyphs

Hi Ken, Thank you for the headsup! Great. Bram must feel relief now :) 2016-08-11 23:44 GMT+09:00 Ken Takata : > Hi, > > 2016/8/11 Thu 14:36:57 UTC+9 Kazunobu Kuriyama wrote: > > Hi Tony, > > > > 2016-08-11 10:05 GMT+09:00 Tony Mechelynck : > >

Re: gvim and ASCII glyphs

Hi, 2016/8/11 Thu 14:36:57 UTC+9 Kazunobu Kuriyama wrote: > Hi Tony, > > 2016-08-11 10:05 GMT+09:00 Tony Mechelynck : > > Hm. gui_gtk_x11.c is of course only for gvim with GTK GUI running on > > Linux-X11. GTK2, and now even GTK3 ("new in 8.0"), are of course the > >

Re: gvim and ASCII glyphs

On Thu, Aug 11, 2016 at 7:36 AM, Kazunobu Kuriyama wrote: > Hi Tony, > > 2016-08-11 10:05 GMT+09:00 Tony Mechelynck : >> >> On Thu, Aug 11, 2016 at 1:39 AM, manuelschiller.pimail via vim_dev >> wrote: >> > On

Re: gvim and ASCII glyphs

Hi Tony, 2016-08-11 10:05 GMT+09:00 Tony Mechelynck : > On Thu, Aug 11, 2016 at 1:39 AM, manuelschiller.pimail via vim_dev > wrote: > > On Wednesday, 10 August 2016 02:35:04 UTC+2, Tony Mechelynck wrote: > >> Manuel: > >> > >> In the past

Re: gvim and ASCII glyphs

On Thu, Aug 11, 2016 at 1:39 AM, manuelschiller.pimail via vim_dev wrote: > On Wednesday, 10 August 2016 02:35:04 UTC+2, Tony Mechelynck wrote: >> Manuel: >> >> In the past there have been "unofficial" features published as patches >> which remained outside of the

Re: gvim and ASCII glyphs

On Wednesday, 10 August 2016 02:37:38 UTC+2, Stefan Schwarzer wrote: > I recently purchased a license for PragmataPro and ran into > the same problem as Manuel. During my research I came across > his patch (many thanks, Manuel!) and I subscribed to the list > to follow the discussion on the patch

Re: gvim and ASCII glyphs

On Wednesday, 10 August 2016 02:35:04 UTC+2, Tony Mechelynck wrote: > Manuel: > > In the past there have been "unofficial" features published as patches > which remained outside of the "official" Vim repositories but publicly > available, sometimes for years, before Bram finally decided to take

Re: gvim and ASCII glyphs

I recently purchased a license for PragmataPro and ran into the same problem as Manuel. During my research I came across his patch (many thanks, Manuel!) and I subscribed to the list to follow the discussion on the patch and possibly contribute to the exchange. Here are my thoughts on the current

Re: gvim and ASCII glyphs

Manuel: In the past there have been "unofficial" features published as patches which remained outside of the "official" Vim repositories but publicly available, sometimes for years, before Bram finally decided to take them in. The +conceal and +float features, now part of mainstream Vim, are two

Re: gvim and ASCII glyphs

Hi Bram, On Tuesday, 9 August 2016 21:52:16 UTC+2, Bram Moolenaar wrote: > Manuel Schiller wrote: > > > > [...] > > > > > > > Concerning your request to send a patch that just fixes the assumption > > > > about "one ascii character == one glyph": One could either get rid of > > > > that speed

Re: gvim and ASCII glyphs

Manuel Schiller wrote: > > [...] > > > > > Concerning your request to send a patch that just fixes the assumption > > > about "one ascii character == one glyph": One could either get rid of > > > that speed optimisation code altogether (in which case all ligatures > > > will work), or rewrite

Re: gvim and ASCII glyphs

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 > : > > > Dear Kazunobu, > > If you don't mind, please consider using friendlier 'Hi' instead of 'Dear.'   >

Re: gvim and ASCII glyphs

Hi Manuel 2016-08-09 20:06 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@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. > On Tuesday, 9 August 2016 12:03:47 UTC+2,

Re: gvim and ASCII glyphs

Dear Kazunobu, On Tuesday, 9 August 2016 12:03:47 UTC+2, Kazunobu Kuriyama wrote: > Hi Manual, > > [...] > Well, the trouble is that I think you likely are qualified to review that > patch, despite me being a newcomer who cannot really tell because I don't > know who does what, and who is

Re: gvim and ASCII glyphs

Hi Manual, 2016-08-09 16:10 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > Dear Kazunobu, > > On Tuesday, 9 August 2016 07:28:43 UTC+2, Kazunobu Kuriyama wrote: > > 2016-08-09 6:35 GMT+09:00 manuelschiller.pimail via vim_dev < > vim...@googlegroups.com>: > > > > On

Re: gvim and ASCII glyphs

Dear Kazunobu, On Tuesday, 9 August 2016 07:28:43 UTC+2, Kazunobu Kuriyama wrote: > 2016-08-09 6:35 GMT+09:00 manuelschiller.pimail via vim_dev > : > > On Monday, 8 August 2016 22:27:11 UTC+2, Bram Moolenaar  wrote: > > > Manuel Schiller wrote: > > > > [...] > > > >

Re: gvim and ASCII glyphs

2016-08-09 6:35 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > On Monday, 8 August 2016 22:27:11 UTC+2, Bram Moolenaar wrote: > > Manuel Schiller wrote: > > > > [...] > > > > > Concerning your request to send a patch that just fixes the assumption > > > about "one

Re: gvim and ASCII glyphs

On Monday, 8 August 2016 22:27:11 UTC+2, Bram Moolenaar wrote: > Manuel Schiller wrote: > > [...] > > > Concerning your request to send a patch that just fixes the assumption > > about "one ascii character == one glyph": One could either get rid of > > that speed optimisation code altogether

Re: gvim and ASCII glyphs

Manuel Schiller wrote: [...] > Concerning your request to send a patch that just fixes the assumption > about "one ascii character == one glyph": One could either get rid of > that speed optimisation code altogether (in which case all ligatures > will work), or rewrite most of that

Re: gvim and ASCII glyphs

On Monday, 8 August 2016 21:27:36 UTC+2, Tony Mechelynck wrote: > On Mon, Aug 8, 2016 at 3:16 PM, manuelschiller.pimail via vim_dev > wrote: > > On Monday, 8 August 2016 14:51:01 UTC+2, Tony Mechelynck wrote: > >> Well, if you let Pango do glyph reshaping for U+0020 to

Re: gvim and ASCII glyphs

On Mon, Aug 8, 2016 at 3:16 PM, manuelschiller.pimail via vim_dev wrote: > On Monday, 8 August 2016 14:51:01 UTC+2, Tony Mechelynck wrote: >> Well, if you let Pango do glyph reshaping for U+0020 to U+007F you >> might end up with what you said you didn't want, i.e. fi

Re: gvim and ASCII glyphs

Hi Kazunobu, On Monday, 8 August 2016 18:31:40 UTC+2, Kazunobu Kuriyama wrote: > 2016-08-08 23:06 GMT+09:00 manuelschiller.pimail via vim_dev > : > > > On Monday, 8 August 2016 15:39:02 UTC+2, Kazunobu Kuriyama  wrote: > > > If your windowing system is a recent X11

Re: gvim and ASCII glyphs

2016-08-08 23:06 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > On Monday, 8 August 2016 15:39:02 UTC+2, Kazunobu Kuriyama wrote: > > If your windowing system is a recent X11 with fontconfig, do > > > > $ fc-scan > > > > > > then you'll have something human

Re: gvim and ASCII glyphs

On Monday, 8 August 2016 15:39:02 UTC+2, Kazunobu Kuriyama wrote: > If your windowing system is a recent X11 with fontconfig, do > >     $ fc-scan > > > then you'll have something human readable. > > > Take a look at an item called 'spacing.' > > > If you have none or the number zero,

Re: gvim and ASCII glyphs

On Monday, 8 August 2016 14:51:01 UTC+2, Tony Mechelynck wrote: > Well, if you let Pango do glyph reshaping for U+0020 to U+007F you > might end up with what you said you didn't want, i.e. fi fl st ffi ffl > digraphs and trigraphs, which in my experience are actually uglier (in > monospaced

Re: gvim and ASCII glyphs

Well, if you let Pango do glyph reshaping for U+0020 to U+007F you might end up with what you said you didn't want, i.e. fi fl st ffi ffl digraphs and trigraphs, which in my experience are actually uglier (in monospaced fonts) than just letting the individual letters stand side by side. Try the

Re: gvim and ASCII glyphs

On Monday, 8 August 2016 12:33:44 UTC+2, Tony Mechelynck wrote: > On Mon, Aug 8, 2016 at 11:15 AM, manuelschiller.pimail via vim_dev > wrote: > > On Monday, 8 August 2016 08:31:13 UTC+2, Kazunobu Kuriyama wrote: > >> 2016-08-07 20:27 GMT+09:00 manuelschiller.pimail via

Re: gvim and ASCII glyphs

Sorry, but I still don't understand how you justify your patch that adds 0x20 to each of alphanumeric characters and send them to Pango. Actually, what is your point to make every text data length double? That is 100% inefficient and totally ruins the existing optimization hack. Just as what

Re: gvim and ASCII glyphs

On Mon, Aug 8, 2016 at 11:15 AM, manuelschiller.pimail via vim_dev wrote: > On Monday, 8 August 2016 08:31:13 UTC+2, Kazunobu Kuriyama wrote: >> 2016-08-07 20:27 GMT+09:00 manuelschiller.pimail via vim_dev >> : >> >> >> On Monday, 19 October

Re: gvim and ASCII glyphs

2016-08-07 20:27 GMT+09:00 manuelschiller.pimail via vim_dev < vim_dev@googlegroups.com>: > On Monday, 19 October 2015 08:41:36 UTC+2, Hörmetjan Yiltiz wrote: > > On Sunday, 20 April 2014 11:55:22 UTC-4, François Gannaz wrote: > > > Hello > > > > > > In a few words, here is a patch that makes

Re: gvim and ASCII glyphs

On Sunday, 7 August 2016 15:19:48 UTC+2, Bram Moolenaar wrote: > Manu Schiller wrote: > > Please let me know if it would be possible to include this, and if > > not, at least the patch is public now where people can find it if they > > want it. > > Let's hear from a few people whether this works

Re: gvim and ASCII glyphs

Manu Schiller wrote: > On Monday, 19 October 2015 08:41:36 UTC+2, Hörmetjan Yiltiz wrote: > > On Sunday, 20 April 2014 11:55:22 UTC-4, François Gannaz wrote: > > > Hello > > > > > > In a few words, here is a patch that makes gvim work better with ligatures > > > in fonts, which can be useful

Re: gvim and ASCII glyphs

On Monday, 19 October 2015 08:41:36 UTC+2, Hörmetjan Yiltiz wrote: > On Sunday, 20 April 2014 11:55:22 UTC-4, François Gannaz wrote: > > Hello > > > > In a few words, here is a patch that makes gvim work better with ligatures > > in fonts, which can be useful even for programmers. Details

Re: gvim and ASCII glyphs

On Sunday, 20 April 2014 11:55:22 UTC-4, François Gannaz wrote: > Hello > > In a few words, here is a patch that makes gvim work better with ligatures > in fonts, which can be useful even for programmers. Details follow. > > I tried to use a Hasklig[^1], a font with ligatures intended for the >

Re: gvim and ASCII glyphs

François Gannaz wrote: In a few words, here is a patch that makes gvim work better with ligatures in fonts, which can be useful even for programmers. Details follow. I tried to use a Hasklig[^1], a font with ligatures intended for the Haskell language. It serves the same objective as the

Re: gvim and ASCII glyphs

Le 2014-04-21, Bram Moolenaar b...@moolenaar.net a écrit : Yet I wonder if the current hack with ASCII characters is really useful. Is there any performance test to check if a simpler behaviour wouldn't be suitable, at least for modern desktop installations? As the code comment mentions

gvim and ASCII glyphs

Hello In a few words, here is a patch that makes gvim work better with ligatures in fonts, which can be useful even for programmers. Details follow. I tried to use a Hasklig[^1], a font with ligatures intended for the Haskell language. It serves the same objective as the Haskell Conceal