Yukihiro Nakadaira wrote:
On Thu, Jul 25, 2013 at 12:53 AM, Bram Moolenaar b...@moolenaar.net wrote:
Yukihiro Nakadaira wrote:
On Mon, Jul 8, 2013 at 9:51 AM, r...@raf.org wrote:
Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.4a BETA
This is
On Friday, July 26, 2013 5:11:56 AM UTC+2, studog wrote:
I cloned your repository, updated the svn.vim syntax file, and have been
running it for a few days. It works great. Patch attached.
BTW, can you send it as a pull request?
I added all the translations svn-1.8.0 is currently using;
On windows 7 64-bit I get this behaviour both in gvim and vim.
The options I have in the vimrc file are read, so this seems like a bug.
Regards
Andreas Stabel
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For
Hi,
:perldo doesn't work with ActivePerl 5.14 on 32-bit Windows when complied
by MSVC8 or later. (And :perl may crash with ActivePerl 5.16.)
It is caused by mismatch of time_t size.
The following patch fixes this:
--- a/src/Make_mvc.mak
+++ b/src/Make_mvc.mak
@@ -846,6 +846,14 @@
CFLAGS =
Hi,
We vim-jp.org members found that the Japanese man pages are not shown
properly on Linux. (Word spacing is not correct.) The Japanese man pages
are currently placed in the ja.UTF-8/ directory, but it should be ja/.
groff should load /usr/share/groff/1.21/tmac/ja.tmac to process Japanese
text,
Hi,
I think vimLoadLib() is used because of security reason,
but LoadLibraryEx() is used directly in if_tcl.c.
Should we use vimLoadLib() in if_tcl.c?
--- a/src/if_tcl.c
+++ b/src/if_tcl.c
@@ -195,7 +195,7 @@
if (hTclLib)
return OK;
-if (!(hTclLib = LoadLibraryEx(libname,
Hi,
There are some implementations which support SGR mouse. Xterm is not the
only one. So I think xterm-277 is confusing.
--- a/runtime/doc/version7.txt
+++ b/runtime/doc/version7.txt
@@ -10349,8 +10349,7 @@
Added |v:windowid| variable containing current window number in GUI
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches any char
including end of line and * is greedy
/pattern\_.* does what I expect: it matches from pattern to end of file
Dimitar
An update/clarification on
Hi,
Some part of regexp_nfa.c is not aligned.
It was aligned before 7.3.1137.
Attached patch fixes this.
Regards,
Ken Takata
--
--
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
On Monday, July 29, 2013 7:55:47 AM UTC-4, Dmitry Vasiliev wrote:
BTW, can you send it as a pull request?
Not at the moment; the git respository is in a VM on my laptop which isn't
usually publically available. I'll look at setting up on github.
Also, I am waiting until I've pulled all the
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
On windows 7 64-bit I get this behaviour both in gvim and vim.
The options I have in the vimrc file are read, so this seems like a bug.
Regards
Andreas Stabel
Does your .vimrc show up in the output of :scriptnames?
What does :verbose
On Mon, July 29, 2013 14:59, Dimitar DIMITROV wrote:
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches any
char including end of line and * is greedy
/pattern\_.* does what I expect: it matches from pattern to
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches any
char including end of line and * is greedy
/pattern\_.* does what I expect: it matches from pattern to end of file
Dimitar
An
On Mon, July 29, 2013 16:14, Dimitar DIMITROV wrote:
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches
any
char including end of line and * is greedy
/pattern\_.* does what I expect: it matches from
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches
any
char including end of line and * is greedy
/pattern\_.* does what I expect: it matches from pattern to end of
file
Dimitar
An
*abandon*
Vim remembers whether you have changed the buffer. You are protected from
losing the changes you made. If you try to quit without writing, or want to
start editing another file, Vim will refuse this. In order to overrule this
Comment #7 on issue 157 by octopusg...@gmail.com: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
This problem is resolved 7.4a beta. Thanks for your help.
--
You received this message because this
On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
On windows 7 64-bit I get this behaviour both in gvim and vim.
The options I have in the vimrc file are read, so this seems like a bug.
Regards
Andreas Stabel
Does your
On Monday, July 29, 2013 11:39:11 AM UTC-5, Stephen Lee wrote:
On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
On windows 7 64-bit I get this behaviour both in gvim and vim.
The options I have in the vimrc file are read,
The 'equalalways' option makes all the windows the same size after a window is
split or closed. However, it doesn't when the Vim window (either the terminal
or the GUI) is resized. I hear many people run [g]vimdiff or ':vsplit', enlarge
the Vim window, only to find only one of the two inner
On Tuesday, July 30, 2013 1:07:20 AM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 11:39:11 AM UTC-5, Stephen Lee wrote:
On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
On windows 7 64-bit I get this behaviour both in
Updates:
Status: Done
Comment #8 on issue 157 by drc...@campbellfamily.biz: gVim alters file type
from Unix to DOS, with propert configuration directives in place.
http://code.google.com/p/vim/issues/detail?id=157
Problem resolved by upgrading vim (to 7.4a beta).
--
You received
David Larson wrote:
On Saturday, June 8, 2013 2:48:39 PM UTC-7, Bram Moolenaar wrote:
There are no options. Vim is written in C and I see no reason to
change. Perhaps, when Zimbu is ready I might consider rewriting some
pieces in Zimbu, but that's going to take several years during which no
On 29-Jul-2013 Stephen Lee stephenletter...@gmail.com wrote:
On Tuesday, July 30, 2013 1:07:20 AM UTC+8, Ben Fritz wrote:
Also note, the recommended place for your _vimrc file is in $HOME (or
$HOME/vimfiles with the latest 7.4 beta builds).
Thankyou for your help. It looks like it is
Hi Ingo!
On Fr, 26 Jul 2013, Ingo Karkat wrote:
Hello Vim developers,
Patch 7.3.590 allows to set the visual selection directly via the marks
' and '. I've found a problem with :set selection=exclusive (while
developing a custom mapping): When the first selection after Vim startup
is
On Monday, July 29, 2013 8:58:29 AM UTC-4, Ken Takata wrote:
Hi,
There are some implementations which support SGR mouse. Xterm is not the
only one. So I think xterm-277 is confusing.
--- a/runtime/doc/version7.txt
+++ b/runtime/doc/version7.txt
@@ -10349,8 +10349,7 @@
Added
I've updated some of these files. Let me know if it's too late to include
these in the next release.
filetype.vim was simplified by specifying '\c' for case-insensitivity.
upstreamlog.vim, usserverlog.vim, and usw2kagtlog.vim had various improvements
for syntax detection and I fixed a couple
Ken Takata wrote:
We vim-jp.org members found that the Japanese man pages are not shown
properly on Linux. (Word spacing is not correct.) The Japanese man pages
are currently placed in the ja.UTF-8/ directory, but it should be ja/.
groff should load /usr/share/groff/1.21/tmac/ja.tmac to
Ken Takata wrote:
:perldo doesn't work with ActivePerl 5.14 on 32-bit Windows when complied
by MSVC8 or later. (And :perl may crash with ActivePerl 5.16.)
It is caused by mismatch of time_t size.
The following patch fixes this:
--- a/src/Make_mvc.mak
+++ b/src/Make_mvc.mak
@@ -846,6
Ken Takata wrote:
There are some implementations which support SGR mouse. Xterm is not the
only one. So I think xterm-277 is confusing.
--- a/runtime/doc/version7.txt
+++ b/runtime/doc/version7.txt
@@ -10349,8 +10349,7 @@
Added |v:windowid| variable containing current window number
Ken Takata wrote:
Some part of regexp_nfa.c is not aligned.
It was aligned before 7.3.1137.
Attached patch fixes this.
Thanks!
--
So this is it, said Arthur, we are going to die.
Yes, said Ford, except...no! Wait a minute! He suddenly lunged across
the chamber at something behind
Thomas Dickey wrote:
On Monday, July 29, 2013 8:58:29 AM UTC-4, Ken Takata wrote:
Hi,
There are some implementations which support SGR mouse. Xterm is not the
only one. So I think xterm-277 is confusing.
--- a/runtime/doc/version7.txt
+++ b/runtime/doc/version7.txt
@@ -10349,8
I just noticed this today with 7.4b but the behavior is the same
with 7.4a.9. It works correctly with 7.3.882.
The problem is that when I open a temporary file created by mutt
with the name /tmp/muttV1LGjR, the latest versions of vim do not
recognize this as a file name that should set
I have a mapping:
inoremap buffer ' 'Esc:call SmartQuote(1)CRa
which does the right thing when a single-quote is inserted. That is, it
either creates a set of matching typographically correct single-quotes, or it
inserts an apostrophe. It works fine in English.
When I switch the
34 matches
Mail list logo
