elastic tabstops and gvim's GTK text widget
Hi all, I am the creator of a mechanism called elastic tabstops (see nickgravgaard.com/elastictabstops/). Right now, my plan is to try and implement this in as many text widgets as possible so that the editors that use them will be able to easily add this as a feature. Since vim (well, gvim really) is my editor of choice I thought I'd start with that. Could someone tell me which GTK widget gvim uses and what problems they think I might encounter? Any other comments are also welcome. Thanks, Nick
insert-mode :map-alt-keys and 8-bit locales
There is bug in vim... According to :help :map-alt-keys : By default Vim assumes that pressing the ALT key sets the 8th bit of a typed character. This is wrong for 8-bit non-ascii locales. Example: :imap M-i something maps CYRILLIC CAPITAL I (in KOI8-R locale) instead of Alt-I. Also, vim suggests to set convert-meta to on in inputrc which is also wrong for 8-bit non-ascii locales. Finally, typing C-VM-i in insert mode gives me the same CYRILLIC CAPITAL I... I think there should be option for Meta handling... -- Regards, Sir Raorn. signature.asc Description: Digital signature
Re: elastic tabstops and gvim's GTK text widget
Hello, Do you intend to make Elastic Tabs available in a console vim as well? regards, Peter --- Nick Gravgaard [EMAIL PROTECTED] wrote: Hi all, I am the creator of a mechanism called elastic tabstops (see nickgravgaard.com/elastictabstops/). Right now, my plan is to try and implement this in as many text widgets as possible so that the editors that use them will be able to easily add this as a feature. Since vim (well, gvim really) is my editor of choice I thought I'd start with that. Could someone tell me which GTK widget gvim uses and what problems they think I might encounter? Any other comments are also welcome. Thanks, Nick On Yahoo!7 Fuel Price Watch: Find the cheapest petrol in your area http://au.maps.yahoo.com/fuelwatch/
Re: elastic tabstops and gvim's GTK text widget
I don't think so - just the GTK version. One of the advantages of the elastic tabstop system is that proportional fonts can be used without breaking vertical alignment, and obviously this advantage is invalid in a monospaced console. I'm not fussed about proportional fonts, I'm interested in not having to manually add and remove whitespace. But I only run OS X and Windows GUIs anyway. regards, Peter Do you Yahoo!? Yahoo!7 Time Capsule - Make your mark and be a part of history http://www.yahoo7.com.au/timecapsule
Re: elastic tabstops and gvim's GTK text widget
--- Nick Gravgaard [EMAIL PROTECTED] wrote: On 20/10/06, Peter Hodge [EMAIL PROTECTED] wrote: I don't think so - just the GTK version. One of the advantages of the elastic tabstop system is that proportional fonts can be used without breaking vertical alignment, and obviously this advantage is invalid in a monospaced console. I'm not fussed about proportional fonts, I'm interested in not having to manually add and remove whitespace. But I only run OS X and Windows GUIs anyway. Yeah well the proportional fonts thing is only a side benefit. There are other more important advantages such as the one you mention. Do you know if gvim uses a standard GTK text widget? I have absolutely no idea, sorry. If you download the Vim source, you should find everything GTK-related in these files: gui_gtk.c gui_gtk_f.c gui_gtk_f.h gui_gtk_vms.h gui_gtk_x11.c If no one else on this list can help you, then Bram ([EMAIL PROTECTED]) is the person to ask. regards, Peter On Yahoo!7 Photos: Unlimited free storage keep all your photos in one place! http://au.photos.yahoo.com
the plugin startup check
Almost every plugin begins with this check: if exists(g:plugin_name) | finish | endif let g:plugin_name = 1 I understand this tries to save time if vim tries to load plugins 2nd time. But aren't plugins loaded only at vim startup ? Does vim *ever* ever try to load plugins 2nd time ? In which situation can vim load plugin 2nd time (except for some manual command) ? Yakov
Re: the plugin startup check
I think it is because you may have a copy of the plugin in $VIMRUNTIME as well as in your .vim folder. In this way, your .vim copy is sourced first (well, according to 'rtp'), sets the g:plugin_name variable and when the $VIMRUNTIME plugins are sourced, and it sees the variable and prevents loading that copy of the plugin also. regards, Peter --- Yakov Lerner [EMAIL PROTECTED] wrote: Almost every plugin begins with this check: if exists(g:plugin_name) | finish | endif let g:plugin_name = 1 I understand this tries to save time if vim tries to load plugins 2nd time. But aren't plugins loaded only at vim startup ? Does vim *ever* ever try to load plugins 2nd time ? In which situation can vim load plugin 2nd time (except for some manual command) ? Yakov Do you Yahoo!? Yahoo!7 Time Capsule - Make your mark and be a part of history http://www.yahoo7.com.au/timecapsule
Re: the plugin startup check
On 10/20/06, Peter Hodge [EMAIL PROTECTED] wrote: --- Yakov Lerner [EMAIL PROTECTED] wrote: Almost every plugin begins with this check: if exists(g:plugin_name) | finish | endif let g:plugin_name = 1 I understand this tries to save time if vim tries to load plugins 2nd time. But aren't plugins loaded only at vim startup ? Does vim *ever* ever try to load plugins 2nd time ? In which situation can vim load plugin 2nd time (except for some manual command) ? Yakov I think it is because you may have a copy of the plugin in $VIMRUNTIME as well as in your .vim folder. In this way, your .vim copy is sourced first (well, according to 'rtp'), sets the g:plugin_name variable and when the $VIMRUNTIME plugins are sourced, and it sees the variable and prevents loading that copy of the plugin also. Ok, I found the description in usr_41.txt, at NOT LOADING. Thanks Yakov
Re: insert-mode :map-alt-keys and 8-bit locales
Alexey I. Froloff wrote: There is bug in vim... According to :help :map-alt-keys : By default Vim assumes that pressing the ALT key sets the 8th bit of a typed character. This is wrong for 8-bit non-ascii locales. Example: :imap M-i something maps CYRILLIC CAPITAL I (in KOI8-R locale) instead of Alt-I. Also, vim suggests to set convert-meta to on in inputrc which is also wrong for 8-bit non-ascii locales. Finally, typing C-VM-i in insert mode gives me the same CYRILLIC CAPITAL I... I think there should be option for Meta handling... This just means that Vim cannot distinguish between a CYRILLIC CAPITAL I sent by your keyboard because you hit the И key, or the same bit-pattern sent by your keyboard because you hit the Alt and I keys together. There's nothing Vim can do about it, all it sees is все еще то же самое... Best regards, Tony.
