Thank for your reply!

>>> Which GUI flavour you got can be found from somewhere near the top of
>>> the :version output: for instance, in gvim I see:

Normal version with X11-Motif GUI.  Features included (+) or not (-):

>>> the console font can only be changed by the console terminal (xterm
>>> etc.), or, for some consoles, not
at all.

In fact I can change the font only after I open gvim. I tried to set the
font in the .gvimrc but it didn't work.
I'll dig into X11-Motif GUI documentation to try to find a solution.
Thanks!

--
View this message in context:
http://vim.1045645.n5.nabble.com/set-guifont-tp5708608p5708622.html
Sent from the Vim - General mailing list archive at Nabble.com.

--
You received this message from the "vim_use" 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

On Mon, May 28, 2012 at 08:58:58AM EDT, Christian Brabandt wrote:

> Hi Chris!

[..]

> I think, you can script this. Something like this:
>
> fu! <sid>Collation(start, end, match) "{{{
>     let start = '0x'. a:start
>     let end   = '0x'. a:end
>     let patt  = '\%('
>     if (end - start) < 256
>         return a:match
>     endif
>     while (end - start) > 256
>         let temp = start + 256
>         let patt .= printf('[\%%u%X-\%%u%X]', start, temp)
>         let start = temp + 1
>         if (end - start) > 0
>             let patt .= '\|'
>         endif
>     endw
>     if (end - start) > 0
>         let patt .= printf('[\%%u%X-\%%u%X]', start, end)
>     endif
>     let patt .= '\)'
>     return patt
> endfu
>
> fu! <sid>RegCollate() "{{{
>     let cmd = getcmdline()
>     if getcmdtype() =~# '[/?:]' && cmd =~# '\[\\%u\x\+-\\%u\x\+\]'
>         let cmd = substitute(cmd,
>         \ '\[\\%u\(\x\+\)-\\%u\(\x\+\)\]',
>         \ '\=<sid>Collation(submatch(1), submatch(2), submatch(0))',
>         \ 'g')
>     endif
>     return cmd
> endfu
>
> cnoremap <f7> <c-\>e<sid>RegCollate()<cr>
>
> And then press f7 whenever you have entered a range > 256 items.

With minor adjustments, the script works as intended and splits the huge
[%\u4e00-%\u9fff] range into a very long series of [n-n+256] subranges
of code points separated by ‘\|’ alternatives.

But there is a second problem: at least in my setup, (Vim 7.2, UTF-8),
the smaller ranges no longer trigger the ‘E16 Invalid Range’ error but
they match any ASCII character.. and ironically the only thing they
don't match are the characters they are supposed to match.. here, the
ones in the %\u4e00-%\u9fff range.

That's why I initially suggested the OP use actual characters for his
ranges instead of the ‘%\u4e00’... etc. code points...

I guess the script could be modified to translate %\u4e00' and friends
into actual characters, but after digging a bit into Vim help.. I'm not
so sure.. my impression is that you'd need an external tool to do it:
Vim's printf() for instance does not support a ‘%U’ conversion type.

Thanks,

CJ

--
Have a nice day!

--
You received this message from the "vim_use" 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

Benjamin R. Haskell:

> Your example worked for me if I first cleared syntax:

In fact, it was working when the buffer's file type was not defined.

> If you want them to work for all filetypes, you'll have to do something more
> drastic.  My first thought is the following -- try putting them in an
> autocmd that runs before filetype-detection:

It will not work because the 'contained' rules require a 'contains'
counterpart.

It means one has to examine the existing highlight groups and append
custom elements to its 'contains' attribute.

What I ended up doing was:
- Create a '_global.vim' file in '~/.vim/after/syntax/'.
- Create symlinks to this file for each relevant file types.

The result is available here:
     http://bit.ly/LDBo5t

Thanks,
--
  b.d
(| |)
  ^ ^

--
You received this message from the "vim_use" 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

monax wrote:
> Hello.
>
> For example let see color theme molokai, "try/except" in green, if/
> else - red (or something close). But try/except can use "else" and I
> want to see that "else" in green color. It is possible?
>
>
If you want some help...

* what language are you using?
* show a code excerpt illustrating the problem

Regards,
Chip Campbell

--
You received this message from the "vim_use" 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

Hi all.
I have an issue using vim in the termninal.
Every time I go to Indert mode and try to sue the cursor it just
begging to write the letter A,B,C,D and creates a new line.
I have been digging and seems it is because of the internal definition
of the termcap in Vim.
So I tried the next:
set term=builtin_ansi

But then it is messing up the colors.
The term is xterm-256color by default.
Is there ane way to get the cursors working properly without changing
the termn, or using the xterm terminal?
I forgot  to say I am using latest vim 7.3.

Thanks



--
Un saludo
Best Regards
Pablo Giménez

--
You received this message from the "vim_use" 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

Ken Schmitt <Ken.Schmitt@...> wrote:

> We have recently purchased a new HP RX2800 I2 server with HP-UX 11I VERSION
> 3 operating system. I downloaded and our IT folks installed vim 7.3 (IA-64)
> from the following website:
>
>
>
> http://hpux.connect.org.uk/hppd/hpux/Editors/vim-7.3/
>
>
>
> When I run vim, I receive an error that libgtk-x11-2.0.so library file is
> not found. Clearly this file exists and is mentioned in the path, so what
> must be done to have vim operate properly with the standard HP operating
> software and libraries delivered with our system?
>
>
>
> Below is a screen capture showing the problem and I have highlighted
> relevant text in yellow:
>
>
>
> [wmsprod]@wmsr1 /home/kschmitt > setenv PATH /opt/gtk2.6/lib:$PATH
>
> [wmsprod]@wmsr1 /home/kschmitt > echo $PATH
>
>
/opt/gtk2.6/lib:/usr/bin:/home/prod/tools/bin/hpux10:/home/prod/meldisco/wmsprod\
/bin/hpux10:/home/prod/meldisco/bin/hpux10:/home/pro
>
>
d/meldisco/wmsprod/scripts:/home/prod/meldisco/scripts:/home/prod/wmscore/script\
s:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:
>
>
/opt/perl/bin:/opt/gvsd/bin:/opt/ipf/bin:/opt/nettladm/bin:/opt/fcms/bin:/opt/wb\
em/bin:/opt/wbem/sbin:/opt/sas/bin:/opt/graphics/com
>
>
mon/bin:/opt/hpvm/bin:/opt/atok/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/sec_m\
gmt/bastille/bin:/opt/caliper/bin:/opt/drd/bin:/opt/
>
>
dsau/bin:/opt/dsau/sbin:/opt/resmon/bin:/opt/firefox:/opt/perf/bin:/usr/contrib/\
kwdb/bin:/opt/perl_32/bin:/opt/perl_64/bin:/opt/prm/
>
>
bin:/opt/propplus/bin:/opt/sfm/bin:/etc/cmcluster/scripts/tkit/vtn:/opt/swm/bin:\
/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/swa/bin:/opt
>
>
/hpsmh/bin:/opt/thunderbird:/opt/sentinel/bin:/opt/langtools/bin:/opt/gwlm/bin:/\
opt/ignite/bin:/opt/omni/bin:/opt/aCC/bin:/opt/cadvi
>
>
se/bin:/opt/hpnpl//bin:/usr/local/bin:/usr/bin:/bin:/home/kschmitt:/usr/etc:/hom\
e/prod/tools/bin/hpux10:/home/prod/tools/bin/share:/
>
> etc:/usr/contrib/bin:/usr/fms_unix/com:.:.
>
> [wmsprod]@wmsr1 /home/kschmitt > vim
>
> /usr/lib/hpux32/dld.so: Unable to find library 'libgtk-x11-2.0.so'.
>
> Killed
>
> [wmsprod]@wmsr1 /home/kschmitt > cd /opt/gtk2.6/lib
>
> [wmsprod]@wmsr1 /opt/gtk2.6/lib > ll libgtk-x11-2.0.so
>
> -r-xr-xr-x   1 bin        bin        12955496 Feb  1  2006 libgtk-x11-2.0.so
>
> [wmsprod]@wmsr1 /opt/gtk2.6/lib >
>
>
>
> Thanks
>
>
>
> Ken Schmitt


It's not the PATH env variable which is used to search
for shared library, but LD_LIBRARY_PATH.

See:

http://administratosphere.wordpress.com/2007/10/19/shared-libraries-hp-ux/

You can fix with with:

$ export LD_LIBRARY_PATH=/opt/gtk2.6/lib

Or ask the administrator to add /opt/gtk2.6/lib in
/etc/dld.sl.conf

Vim-7.3 is a bit old already, you're better off
downloading the source and compiling Vim, or
else you're missing 531 patches of goodies.

Regards
-- Dominique

--
You received this message from the "vim_use" 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

I know essentially nothing about HP-UX, but at least on Linux, $PATH has
nothing to do with where shared libraries are searched for; it's the
search path for executables run as shell commands.

On Linux, there are default search locations for shared libs like /lib,
/usr/lib, and /usr/share/lib. If you want to dynamically link a library
that is in some other location, you can use the $LD_LIBRARY_PATH
variable to name those extra locations. So in your case, you might run

     LD_LIBRARY_PATH=/opt/gtk2.6/lib vim

in the shell and see if that works. I don't know if any of that is truly
Linux-specific, but chances are something similar is true on HP-UX if
it's not exactly the same.

Pablo Giménez <pablogipi@...> wrote:

> Hi all.
> I have an issue using vim in the termninal.
> Every time I go to Indert mode and try to sue the cursor it just
> begging to write the letter A,B,C,D and creates a new line.
> I have been digging and seems it is because of the internal definition
> of the termcap in Vim.
> So I tried the next:
> set term=builtin_ansi
>
> But then it is messing up the colors.
> The term is xterm-256color by default.
> Is there ane way to get the cursors working properly without changing
> the termn, or using the xterm terminal?
> I forgot  to say I am using latest vim 7.3.
>
> Thanks

Try...

    :set nocompatible

I don't remember the reason, but cursor keys only work
with nocompatible in insert mode.

-- Dominique

--
You received this message from the "vim_use" 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

Enviado desde mi iPhone

El 29 May 2012, a las 19:26, Dominique Pellé <dominique.pelle@...>
escribió:

> Pablo Giménez <pablogipi@...> wrote:
>
>> Hi all.
>> I have an issue using vim in the termninal.
>> Every time I go to Indert mode and try to sue the cursor it just
>> begging to write the letter A,B,C,D and creates a new line.
>> I have been digging and seems it is because of the internal definition
>> of the termcap in Vim.
>> So I tried the next:
>> set term=builtin_ansi
>>
>> But then it is messing up the colors.
>> The term is xterm-256color by default.
>> Is there ane way to get the cursors working properly without changing
>> the termn, or using the xterm terminal?
>> I forgot  to say I am using latest vim 7.3.
>>
>> Thanks
>
> Try...
>
>   :set nocompatible
Thanks, I have already tried it.
I think it is the third line in my vimrc
>
> I don't remember the reason, but cursor keys only work
> with nocompatible in insert mode.
>
> -- Dominique
>
> --
> You received this message from the "vim_use" 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 from the "vim_use" 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

On 2012-05-29, Pablo Giménez wrote:
> Hi all.
> I have an issue using vim in the termninal.
> Every time I go to Indert mode and try to sue the cursor it just
> begging to write the letter A,B,C,D and creates a new line.
> I have been digging and seems it is because of the internal definition
> of the termcap in Vim.
> So I tried the next:
> set term=builtin_ansi
>
> But then it is messing up the colors.
> The term is xterm-256color by default.
> Is there ane way to get the cursors working properly without changing
> the termn, or using the xterm terminal?
> I forgot  to say I am using latest vim 7.3.

The value of $TERM needs to be appropriate for the terminal you are
actually using.

Vim uses $TERM to determine the terminal's capabilities and escape
sequences from your system's terminfo or termcap database.  If the
value of $TERM is not correct, then Vim may obtain an incorrect
description of your arrow keys.

What is the terminal you are using and what is the value of $TERM?

Regards,
Gary

--
You received this message from the "vim_use" 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

Pablo Giménez Pizarro <pablogipi@...> wrote:

> Enviado desde mi iPhone
>
> El 29 May 2012, a las 19:26, Dominique Pellé <dominique.pelle@...>
escribió:
>
>> Pablo Giménez <pablogipi@...> wrote:
>>
>>> Hi all.
>>> I have an issue using vim in the termninal.
>>> Every time I go to Indert mode and try to sue the cursor it just
>>> begging to write the letter A,B,C,D and creates a new line.
>>> I have been digging and seems it is because of the internal definition
>>> of the termcap in Vim.
>>> So I tried the next:
>>> set term=builtin_ansi
>>>
>>> But then it is messing up the colors.
>>> The term is xterm-256color by default.
>>> Is there ane way to get the cursors working properly without changing
>>> the termn, or using the xterm terminal?
>>> I forgot  to say I am using latest vim 7.3.
>>>
>>> Thanks
>>
>> Try...
>>
>>   :set nocompatible
> Thanks, I have already tried it.
> I think it is the third line in my vimrc


Then what about...

:set esckeys

I can reproduce the ABCD being inserted in insert mode
when pressing cursor keys with  :set noesckeys

-- Dominique

--
You received this message from the "vim_use" 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

Enviado desde mi iPhone

El 29 May 2012, a las 20:45, Dominique Pellé <dominique.pelle@...>
escribió:

> Pablo Giménez Pizarro <pablogipi@...> wrote:
>
>> Enviado desde mi iPhone
>>
>> El 29 May 2012, a las 19:26, Dominique Pellé <dominique.pelle@...>
escribió:
>>
>>> Pablo Giménez <pablogipi@...> wrote:
>>>
>>>> Hi all.
>>>> I have an issue using vim in the termninal.
>>>> Every time I go to Indert mode and try to sue the cursor it just
>>>> begging to write the letter A,B,C,D and creates a new line.
>>>> I have been digging and seems it is because of the internal definition
>>>> of the termcap in Vim.
>>>> So I tried the next:
>>>> set term=builtin_ansi
>>>>
>>>> But then it is messing up the colors.
>>>> The term is xterm-256color by default.
>>>> Is there ane way to get the cursors working properly without changing
>>>> the termn, or using the xterm terminal?
>>>> I forgot  to say I am using latest vim 7.3.
>>>>
>>>> Thanks
>>>
>>> Try...
>>>
>>>   :set nocompatible
>> Thanks, I have already tried it.
>> I think it is the third line in my vimrc
>
>
> Then what about...
>
> :set esckeys
>
> I can reproduce the ABCD being inserted in insert mode
> when pressing cursor keys with  :set noesckeys
I haven't tried this.
I'll try, thanks Dominique
>
> -- Dominique
>
> --
> You received this message from the "vim_use" 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 from the "vim_use" 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

Enviado desde mi iPhone

El 29 May 2012, a las 20:05, Gary Johnson <garyjohn@...> escribió:

> On 2012-05-29, Pablo Giménez wrote:
>> Hi all.
>> I have an issue using vim in the termninal.
>> Every time I go to Indert mode and try to sue the cursor it just
>> begging to write the letter A,B,C,D and creates a new line.
>> I have been digging and seems it is because of the internal definition
>> of the termcap in Vim.
>> So I tried the next:
>> set term=builtin_ansi
>>
>> But then it is messing up the colors.
>> The term is xterm-256color by default.
>> Is there ane way to get the cursors working properly without changing
>> the termn, or using the xterm terminal?
>> I forgot  to say I am using latest vim 7.3.
>
> The value of $TERM needs to be appropriate for the terminal you are
> actually using.
>
> Vim uses $TERM to determine the terminal's capabilities and escape
> sequences from your system's terminfo or termcap database.  If the
> value of $TERM is not correct, then Vim may obtain an incorrect
> description of your arrow keys.
>
> What is the terminal you are using and what is the value of $TERM?
I am using gnome terminal and xterm, for both TERM is set to xterm-256color
>
> Regards,
> Gary
>
> --
> You received this message from the "vim_use" 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 from the "vim_use" 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

On 2012-05-29, Pablo Giménez Pizarro wrote:
> Enviado desde mi iPhone
>
> El 29 May 2012, a las 20:05, Gary Johnson <garyjohn@...> escribió:
>
> > On 2012-05-29, Pablo Giménez wrote:
> >> Hi all.
> >> I have an issue using vim in the termninal.
> >> Every time I go to Indert mode and try to sue the cursor it just
> >> begging to write the letter A,B,C,D and creates a new line.
> >> I have been digging and seems it is because of the internal definition
> >> of the termcap in Vim.
> >> So I tried the next:
> >> set term=builtin_ansi
> >>
> >> But then it is messing up the colors.
> >> The term is xterm-256color by default.
> >> Is there ane way to get the cursors working properly without changing
> >> the termn, or using the xterm terminal?
> >> I forgot  to say I am using latest vim 7.3.
> >
> > The value of $TERM needs to be appropriate for the terminal you are
> > actually using.
> >
> > Vim uses $TERM to determine the terminal's capabilities and escape
> > sequences from your system's terminfo or termcap database.  If the
> > value of $TERM is not correct, then Vim may obtain an incorrect
> > description of your arrow keys.
> >
> > What is the terminal you are using and what is the value of $TERM?
> I am using gnome terminal and xterm, for both TERM is set to xterm-256color

If I'm understanding you correctly, the arrow keys work in xterm but
not in GNOME Terminal.

I should have suggested this earlier:  Try starting vim like this,

     vim -N -u NONE

to see whether the behavior is due to either your ~/.vimrc or one of
your plugins.

One other thing you might try is executing

     infocmp

to see if xterm-256color is properly defined on your system.

I run Vim 7.3.524 in a GNOME Terminal 2.26.3.1 on a Fedora 11 system
daily without problems, but my TERM is set to "xterm".  I just tried
setting TERM to "xterm-256color" and the arrow keys worked fine in
both normal and insert modes.  I don't see anything in the Profile
Preferences that would change the arrow key behavior.

Regards,
Gary

--
You received this message from the "vim_use" 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

On Wed, May 30, 2012 at 03:47:16AM +1000, Ken Schmitt wrote:
>We have recently purchased a new HP RX2800 I2 server with HP-UX 11I
>VERSION 3 operating system. I downloaded and our IT folks installed vim
>7.3 (IA-64) from the following website:
>
>http://hpux.connect.org.uk/hppd/hpux/Editors/vim-7.3/

If my Linux experience is any guide, PATH doesn't have anything to do
with shared libraries.  You either need to install shared libraries in a
standard location that your OS already looks in, or configure your
dynamic linker to know about the nonstandard place where you have your
GTK libraries installed.

When I went to the website above, I saw "gtk+2" on the list of Vim's
runtime dependencies.  When I followed the link to that package, I see
that the standard HP porting package of gtk+2 installs in /usr/local,
not /opt, which is why I think your install of GTK is in a nonstandard
place.

I'd suggest getting your sysadmin to install gtk+2 from the page above,
and check that all the other runtime dependencies are installed while
they're at it.

--
Ed Blackman

--
You received this message from the "vim_use" 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

Ben,

Thanks, that is exactly the problem. I needed nnoremap. Thanks.


Ben Fritz wrote
>
>
> The tip uses inoremap, which only applies in insert mode.
>
> I assume you want to adapt the tip using nnoremap (normal mode) or
> cnoremap (command-line mode).
>
> --
> You received this message from the "vim_use" 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
>


--
View this message in context:
http://vim.1045645.n5.nabble.com/Invert-the-number-row-keys-not-in-Command-mode-\
tp5708596p5708629.html
Sent from the Vim - General mailing list archive at Nabble.com.

--
You received this message from the "vim_use" 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

On Tuesday, May 29, 2012 2:29:34 AM UTC-5, qfwfq wrote:
>
> In fact I can change the font only after I open gvim.

Yes, this is the only way :set guifont=* will ever work. Did you try that in
your .vimrc?

> I tried to set the
> font in the .gvimrc but it didn't work.

What did you try to set it to? The easy way to figure out what will work is to
first use :set guifont=*, select the desired font, then :set guifont? to see
what it actually got set to.

--
You received this message from the "vim_use" 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

On Tuesday, May 29, 2012 10:03:57 PM UTC-5, Ben Fritz wrote:
> On Tuesday, May 29, 2012 2:29:34 AM UTC-5, qfwfq wrote:
> >
> > In fact I can change the font only after I open gvim.
>
> Yes, this is the only way :set guifont=* will ever work. Did you try that in
your .vimrc?
>
> > I tried to set the
> > font in the .gvimrc but it didn't work.
>
> What did you try to set it to? The easy way to figure out what will work is to
first use :set guifont=*, select the desired font, then :set guifont? to see
what it actually got set to.

Also see http://vim.wikia.com/wiki/Setting_the_font_in_the_GUI

--
You received this message from the "vim_use" 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

I use taglist() to get a tag list. Then I did some filter, just leave
some useful one like this:

let tttlist = taglist("^List$")
let newtttlist = []
for item in tttlist
    if item['kind'] == 'i' || item['kind'] == 'c'
        call add(newtttlist, item)
    endif
endfor
echo newtttlist

But how to show them like :tag and :ptag in vim?

--
You received this message from the "vim_use" 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

qfwfq <veranda.marco@...> wrote:

>
> Thank for your reply!
>
> >>> Which GUI flavour you got can be found from somewhere near the top of
> >>> the :version output: for instance, in gvim I see:
>
> Normal version with X11-Motif GUI.  Features included (+) or not (-):
>
> >>> the console font can only be changed by the console terminal (xterm
> >>> etc.), or, for some consoles, not
> at all.
>
> In fact I can change the font only after I open gvim. I tried to set the
> font in the .gvimrc but it didn't work.
> I'll dig into X11-Motif GUI documentation to try to find a solution.
> Thanks!

Did you pick a font which is listed by "xlsfonts"?

Anyway, using the gtk2 GUI is preferable if you can.
The X11-Motif GUI does not support Unicode among other things.

Regards
-- Dominique

--
You received this message from the "vim_use" 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

I install gvimPortable in a thumb drive.
The $VIMRUNTIME is d:\Dropbox\Portable\GVimPortable\App\vim\vim73\.
I have a character encoding converter located in d:\Dropbox\Portable
\ConvertZ\ConvertZ.exe
Currently, I use :%!D:\PROGRA~1\ConvertZ\ConvertZ.exe /i:utf8 /o:big5
% to run the converter.
However, when I plug the thumb drive into another computer,
the driver letter of the thumb drive may change to another one.
How do I change the absolute path of convertz.exe to a relative path
referring to $VIMRUNTIME?

--
You received this message from the "vim_use" 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

I'm using the auto reload trick for my .vimrc:

if !exists( "autoload_vimrc" )

   let autoload_vimrc = 1
   autocmd BufWritePost .vimrc source $MYVIMRC

endif

I'd like to auto reload .vimrc when any of my configuration files are modified.

I tried adding all of the following to the if section above:

   autocmd BufWritePost .vim/after/plugin/misc.vim source ~/.vimrc
   autocmd BufWritePost .vim/after/plugin/misc.vim source $MYVIMRC
   autocmd BufWritePost misc.vim source ~/.vimrc
   autocmd BufWritePost misc.vim source $MYVIMRC

None seem to work.

My ~/.vim directory is actually a symlink to ~/projects/dot_vim/.vim, so I don't
really want to hardcode the path.  However, just to test, I even did that. 
Still no joy.

Ideally, it would be great to just say if any *.vim file in the .vim directory
is modified then reload $MYVIMRC.

Any pointers?

--
You received this message from the "vim_use" 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

Hi,

I have a file, say "test.txt", in Cygwin, which does not have
executable property.  The file property is
-rw-------+ 1 user Domain Users 16 May 30 16:04 test.txt

After I edited it with Windows native vim and saved the file, I can
see it has executable property in Cygwin. The file property now is
-rwx------+ 1 robert_bu Domain Users 16 May 30 16:10 test.txt*

Is there any way to tell Windows VIM to preserve the original file
property?

Thanks.
Robert

--
You received this message from the "vim_use" 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

On Wed, 30 May 2012, oversky wrote:

> I install gvimPortable in a thumb drive.
> The $VIMRUNTIME is d:\Dropbox\Portable\GVimPortable\App\vim\vim73\.
> I have a character encoding converter located in d:\Dropbox\Portable
> \ConvertZ\ConvertZ.exe
> Currently, I use :%!D:\PROGRA~1\ConvertZ\ConvertZ.exe /i:utf8 /o:big5
> % to run the converter.
> However, when I plug the thumb drive into another computer, the driver
> letter of the thumb drive may change to another one.
> How do I change the absolute path of convertz.exe to a relative path
> referring to $VIMRUNTIME?

You should be able to get the prefix (D:\Dropbox\Portable) by using:

let $PORTABLE = fnamemodify($VIMRUNTIME, ':h:h:h:h')

You might need to change the number of :h's.  There may also be fewer
:h's if you use $VIM instead of $VIMRUNTIME.

Then your command can become:

:%!$PORTABLE\ConvertZ\ConvertZ.exe /i:utf8 /o:big5

You may also wish to add ':8' to the modifiers, so that you get a
filename that will never have spaces in it.

See:
:help fnamemodify()
:help filename-modifiers

--
Best,
Ben

--
You received this message from the "vim_use" 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

On Wed, 30 May 2012, HarleyPig wrote:

> I'm using the auto reload trick for my .vimrc:
>
> if !exists( "autoload_vimrc" )
>
>  let autoload_vimrc = 1
>  autocmd BufWritePost .vimrc source $MYVIMRC
>
> endif

A better way to prevent doubling autocmds is to put them in a group
(better mainly because it prevents using a global variable, but it's
also more idiomatic VimL):

aug AutoloadVimrc
    au!
    au BufWritePost .vimrc source $MYVIMRC
aug END

Or just force the autocmd to be recreated (and don't worry about the
global var):

autocmd! BufWritePost .vimrc source $MYVIMRC

Personally, I prefer the group, since it lets you disable multiple
commands easily.  E.g. if you end up using multiple AutoloadVimrc
commands, you can clear them all by issuing:

:au! AutoloadVimrc


> I'd like to auto reload .vimrc when any of my configuration files are
> modified.
>
> I tried adding all of the following to the if section above:
>
>  autocmd BufWritePost .vim/after/plugin/misc.vim source ~/.vimrc
>  autocmd BufWritePost .vim/after/plugin/misc.vim source $MYVIMRC
>  autocmd BufWritePost misc.vim source ~/.vimrc
>  autocmd BufWritePost misc.vim source $MYVIMRC
>
> None seem to work.

In what way do they not work?  To verify that your .vimrc is being
reloaded, add this to your .vimrc:

echomsg 'Loaded .vimrc'

Then, when you write your .vimrc, check the messages:

:mess

With your original autocmd, writing my vimrc twice yields:

"~/.vimrc" 233L, 6448C written
Loaded .vimrc
"~/.vimrc" 233L, 6448C written
Loaded .vimrc

Also note that your plugins won't be reloaded just because you source
your ~/.vimrc.  They're autoloaded at startup.  (See :help load-plugins
for the gory details.)  From that help text, maybe you also want:

autocmd BufWritePost misc.vim runtime! plugins/**/*.vim


> My ~/.vim directory is actually a symlink to ~/projects/dot_vim/.vim,
> so I don't really want to hardcode the path.  However, just to test, I
> even did that.  Still no joy.
>
> Ideally, it would be great to just say if any *.vim file in the .vim
> directory is modified then reload $MYVIMRC.
>
> Any pointers?

Beware the dragons.  You're bound to run into some plugin or another
that doesn't cleanly apply twice.  In my experience, it's not worth the
hassle of debugging the auto-reload autocmd's.  Just find better ways to
start Vim or get it back into the state you want.

E.g.
:help :mksession
:help :mkview
:help :loadview

The way I use Vim, I find that the Ctrl-P plugin makes it fast enough to
open whatever per-project files I'm interested in, so that shutting down
Vim and restarting simply isn't much hassle.

--
Best,
Ben

--
You received this message from the "vim_use" 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

Ben Fritz wrote
>
>
> What did you try to set it to? The easy way to figure out what will work
> is to first use :set guifont=*, select the desired font, then :set
> guifont? to see what it actually got set to.
>
>

It was a mistake in how I was setting the guifont in my .gvimrc:
Now I say:

set guifont=-adobe-courier-medium-r-normal--17-120-100-100-m-100-iso8859-1

and everything works; when i :set guifont? and I get what it is supposed to
be.

Thank you.

--
View this message in context:
http://vim.1045645.n5.nabble.com/set-guifont-tp5708608p5708651.html
Sent from the Vim - General mailing list archive at Nabble.com.

--
You received this message from the "vim_use" 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

2012/5/29 Gary Johnson <garyjohn@...>:
> On 2012-05-29, Pablo Giménez Pizarro wrote:
>> Enviado desde mi iPhone
>>
>> El 29 May 2012, a las 20:05, Gary Johnson <garyjohn@...> escribió:
>>
>> > On 2012-05-29, Pablo Giménez wrote:
>> >> Hi all.
>> >> I have an issue using vim in the termninal.
>> >> Every time I go to Indert mode and try to sue the cursor it just
>> >> begging to write the letter A,B,C,D and creates a new line.
>> >> I have been digging and seems it is because of the internal definition
>> >> of the termcap in Vim.
>> >> So I tried the next:
>> >> set term=builtin_ansi
>> >>
>> >> But then it is messing up the colors.
>> >> The term is xterm-256color by default.
>> >> Is there ane way to get the cursors working properly without changing
>> >> the termn, or using the xterm terminal?
>> >> I forgot  to say I am using latest vim 7.3.
>> >
>> > The value of $TERM needs to be appropriate for the terminal you are
>> > actually using.
>> >
>> > Vim uses $TERM to determine the terminal's capabilities and escape
>> > sequences from your system's terminfo or termcap database.  If the
>> > value of $TERM is not correct, then Vim may obtain an incorrect
>> > description of your arrow keys.
>> >
>> > What is the terminal you are using and what is the value of $TERM?
>> I am using gnome terminal and xterm, for both TERM is set to xterm-256color
>
> If I'm understanding you correctly, the arrow keys work in xterm but
> not in GNOME Terminal.
Nop it doesnt work in any terminal, xterm or gnome-terminal.
I also have mrxvt, but same problem.
>
> I should have suggested this earlier:  Try starting vim like this,
>
>    vim -N -u NONE
This is interesting to try.
Thanks.
Let you know guys hos it goes.
Thanks for the advice.
>
> to see whether the behavior is due to either your ~/.vimrc or one of
> your plugins.
>
> One other thing you might try is executing
>
>    infocmp
>
> to see if xterm-256color is properly defined on your system.
>
> I run Vim 7.3.524 in a GNOME Terminal 2.26.3.1 on a Fedora 11 system
> daily without problems, but my TERM is set to "xterm".  I just tried
> setting TERM to "xterm-256color" and the arrow keys worked fine in
> both normal and insert modes.  I don't see anything in the Profile
> Preferences that would change the arrow key behavior.
>
> Regards,
> Gary
>
> --
> You received this message from the "vim_use" 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



--
Un saludo
Best Regards
Pablo Giménez

--
You received this message from the "vim_use" 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

Ja I got where is the problem.
I have these keymaps for the completion popmenu:
     inoremap <expr> <Esc>      pumvisible() ? "\<C-e>" : "\<Esc>"
     inoremap <expr> <CR>       pumvisible() ? "\<C-y>" : "\<CR>"
     inoremap <expr> <Down>     pumvisible() ? "\<C-n>" : "\<Down>"
     inoremap <expr> <Up>       pumvisible() ? "\<C-p>" : "\<Up>"
     inoremap <expr> <PageDown> pumvisible() ?
"\<PageDown>\<C-p>\<C-n>" : "\<PageDown>"
     inoremap <expr> <PageUp>   pumvisible() ? "\<PageUp>\<C-p>\<C-n>"
: "\<PageUp>"

I got them from the vim wiki, so I am not sure why they are breaking
my cursors when working from a terminal.
It is supposed that if pop menu is not visible they just return the
same key isnt it?


2012/5/30 Pablo Giménez <pablogipi@...>:
> 2012/5/29 Gary Johnson <garyjohn@...>:
>> On 2012-05-29, Pablo Giménez Pizarro wrote:
>>> Enviado desde mi iPhone
>>>
>>> El 29 May 2012, a las 20:05, Gary Johnson <garyjohn@...> escribió:
>>>
>>> > On 2012-05-29, Pablo Giménez wrote:
>>> >> Hi all.
>>> >> I have an issue using vim in the termninal.
>>> >> Every time I go to Indert mode and try to sue the cursor it just
>>> >> begging to write the letter A,B,C,D and creates a new line.
>>> >> I have been digging and seems it is because of the internal definition
>>> >> of the termcap in Vim.
>>> >> So I tried the next:
>>> >> set term=builtin_ansi
>>> >>
>>> >> But then it is messing up the colors.
>>> >> The term is xterm-256color by default.
>>> >> Is there ane way to get the cursors working properly without changing
>>> >> the termn, or using the xterm terminal?
>>> >> I forgot  to say I am using latest vim 7.3.
>>> >
>>> > The value of $TERM needs to be appropriate for the terminal you are
>>> > actually using.
>>> >
>>> > Vim uses $TERM to determine the terminal's capabilities and escape
>>> > sequences from your system's terminfo or termcap database.  If the
>>> > value of $TERM is not correct, then Vim may obtain an incorrect
>>> > description of your arrow keys.
>>> >
>>> > What is the terminal you are using and what is the value of $TERM?
>>> I am using gnome terminal and xterm, for both TERM is set to xterm-256color
>>
>> If I'm understanding you correctly, the arrow keys work in xterm but
>> not in GNOME Terminal.
> Nop it doesnt work in any terminal, xterm or gnome-terminal.
> I also have mrxvt, but same problem.
>>
>> I should have suggested this earlier:  Try starting vim like this,
>>
>>    vim -N -u NONE
> This is interesting to try.
> Thanks.
> Let you know guys hos it goes.
> Thanks for the advice.
>>
>> to see whether the behavior is due to either your ~/.vimrc or one of
>> your plugins.
>>
>> One other thing you might try is executing
>>
>>    infocmp
>>
>> to see if xterm-256color is properly defined on your system.
>>
>> I run Vim 7.3.524 in a GNOME Terminal 2.26.3.1 on a Fedora 11 system
>> daily without problems, but my TERM is set to "xterm".  I just tried
>> setting TERM to "xterm-256color" and the arrow keys worked fine in
>> both normal and insert modes.  I don't see anything in the Profile
>> Preferences that would change the arrow key behavior.
>>
>> Regards,
>> Gary
>>
>> --
>> You received this message from the "vim_use" 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
>
>
>
> --
> Un saludo
> Best Regards
> Pablo Giménez



--
Un saludo
Best Regards
Pablo Giménez

--
You received this message from the "vim_use" 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

On Wed, May 30, 2012 16:19, oversky wrote:
> I still have problem.
> I check with :echo $PORTABLE,
> it shows correct path.
> But the error message still says it can't find the file.
> Then I use :! instead of :%!,
> the command paste to shell is
>
> C:\WINDOWS\system32\cmd.exe /c $PORTABLE\ConvertZ\ConvertZ.exe /
> i:sjis /o:utf8 1.cue
>
> $PORTABLE is not replaced by its value.
> Any suggestion?

:h expand()

regards,
Christian

--
You received this message from the "vim_use" 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