Re: conflicts with in windows console vim (vim.exe), bug ?

2016-10-09 Fir de Conversatie skywind3000 
Marius Gedminas wrote：
> > After downloading msys2 and installing gcc, ncurses-devel ... with pacman,
> > I started to build latest vim inside msys2, and found these:
> > 
> > checking for tgetent in -ltinfo... (cached) no
> > checking for tgetent in -lncurses... (cached) yes
> > ncurses library is not usable
> 
> You need to figure out why that is (check config.log for clues).
> 
> Alternatively, install Git for Windows and you get a nice set of tools
> that include bash, vim and a better console (mintty).
> 
> The vim might be a bit feature-limited, though, so I understand your
> desire to build something newer.

I can manage to build vim in the msys2 now by clone a refresh vim repository. 
thank you very much, msys2 + vim is right what I need

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

Re: conflicts with in windows console vim (vim.exe), bug ?

2016-09-23 Fir de Conversatie Marius Gedminas 
On Fri, Sep 23, 2016 at 12:41:56AM -0700, skywind3000 wrote:
> Magnus Woldrich：
> > >Thanks, very disappointted with cmd.exe
> > 
> > Here you go: https://msys2.github.io/
> 
> After downloading msys2 and installing gcc, ncurses-devel ... with pacman,
> I started to build latest vim inside msys2, and found these:
> 
> checking for tgetent in -ltinfo... (cached) no
> checking for tgetent in -lncurses... (cached) yes
> ncurses library is not usable

You need to figure out why that is (check config.log for clues).

Alternatively, install Git for Windows and you get a nice set of tools
that include bash, vim and a better console (mintty).

The vim might be a bit feature-limited, though, so I understand your
desire to build something newer.

Marius Gedminas
-- 
Never trust an operating system you don't have sources for.

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


signature.asc
Description: PGP signature

Re: conflicts with in windows console vim (vim.exe), bug ?

2016-09-23 Fir de Conversatie skywind3000 
Magnus Woldrich：
> >Thanks, very disappointted with cmd.exe
> 
> Here you go: https://msys2.github.io/

After downloading msys2 and installing gcc, ncurses-devel ... with pacman,
I started to build latest vim inside msys2, and found these:

checking for tgetent in -ltinfo... (cached) no
checking for tgetent in -lncurses... (cached) yes
ncurses library is not usable
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lcurses... no
no terminal library found
checking for tgetent()... configure: error: NOT FOUND!
  You need to install a terminal library; for example ncurses.
  Or specify the name of the library with --with-tlib.


msys2 is a wonderful console, but latest vim can't be build in it , 
do you know what's wrong ?

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

Re: conflicts with in windows console vim (vim.exe), bug ?

2016-09-22 Fir de Conversatie Magnus Woldrich 

Thanks, very disappointted with cmd.exe


Here you go: https://msys2.github.io/

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

Re: conflicts with in windows console vim (vim.exe), bug ?

2016-09-22 Fir de Conversatie skywind3000 
Marvin Renich wrote：
> * skywind3000  [160921 14:18]:
> >  has been mapped to something in my vimrc, which works fine in
> > win32-gvim/macvim and linux/mac terminal vim (with backspace set to
> > 127/ctrl-? )
> > 
> > but in windows console vim, mapping  will cause  unable to
> > work properly (it appears that backspace also get mapped),
> > 
> > After reading a lot of docs, I still can't figure out how to fix it .
> > 
> > Is that a bug ? or something misconfiguration ?
> > 
> > Can console  behave exactly in the same way like other platforms ?
> 
> , the ASCII character, is exactly Ctrl-h.  , the keyboard key,
> in a terminal emulator (windows console, i.e. cmd.exe, is a terminal
> emulator) sends to the program whatever the terminal emulator decides,
> which is usually , but sometimes  (the ASCII character).
> 
> Many terminal emulators allow you to configure this to some degree.
> Most terminal emulators use VT102 or VT220 key codes and escape
> sequences by default.  If you can configure the terminal emulator to
> send your own escape sequence, you can set the t_kb option to recognize
> it.  I am pretty sure that Vim will treat this escape sequence
> separately from Ctrl-h in mappings.
> 
> I don't know if you can get cmd.exe to send anything other than an ASCII
>  character.
> 
> ...Marvin

Thanks, very disappointted with cmd.exe

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

Re: conflicts with in windows console vim (vim.exe), bug ?

2016-09-21 Fir de Conversatie Marvin Renich 
* skywind3000  [160921 14:18]:
>  has been mapped to something in my vimrc, which works fine in
> win32-gvim/macvim and linux/mac terminal vim (with backspace set to
> 127/ctrl-? )
> 
> but in windows console vim, mapping  will cause  unable to
> work properly (it appears that backspace also get mapped),
> 
> After reading a lot of docs, I still can't figure out how to fix it .
> 
> Is that a bug ? or something misconfiguration ?
> 
> Can console  behave exactly in the same way like other platforms ?

, the ASCII character, is exactly Ctrl-h.  , the keyboard key,
in a terminal emulator (windows console, i.e. cmd.exe, is a terminal
emulator) sends to the program whatever the terminal emulator decides,
which is usually , but sometimes  (the ASCII character).

Many terminal emulators allow you to configure this to some degree.
Most terminal emulators use VT102 or VT220 key codes and escape
sequences by default.  If you can configure the terminal emulator to
send your own escape sequence, you can set the t_kb option to recognize
it.  I am pretty sure that Vim will treat this escape sequence
separately from Ctrl-h in mappings.

I don't know if you can get cmd.exe to send anything other than an ASCII
 character.

...Marvin

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

conflicts with in windows console vim (vim.exe), bug ?

2016-09-21 Fir de Conversatie skywind3000 
 has been mapped to something in my vimrc, 
which works fine in win32-gvim/macvim and linux/mac terminal vim (with 
backspace set to 127/ctrl-? )

but in windows console vim, mapping  will cause  unable to work 
properly (it appears that backspace also get mapped),

After reading a lot of docs, I still can't figure out how to fix it .

Is that a bug ? or something misconfiguration ?

Can console  behave exactly in the same way like other platforms ?

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