Hello,
The attachment is a patch that will not indent the line after '@*' for
java, such as @Override, @Deprecated.
The file header says that the maintainer has resigned, so I did not try
to contact him/her.
If I have done anything wrong, please point it out.
Hong
--
You received this mes
Hello,
The value of "fileencoding" does not change after saving a new file,
until reopen the file.
Regards,
Hong Xu
10/01/2010
--
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.v
Does this bug get any chance to be fixed? Thanks.
On 10/1/10, Tony Mechelynck wrote:
> On 01/10/10 03:39, H Xu wrote:
>> Hello,
>>
>> The value of "fileencoding" does not change after saving a new file,
>> until reopen the file.
>>
>> Regards,
>
intended to be. Thank you.
Hong Xu
10/10/10
On 10/10/10, Bram Moolenaar wrote:
>
> H Xu wrote:
>
>> Does this bug get any chance to be fixed? Thanks.
>
> This is not a bug. Works as intended.
>
>> On 10/1/10, Tony Mechelynck wrote:
>> > On 01/10/10 03:39, H Xu
Hello:
The attachment is a patch which provides two pseudo-random number generating
functions for vimscript.
Thanks.
Hong Xu
2010/11/08
--
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 htt
OK, the attachment is the latest patch which I add a srand function to set seed.
-Original Message-
From: Bram Moolenaar
Sent: 2010/11/09 02:08:27
To: H Xu
Cc: vim_dev@googlegroups.com
Subject: Re: [PATCH] provide random number generating functions for vimscript
Hong Xu wrote:
>
To Bram:
Yes, randfloat would not be frequently used.
The attachment is a new patch which simplifies randfloat function and makes
srand function more convenient to use.
Hong Xu
2010/11/10
-Original Message-
From: Bram Moolenaar
Sent: 2010/11/10 19:45:52
To: xuh...@gmail.com
Cc: vim_d
Hello,
The attachment is a patch which makes vim not to lose its focus when
executing an external program in background on Windows. It is always
annoying when use "system()" function to execute a program in background
and gvim loses its focus (the focus was set to the console window owned by
the s
Hello,
When I add "b1" to cinoptions, vim doesn't indent current line when I
type "break" by default. This is inappropriate, I think. So I
recommend to change the default value of cinkeys by adding "0break".
What do you think?
Hong Xu
2010/11/26
--
You received this message from the "vim_dev"
On 11/26/2010 03:37 PM, H Xu wrote:
Hello,
When I add "b1" to cinoptions, vim doesn't indent current line when I
type "break" by default. This is inappropriate, I think. So I
recommend to change the default value of cinkeys by adding "0break".
What do you
On 2010/11/27 4:34, Bram Moolenaar wrote:
Hong Xu wrote:
On 11/26/2010 03:37 PM, H Xu wrote:
Hello,
When I add "b1" to cinoptions, vim doesn't indent current line when I
type "break" by default. This is inappropriate, I think. So I
recommend to change the default v
On 11/27/2010 09:49 PM, Lech Lorens wrote:
On 27-Nov-2010 H Xu wrote:
On 2010/11/27 4:34, Bram Moolenaar wrote:
Well, if you change the default for 'cinoptions', then it's not unusual
to also need to change 'cinkeys'. I don't think "break" needs to
On 12/04/2010 01:45 AM, H Xu wrote:
On Thu, Oct 28, 2010 at 4:58 PM, George Hawkins
wrote:
Hi there --
I'm using the standard yum installed Gvim on a normal Fedora 13 system
running Gnome.
For whatever reason I quite like the Windows Gvim arrangement where
clicking the right mouse b
On 12/04/2010 11:09 PM, Bram Moolenaar wrote:
Hong Xu wrote:
I think I have fixed this problem. The attachment is the patch. The
reason is that when gtk_menu_popup is called, its last parameter is
not passed in the correct time stamp but GDK_CURRENT_TIME. I fixed
this by adding a global varibl
Hello Bram,
Now we don't need to access any other field, we can change this when we need to
access them. The attachment is the patch to rename the variable and fix the
problem.
Regards,
Hong Xu
2010/12/5
-Original Message-
From: Bram Moolenaar
Sent: 2010/12/05 22:47:29
To: H
Hi,
When using :f to rename, for example, from a.txt to a.c, the
'filetype' does not automatically change when autocmd is compiled,
while :e could change 'filetype'. Should this be fixed by adding
"BufFilePost" to each autocmd which changes 'filetype' in
filetype.vim?
Regards,
Hong Xu
2010/12/9
-
Hi Bram,
labs is in the c89 standard. Is it widespread enough?
Hong Xu
2010/12/22
On 12/22/10, Bram Moolenaar wrote:
>
> Hong Xu wrote:
>
>> The attached file removes some unnecessary type casting in vim's
>> source file by replacing abs function with labs function.
>
> This uses the labs() fun
Hello,
"vimdiff" doesn't work when the arguments are urls. For example,
"vimdiff /home/user/a.c /home/user/b.c" works, but "vimdiff
file:///home/user/a.c file:///home/user/b.c" doesn't work.
Tested under Linux.
Regards,
Hong Xu
01/01/2011
--
You received this message from the "vim_dev" maillis
On 01/03/2011 11:51 PM, Charles Campbell wrote:
Hello,
Please try netrw v141i available from my website
(http://mysite.verizon.net/astronaut/vim/index.html#NETRW).
HTH,
Chip Campbell
Hello Charles Campbell,
v141i works fine. Thanks!
Regards,
Hong Xu
01/05/2011
--
You received this message
On Sat, Dec 4, 2010 at 11:09 PM, Bram Moolenaar wrote:
>
> Hong Xu wrote:
>
>> I think I have fixed this problem. The attachment is the patch. The
>> reason is that when gtk_menu_popup is called, its last parameter is
>> not passed in the correct time stamp but GDK_CURRENT_TIME. I fixed
>> this by
On Sat, Dec 4, 2010 at 11:09 PM, Bram Moolenaar wrote:
>
> Hong Xu wrote:
>
>> I think I have fixed this problem. The attachment is the patch. The
>> reason is that when gtk_menu_popup is called, its last parameter is
>> not passed in the correct time stamp but GDK_CURRENT_TIME. I fixed
>> this by
Hello,
The comment in function vim_tempname says: "GetTempPath() failed, use
current
dir". It use "szTempFile[0] = NUL" to do this, which makes szTempFile an
empty
string. szTempFile is going to be passed as a parameter to the function
GetTempFileName. However, if we want to use current direct
Hello,
tmpnam() might return a NULL pointer if it failed to generate a unique
name. Vim doesn't handle it properly. Here's the patch to fix it.
Regards,
Hong Xu
2011/2/6
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
On 2011/2/6 20:21, Bram Moolenaar wrote:
Hong Xu wrote:
The comment in function vim_tempname says: "GetTempPath() failed, use
current
dir". It use "szTempFile[0] = NUL" to do this, which makes szTempFile an
empty
string. szTempFile is going to be passed as a parameter to the function
GetTempFi
On 2011/2/7 4:45, Bram Moolenaar wrote:
Ingo Karkat wrote:
On 06-Feb-2011 14:38, Bram Moolenaar wrote:
They are in the todo list.
Ah, okay. I had checked todo.txt in Mercurial and on ftp.vim.org, and they're
both outdated:
*todo.txt* For Vim version 7.3. Last change: 2011 Jan 07
Hello,
The attachment fixes a document bug, which misses some float point
functions in usr_41.txt.
Regards,
H Xu
03/01/2011
--
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,
Hello,
The attachment is a patch for filetype.vim to improve the determination
of *.pro files.
If the pro file is a cpp file, we think that the second line is a
function prototype which ends with a ";". However, IDL source file may
also put a single ";" in the second line as comment just as many
Hello,
To reproduce:
:!echo -n 'Hello' >temp.txt
:echo readfile('temp.txt')
Then an empty list is displayed rather than the content of this file.
The attached patch fixes this problem.
Regards,
Hong Xu
2011/3/26
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
On 2011/3/26 15:48, H Xu wrote:
Hello,
To reproduce:
:!echo -n 'Hello' >temp.txt
:echo readfile('temp.txt')
Then an empty list is displayed rather than the content of this file.
The attached patch fixes this problem.
Regards,
Hong Xu
2011/3/26
Hello,
The last patc
On 2011/3/26 18:38, H Xu wrote:
On 2011/3/26 15:48, H Xu wrote:
Hello,
To reproduce:
:!echo -n 'Hello' >temp.txt
:echo readfile('temp.txt')
Then an empty list is displayed rather than the content of this file.
The attached patch fixes this problem.
Hello,
The last
Hello,
The comment in configure.in says "Exuberant ctags is preferred", but it
doesn't check exctags command. On some systems, the binary of Exuberant
ctags is default to exctags, such as my NetBSD, while ctags is the
default ctags shipped with the operating system; so we also need to
check excta
Hello,
"FOR" should not be regarded as idlangRoutine. This is fixed in the
attachment.
Cannot get in touch with the maintainer.
Regards,
H Xu
2011/4/11
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are r
On 2011/4/14 3:05, Dominique Pellé wrote:
Hi
Attached patch fixes a bug in vim_getenv() found
with cppcheck static analyzer:
$ cd vim/src ; cppcheck -f -I proto misc1.c
[misc1.c:3956]: (error) Possible null pointer dereference: mustfree -
otherwise it is redundant to check if mustfree is null a
On 2011/4/14 16:28, Dominique Pellé wrote:
H Xu wrote:
On 2011/4/14 3:05, Dominique Pellé wrote:
Hi
Attached patch fixes a bug in vim_getenv() found
with cppcheck static analyzer:
$ cd vim/src ; cppcheck -f -I proto misc1.c
[misc1.c:3956]: (error) Possible null pointer dereference
Hello,
Here is the version information:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 6 2011 08:50:20)
Included patches: 1-177
Compiled by someone
Huge version with GTK2 GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent
+c
On 05/07/2011 11:40 AM, Ben Schmidt wrote:
Here is the version information:
...
+python/dyn +python3/dyn +quickfix +reltime +rightleft -ruby
+scrollbind +signs
...
However, :echo has('python') returns 0.
Does the :python command work? If not, perhaps it can't find the python
library at runt
On 05/07/2011 11:40 AM, Ben Schmidt wrote:
Here is the version information:
...
+python/dyn +python3/dyn +quickfix +reltime +rightleft -ruby
+scrollbind +signs
...
However, :echo has('python') returns 0.
Does the :python command work? If not, perhaps it can't find the python
library at runt
Hello,
This patch makes the three commands: mkvimrc, mksession and mkexrc
commands could have a directory name as its argument. If the argument is
a directory, Then the file, which is the .vimrc, Session.vim or .exrc,
is generated under the directory and is named as the default file name
(whi
Hello,
python3 is not listed there. The patch fixes this.
Regards,
Hong Xu
05/07/2011
--
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
diff -r 60890b26cb17 r
On 05/07/2011 07:20 PM, Bram Moolenaar wrote:
Hong Xu wrote:
This patch makes the three commands: mkvimrc, mksession and mkexrc
commands could have a directory name as its argument. If the argument is
a directory, Then the file, which is the .vimrc, Session.vim or .exrc,
is generated under the
On 2011/5/10 2:35, Bram Moolenaar wrote:
Hong Xu wrote:
This patch makes the three commands: mkvimrc, mksession and mkexrc
commands could have a directory name as its argument. If the argument is
a directory, Then the file, which is the .vimrc, Session.vim or .exrc,
is generated under the dire
On 05/10/2011 11:22 PM, Bram Moolenaar wrote:
Patch 7.3.188
Problem:More RISC OS files to remove.
Solution: Remove them. Update the file list.
Files: src/proto/gui_riscos.pro, src/proto/os_riscos.pro, Filelist
*** ../vim-7.3.187/src/proto/gui_riscos.pro 2010-08-15 21:57:28.
On 05/10/2011 11:22 PM, Bram Moolenaar wrote:
Patch 7.3.188
Problem:More RISC OS files to remove.
Solution: Remove them. Update the file list.
Files: src/proto/gui_riscos.pro, src/proto/os_riscos.pro, Filelist
*** ../vim-7.3.187/src/proto/gui_riscos.pro 2010-08-15 21:57:28.
On 05/15/2011 07:15 PM, H Xu wrote:
On 05/10/2011 11:22 PM, Bram Moolenaar wrote:
Patch 7.3.188
Problem: More RISC OS files to remove.
Solution: Remove them. Update the file list.
Files: src/proto/gui_riscos.pro, src/proto/os_riscos.pro, Filelist
*** ../vim-7.3.187/src/proto/gui_riscos.pro
On 05/15/2011 10:20 PM, Ben Schmidt wrote:
On 15/05/11 9:07 PM, H Xu wrote:
Another winner for the worst quote trimming ever.
I have no idea what you even wrote in your other messages, because I
couldn't easily find your reply amongst the patches.
Could you/others please trim quotes t
Hello,
The and , the two mouse keys, exactly exist in vim.
However, it seems that nothing about them is mentioned in the doc. Hope
it could be written somewhere?
Regards,
H Xu
2011/5/22
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply
On 2011/5/22 21:30, H Xu wrote:
Hello,
The and , the two mouse keys, exactly exist in vim.
However, it seems that nothing about them is mentioned in the doc. Hope
it could be written somewhere?
Sorry that I've made a mistake.
--
You received this message from the "vim_dev" m
urial repository.
Regards,
H Xu
05/28/2011
--
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
On 2011/5/29 20:54, Ben Schmidt wrote:
On Thu, May 26, 2011 at 5:00 PM, Ben Schmidt mailto:mail_ben_schm...@yahoo.com.au>> wrote:
On 27/05/11 1:02 AM, Richard Guse wrote:
I'm using Vim 7.3 7/20/2010 under Windows 7.
I usually start gvim from the command-line but sometimes from
Windows Explorer
RISC OS is unsupported now, and I think osfiletype related code should
also be removed. Here is the patch to remove them.
Regards,
Hong Xu
06/05/2011
--
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 informat
On 05/29/2011 08:54 PM, Ben Schmidt wrote:
Below is a message from vim_use where we've partially identified the
cause of some bug. Maybe there's a Windows dev here who has some more
ideas, or could reproduce it and track it down? I'm afraid I'm pretty
useless from here.
Smiles,
Ben.
On Thu,
ly from the original author of this syntax file.
Regards,
H Xu
2011/7/15
--
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
diff -r e9538cfd0d9c runtim
On 2011/7/15 22:01, Bram Moolenaar wrote:
Hong Xu wrote:
The attached patch also highlights lines starting with '#' as comment
line. Now most dosini parser also regards '#' as comment string, and
Debian has already modified dosini.vim to highlight lines starting with
'#' as comment lines.
Cou
On 2011/7/16 19:53, Bram Moolenaar wrote:
James Vega wrote:
On Fri, Jul 15, 2011 at 04:01:13PM +0200, Bram Moolenaar wrote:
Hong Xu wrote:
The attached patch also highlights lines starting with '#' as comment
line. Now most dosini parser also regards '#' as comment string, and
Debian has alr
/etc/yum.conf and /etc/yum.repos.d/* are widely used, and their conf
files are dosini format. So we should set their filetype to dosini in
filetype.vim.
Regards,
Hong Xu
07/19/2011
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you ar
Hi,
I'm using MSVC 9.0, using the following command to compile vim 7.3.266:
nmake -f Make_mvc.mak GUI=yes PYTHON=C:\Python26 DEBUG=no
OPTIMIZE=MAXSPEED PYTHON_VER=26 DYNAMIC_PYTHON=yes FEATURES=HUGE
PERL=C:\perl PERL_VER=514 DYNAMIC_PERL=yes
The link stage fails, with the following messages:
When build vim with MSVC, there is always a warning message like this
when compiling each source file:
x:\path\to\source\ascii.h : warning C4819: The file contains a character
that cannot be represented in the current code page (936). Save the
file in Unicode format to prevent data loss
The att
On 2011/8/21 23:53, Bram Moolenaar wrote:
When build vim with MSVC, there is always a warning message like this
when compiling each source file:
x:\path\to\source\ascii.h : warning C4819: The file contains a character
that cannot be represented in the current code page (936). Save the
file in Un
Vim sometimes crashes when using ":GetScripts". Here is the debug
information (7.3.303):
(gdb) run -g -f
Starting program: /xx/src/vim-debug/src/vim -g -f
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x00605b28 in mf_put (mfp=0x20
On 09/10/2011 08:24 PM, Bram Moolenaar wrote:
Hong Xu wrote:
Vim sometimes crashes when using ":GetScripts". Here is the debug
information (7.3.303):
Thanks for the stack trace. I can see what happens: when a window is
closed, halfway when freeing up the data structures, the GUI resize
caus
On 09/12/2011 02:41 AM, niva wrote:
Hi,
Following the instructions to get vim 7.3 last version with MErcurial,
I am trying to patch this version with the latest patch under windows
but...
...under windows, it seems that patch does not exist.
After you update vim with mercurial, it's already t
61 matches
Mail list logo
