Hello,
I noticed the Cursor and CursorIM color is not displayed correctly in
VIM 7.2a.
VIM 7.1.xxx (Last xxx was 330) worked as expected.
For the VIM 7.2a;
1. run gvim - 'Cursor' color
2. type 'i' - 'Cursor' color
3. type imak (s-space) - 'CursorIM' color
I can
On Mon, Jun 30, 2008 at 23:17, Christian MICHON
[EMAIL PROTECTED] wrote:
web based format, close to useless unless I write a clever awk script
after I individually download each page individually.
wget comes to mind. I am sure you will find a script to do what you
want. Wanting web archives
##
http:\\lakshmiraiprofile.blogspot.com
##
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
On Tue, Jul 1, 2008 at 12:21 PM, Richard Hartmann
[EMAIL PROTECTED] wrote:
wget comes to mind. I am sure you will find a script to do what you
want. Wanting web archives in a sane format is not too uncommon,
after all.
thanks for suggesting it. as I mentioned, it would have been the last
On Mon, Jun 30, 2008 at 11:39 PM, James Vega [EMAIL PROTECTED] wrote:
One feedback: we should try to keep the patch numbers from Bram in the
shortlog, shouldn't we ?
*shrug* I went back and forth on that and ended up leaving it as is
since that's the way I started.
I managed to find a neat
I've wrote compiler file for Lua: http://wit.edu.pl/~husiatyn/lua.vim
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Hi,
When running 7.2a in an xterm under Cygwin, the color capabilities
of the xterm are not used. Rather, vim uses only standard terminal
capabilities like underline, bold, etc.
This doesn't happen with vim 7.1. Running vim 7.1 in an xterm under
Cygwin shows all colors the xterm is capable
Hi,
Corinna Vinschen wrote:
Hi,
When running 7.2a in an xterm under Cygwin, the color capabilities
of the xterm are not used. Rather, vim uses only standard terminal
capabilities like underline, bold, etc.
This doesn't happen with vim 7.1. Running vim 7.1 in an xterm under
Cygwin
Hi,
Jürgen Krämer wrote:
Corinna Vinschen wrote:
Hi,
When running 7.2a in an xterm under Cygwin, the color capabilities
of the xterm are not used. Rather, vim uses only standard terminal
capabilities like underline, bold, etc.
This doesn't happen with vim 7.1. Running vim 7.1 in an
On Jul 1 16:37, Marc Haisenko wrote:
On Tuesday 01 July 2008, Corinna Vinschen wrote:
Hi,
When running 7.2a in an xterm under Cygwin, the color capabilities
of the xterm are not used. Rather, vim uses only standard terminal
capabilities like underline, bold, etc.
This doesn't
On Tuesday 01 July 2008, Corinna Vinschen wrote:
xterm has color capabilities for ages and the terminfo xterm entry
contains this information.
Yes, but in a lot of places it is still assumed that xterm means monochrome.
For example, try OpenSolaris: if TERM=xterm you'll get a monochrome vim.
On 2008-07-01, Marc Haisenko [EMAIL PROTECTED] wrote:
On Tuesday 01 July 2008, Corinna Vinschen wrote:
xterm has color capabilities for ages and the terminfo xterm entry
contains this information.
Yes, but in a lot of places it is still assumed that xterm means
monochrome.
For
I found a ruby command's bug on Windows VIM.
:ruby require 'open-uri'
:ruby open('http://google.com/')
= SocketError: `initialize': getaddrinfo: non-recoverable failure in
name resolution.
:ruby open('http://66.249.89.147')
= vim dies
In Windows, NtInitialize() should called when
Ingo Karkat wrote:
Hello VIM developers,
I found a small bug in :pedit when one wants to clone the current
buffer to the preview window _and_ there is a :autocmd for the
'BufReadPre' event; in that case, the cursor jumps to the first line
of the original window instead of remaining at
SungHyun Nam wrote:
I noticed the Cursor and CursorIM color is not displayed correctly in
VIM 7.2a.
VIM 7.1.xxx (Last xxx was 330) worked as expected.
For the VIM 7.2a;
1. run gvim - 'Cursor' color
2. type 'i' - 'Cursor' color
3. type imak (s-space) - 'CursorIM' color
Dominique Pelle wrote:
Attached patch fixes incorrect cell computation
introduced my previous patch fix2-invalid-utf8-seq.patch
while still correcting the original bug (read overflow).
I tested it, but please review it.
I'm not too pleased about the hard-coded 4 cells
for illegal
Christian Michon wrote:
On Mon, Jun 30, 2008 at 11:13 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
See http://vim.sourceforge.net/maillist.php#vim-dev under Archive. I
don't know under what format the archives are held.
web based format, close to useless unless I write a clever awk
Patch 7.2a.011
Problem:The Edit/Startup Settings menu doesn't work.
Solution: Expand environment variables. (Ben Schmidt)
Files: runtime/menu.vim
*** ../vim-7.2a.010/runtime/menu.vimWed Jun 25 21:51:59 2008
--- runtime/menu.vimMon Jun 30 22:54:27 2008
***
*** 2,8
On 01-Jul-08 21:34, Bram Moolenaar wrote:
Ingo Karkat wrote:
Hello VIM developers,
I found a small bug in :pedit when one wants to clone the current
buffer to the preview window _and_ there is a :autocmd for the
'BufReadPre' event; in that case, the cursor jumps to the first line
of
Bram Moolenaar wrote:
SungHyun Nam wrote:
I noticed the Cursor and CursorIM color is not displayed correctly in
VIM 7.2a.
VIM 7.1.xxx (Last xxx was 330) worked as expected.
For the VIM 7.2a;
1. run gvim - 'Cursor' color
2. type 'i' - 'Cursor' color
3. type imak (s-space) -
On 02/07/08 02:26, Jan Minář wrote:
Looks like this didn't go through, so here it is again:
[...]
The updated tarplugin attack is rather simple:
$ rm -rf ./*
$ touch foo%;eval eval \`echo 0:64617465203e2070776e6564 |
xxd -r\`;'bar.tar
$ vim +:q ./foo*
$ ls
SungHyun Nam, more question.
what $LANG?
what $GTK_IM_MODULE?
what $XMODIFIERS
Thanks.
On Wed, Jul 2, 2008 at 10:28 AM, SungHyun Nam [EMAIL PROTECTED] wrote:
mattn wrote:
Hmm, it seems that current code was broken for japanese also.
I'll look into it later.
SungHyun Nam, What IM do you
Hello,
My settings are:
---
$ echo $LANG
$ echo $GTK_IM_MODULE
hangul2
$ echo $XMODIFIERS
$
I think LANG does not affect cygwin. Instead windows's current
codepage(?) affects cygwin. I use Korean version of windows which
use CP949 codepage. Unix(or Linux)
Hi Bram,
I just compiled a minimal Vim as an experiment. Here are my configure
settings (most of them are probably redundant):
export CONF_OPT_X='--without-x'
export CONF_OPT_GUI='--disable-gui'
export CONF_OPT_FEAT='--with-features=tiny'
export CONF_OPT_PERL='--disable-perlinterp'
export
On 02/07/08 06:23, SungHyun Nam wrote:
Hello,
My settings are:
---
$ echo $LANG
$ echo $GTK_IM_MODULE
hangul2
$ echo $XMODIFIERS
$
I think LANG does not affect cygwin. Instead windows's current
codepage(?) affects cygwin. I use Korean version of
25 matches
Mail list logo
