Hi,
2014/1/11 Sat 0:24:26 UTC+9 Ken Takata wrote:
> This issue can be fixed by mattn's following patch:
> https://groups.google.com/d/topic/vim_dev/eEBXYLz0NHI/discussion
>
> The patch is already listed in the todo.txt:
> > Win32: use different args for SearchPath()? (Yasuhiro Matsumoto, 2009 Jan
2014年1月7日火曜日 14時21分26秒 UTC+9 Bram Moolenaar:
> Shougo Matsu wrote:
>
>
>
> > Sorry, I get it. I fixed the description.
>
>
>
> Thanks!
>
>
>
> --
>
> hundred-and-one symptoms of being an internet addict:
>
> 117. You are more comfortable typing in html.
>
>
>
> /// Bram Moolenaar --
Christian Brabandt wrote:
> On Fr, 10 Jan 2014, Bram Moolenaar wrote:
>
> > Christian Brabandt wrote:
> >
> > > On Di, 07 Jan 2014, Matteo Cavalleri wrote:
> > >
> > > > some easy steps to reproduce the problem:
> > > >
> > > > :set t_Co?
> > > > t_Co=256
> > > > :set background?
> > > > back
Matteo Cavalleri wrote:
> > To see if this is right we would need to make areas with the background
> > color, put some white and black text in it, and check which text is best
> > readable.
>
> the formula I choosen should calculate the "perceptual" brightness,
> i.e. it should take into accoun
Using gvim 7.4.141 (Huge) for GTK2/GNOME2, changeset 2ca470c6096e
g:loaded_netrw == g:loaded_netrwPlugin == 'v149'
$VIMRUNTIME/plugin/gzip.vim dated 2010 Mar 10
While viewing
ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-central-trunk-linux64/1389382240/
hit with the
^^^
--
--
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 u
On Fr, 10 Jan 2014, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > On Di, 07 Jan 2014, Matteo Cavalleri wrote:
> >
> > > some easy steps to reproduce the problem:
> > >
> > > :set t_Co?
> > > t_Co=256
> > > :set background?
> > > background=light
> > > :set background=dark
> > > :set
On 2014-01-10, Lech Lorens wrote:
> On 10 January 2014 20:16, Gary Johnson wrote:
> > On 2014-01-10, Bram Moolenaar wrote:
> >> Patch 7.4.138 (after 7.4.114)
> >> Problem:Directory change messages are not recognized.
> >> Solution: Fix using a character range literally. (Lech Lorens)
> >> Fi
On 10 January 2014 20:16, Gary Johnson wrote:
> On 2014-01-10, Bram Moolenaar wrote:
>> Patch 7.4.138 (after 7.4.114)
>> Problem:Directory change messages are not recognized.
>> Solution: Fix using a character range literally. (Lech Lorens)
>> Files:src/option.h
>
> It looks to m
On 2014-01-10, Bram Moolenaar wrote:
> Patch 7.4.138 (after 7.4.114)
> Problem:Directory change messages are not recognized.
> Solution: Fix using a character range literally. (Lech Lorens)
> Files:src/option.h
It looks to me that this fix does not use a character range but
allow
ZyX, I'm sorry for late reply.
2013/12/15 22:10、Nikolay Pavlov ：
> You meant there that sequence should be ESC [ 48 : 2 : R : G : B?
Yes, I certainly feel xterm's colon separated style (ESC [ 48 : 2 : R : G : B
m) is better than konsole-style (ESC [ 48 ; 2 ; R ; G ; B m).
But I think the best
Patch 7.4.141
Problem:Problems when building with Borland: st_mode is signed short;
can't build with Python; temp files not ignored by Mercurial;
building with DEBUG doesn't define _DEBUG.
Solution: Fix the problems. (Ken Takata)
Files: src/Make_bc5.mak, src/if_p
>
> To see if this is right we would need to make areas with the background
>
> color, put some white and black text in it, and check which text is best
>
> readable.
>
the formula I choosen should calculate the "perceptual" brightness, i.e. it
should take into account human perception and als
Matteo Cavalleri wrote:
> ok, i took the rgb values from that image of the xterm colors (using
> the gist linked in the image itself) and wrote a little ruby script to
> print 1 or 0 depending on the brightness of the color.
>
> according to the source snippet posted by Christian, it seems that
Patch 7.4.140
Problem:Crash when wiping out buffer triggers autocommand that wipes out
only other buffer.
Solution: Do not delete the last buffer, make it empty. (Hirohito Higashi)
Files: src/buffer.c
*** ../vim-7.4.139/src/buffer.c 2013-11-06 05:26:08.0 +0100
---
Hi,
executable() returns a wrong result when an executable is placed at
C:\Windows\System32 and it isn't listed in the PATH environment.
E.g.:
C:\>set PATH=
" Clear the PATH environment.
C:\>cmd
'cmd' is not recognized as an internal or external command,
operable program or batch file.
C:\>\path
Patch 7.4.139
Problem:Crash when using :cd in autocommand. (François Ingelrest)
Solution: Set w_localdir to NULL after freeing it. (Dominique Pelle)
Files: src/ex_docmd.c, src/window.c
*** ../vim-7.4.138/src/ex_docmd.c 2013-12-14 13:06:13.0 +0100
--- src/ex_docmd.c
Patch 7.4.138 (after 7.4.114)
Problem:Directory change messages are not recognized.
Solution: Fix using a character range literally. (Lech Lorens)
Files: src/option.h
*** ../vim-7.4.137/src/option.h 2013-12-11 12:22:54.0 +0100
--- src/option.h2014-01-10 15:17:09.00
ok, i took the rgb values from that image of the xterm colors (using the gist
linked in the image itself) and wrote a little ruby script to print 1 or 0
depending on the brightness of the color.
according to the source snippet posted by Christian, it seems that when "i" is
true then the backgro
I contacted Chip Campbell (the maintainer) via email and he's fixed the issue,
so this bug is now patched. No more action is required.
--
--
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 ht
Nobuhiro Takasaki
https://groups.google.com/d/msg/vim_dev/JhtPJhOdTKo/uYxX7TzTSK8J
--
--
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 thi
Yasuhiro Matsumoto wrote:
> I'm not an author of this patch.
Who should I list then?
--
Why is it called "Windows"? "Gates" would be more appropriate...
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org
Lcd wrote:
> A number of functions are documented in eval.txt, but missing from
> function-list in usr_41.txt. Patch below.
Thanks!
--
All true wisdom is found on T-shirts.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for featu
I'm not an author of this patch.
--
--
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
Yasuhiro Matsumoto wrote:
> https://gist.github.com/mattn/8312677
Thanks. I'll include it. If someone spots a problem with this patch,
please let us know.
--
hundred-and-one symptoms of being an internet addict:
130. You can't get out of your desk even if it's time to eat or time
to go
Patch 7.4.137
Problem:Cannot use IME with Windows 8 console.
Solution: Change the user of ReadConsoleInput() and PeekConsoleInput().
(Yasuhiro Matsumoto)
Files: src/os_win32.c
*** ../vim-7.4.136/src/os_win32.c 2014-01-10 13:05:12.0 +0100
--- src/os_win32.c
Cade Foster wrote:
> Use ";" as comment character to *.reg files.
Thanks. Looks like I can include this without causing trouble for anyone.
--
You cannot have a baby in one month by getting nine women pregnant.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///
Patch 7.4.136 (after 7.4.096)
Problem:MS-Windows: When saving a file with a UNC path the file becomes
read-only.
Solution: Don't mix up Win32 attributes and Unix attributes. (Ken Takata)
Files: src/os_mswin.c, src/os_win32.c
*** ../vim-7.4.135/src/os_mswin.c 2013-09-
Ken Takata wrote:
> After the patch 7.4.096, when edit and save a file on a UNC path, the file
> becomes unexpectedly readonly. mch_getperm() should return permissions in
> a unix style like 0644 or 0777, but it returns Win32 attributes for a UNC
> path after 7.4.096. vim_stat() should have bee
Christian Brabandt wrote:
> On Di, 07 Jan 2014, Matteo Cavalleri wrote:
>
> > some easy steps to reproduce the problem:
> >
> > :set t_Co?
> > t_Co=256
> > :set background?
> > background=light
> > :set background=dark
> > :set background?
> > background=dark
> > :hi Normal ctermfg=grey ctermbg
See image (also attached): http://i.imgur.com/wdC6vUK.png
I've reproduced this in OSX and Red Hat, on terminal vim versions 7.2, 7.3,
and 7.4. I don't have access to gVim but I did reproduce this problem on
MacVim, as well as in terminal vim over ssh.
Steps to reproduce:
Configuration doesn't ma
>
> i.e. Vim always sets a light background for all colors except the first
>
> 7 and color 8 for which it will set a dark background. I don't think Vim
>
> should try to determine what color is used and depending on it's value
>
> try to set a sane 'bg' value for the other 256 colors (in a
32 matches
Mail list logo
