On Monday 09 August 2010 21:43:41 Vlad Irnov wrote:
But it's really Normal. I get +persistent_undo after compiling
Normal version on Windows with MinGW.
i get it after compiling Big version on linux with gcc
sc
--
You received this message from the vim_dev maillist.
Do not top-post! Type
Vlad Irnov wrote:
According to
:help +feature-list
the smallest version with persistent_undo is Huge,
line 367 in doc/various.txt is
H *+persistent_undo* Persistent undo |undo-persistence|
But it's really Normal. I get +persistent_undo after compiling Normal
version on Windows with
On Tuesday 10 August 2010 05:12:35 Tony Mechelynck wrote:
Well, 'lines', 'columns', 'guifont', 'guioptions', 'guicursor' can be
set, and the :winpos command issued, before the GUI is started, e.g. in
your vimrc (just remember to check :if has('gui_running') since they can
sometimes give
On 08.09.2010 22:02:50
b...@moolenaar.net wrote:
James Vega wrote:
On Mon, Aug 9, 2010 at 9:49 AM, Roland Puntaier
roland.punta...@br-automation.com wrote:
On Mon, 09 Aug 2010 13:49:43
Andy Kittner and...@gmx.de wrote:
I made the test in Vim 7.3: After removing RTLD_GLOBAL there
On 08.09.2010 22:02:48
b...@moolenaar.net wrote:
I would opt for the following:
If only one, Python 2.x xor Python 3.x, is configured (and if
DYNAMIC_PYTHON), then use RTLD_GLOBAL:
#define load_dll(n) dlopen((n), RTLD_LAZY|RTLD_GLOBAL)
If both are configured use without
On Mon, Aug 9, 2010 at 10:55 PM, Bram Moolenaar wrote:
Thanks, but it's not quite rigth. Most GUI functions must not be called
when gui.starting is TRUE, only when gui.in_use is TRUE. You might not
notice this when testing, as there are some dependencies on timing.
Also, you missed a few
Sometimes I paste some text into the Vim command line
(example: type ':echo ' then Ctrl-R a to paste register a).
If I accidentally paste a large amount (kilobytes), I have to
wait a very long time (several minutes) while Vim struggles
to handle the text. Pressing Ctrl-C has no discernible
On Aug 10, 2010, at 14:22 , John Beckett wrote:
Sometimes I paste some text into the Vim command line
(example: type ':echo ' then Ctrl-R a to paste register a).
If I accidentally paste a large amount (kilobytes), I have to
wait a very long time (several minutes) while Vim struggles
to
On 10-Aug-2010 14:22, John Beckett wrote:
Sometimes I paste some text into the Vim command line
(example: type ':echo ' then Ctrl-R a to paste register a).
If I accidentally paste a large amount (kilobytes), I have to
wait a very long time (several minutes) while Vim struggles
to handle the
On Aug 10, 4:34 pm, Ben Fritz fritzophre...@gmail.com wrote:
Vim is not multi-threaded, I doubt things are actually running during
the sleep. Or maybe you just need time for non-Vim stuff initiated by
Vim to finish? What happens if you don't call sleep but just
ReloadSession (not that 100ms
Nazri Ramliy wrote:
On Mon, Aug 9, 2010 at 5:33 PM, Nazri Ramliy ayieh...@gmail.com wrote:
On Mon, Aug 9, 2010 at 4:14 PM, Nazri Ramliy ayieh...@gmail.com wrote:
On Mon, Aug 9, 2010 at 4:05 PM, Bram Moolenaar b...@moolenaar.net wrote:
The test is passing for me on all platforms, except
Peter Odding wrote:
I just got an E432 error and consulted the documentation which contains
a typo. I've attached a patch against the latest vim-7.3e updated today.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
33. You name your children Eudora, Mozilla and Dotcom.
///
We tracked down the issue to a change in the file src/ex_getln.c.
Here is the change log for the change that introduced the problem:
CVS revision 1.14
HG revision 4d9eabb139
date: 2005/02/22 08:44:08; author: vimboss; state: Exp; lines: +181
-182
updated for version 7.0051
if
Nazri Ramliy wrote:
I wrote earlier:
To make test73 pass on unix, msvc-vim and djggp-vim I'll use
uppercase letters for all the directory names that it uses (unless
someone has a better idea).
I didn't work.
The test still fails due to the different ordering of the find
completion
Christian J. Robinson wrote:
I guess it's too late to add this to Vim 7.3, but attached is a very
simple patch that enables X1Mouse and X2Mouse under GTK/Gnome.
It appears GDK does not provide defines for GDK_BUTTON8_MASK /
GDK_BUTTON9_MASK, so this patch does not support X1Drag /
Xavier de Gaye wrote:
On Mon, Aug 9, 2010 at 10:55 PM, Bram Moolenaar wrote:
Thanks, but it's not quite rigth. Most GUI functions must not be called
when gui.starting is TRUE, only when gui.in_use is TRUE. You might not
notice this when testing, as there are some dependencies on
Roland Puntaier wrote:
What do you suggest we do when RTLD_GLOBAL is needed? Disallow building
with two versions of Python? Or restrict use at runtime, as it is now?
We could add an option to switch using RTLD_GLOBAL on/off, but it's
really ugly. I would rather tell users to build two
Roland Puntaier wrote:
There are no differences apart from :py3 - :py[thon], and the discussed
consequences,
and the possible restrictions in python functionality, if both versions
are enabled, as discussed in this thread.
I had a look at the current documentation. You already mention
John Beckett wrote:
Sometimes I paste some text into the Vim command line
(example: type ':echo ' then Ctrl-R a to paste register a).
If I accidentally paste a large amount (kilobytes), I have to
wait a very long time (several minutes) while Vim struggles
to handle the text. Pressing
Jakson Aquino wrote:
The Portuguese dictionaries downloaded by runtime/spell/pt/main.aap
are outdated. The attached patch fix this and I hope the patch is
ok...
The European Portuguese list of words has additional information about
the grammatical category of the words, as in the lines
Bram wrote:
In function getcmdline() (file ex_getln.c line 1840) we find:
/* Always redraw the whole command line to fix shaping and
* right-left typing. Not efficient, but it works. */
redrawcmd();
Removing that redrawcmd() makes accidental pastes of 8000
bytes into the
Ingo Karkat wrote:
There's no need to modify the source code to avoid the
redraw; just turn off Arabic shaping. There was a discussion
about this on this list two years ago (I was involved, that's
why I remember ;-):
http://tech.groups.yahoo.com/group/vimdev/message/51944
Andy Block wrote:
Are you by any chance using MacVim? I had this problem with
MacVim and raised it in the MacVim list.
No, but I mentioned your post earlier, see:
http://groups.google.com/group/vim_dev/browse_thread/thread/40e590a3b0ca1b43
I had experienced this frustration a couple of times
On Tue, Aug 10, 2010 at 6:15 PM, Bram Moolenaar b...@moolenaar.net wrote:
Unfortunately, when I run Aap, applying the diff fails. It looks like
the diff was made for another pt_PT.aff file. The one that was
downloaded looks like this:
SET UTF-8
LANG pt_PT
TRY
On Wed, Aug 11, 2010 at 1:58 AM, Bram Moolenaar b...@moolenaar.net wrote:
The full path names are not nice. Not only for the test but also for
interactive use. I think we should replace the current directory with
./ when possible.
Thanks for pointing this out. Attached patch does the
On Wed, Aug 11, 2010 at 12:04 PM, Nazri Ramliy ayieh...@gmail.com wrote:
On Wed, Aug 11, 2010 at 1:58 AM, Bram Moolenaar b...@moolenaar.net wrote:
The full path names are not nice. Not only for the test but also for
interactive use. I think we should replace the current directory with
./
Found a problem with c.vim runtime files regarding the syntax region
definitions.
Attached pictures shows the error in color regions.
Color scheme used is Zenburn.
http://vim.sourceforge.net/scripts/script.php?script_id=415
The diff of c.vim that is causing problem:
---
On Mon, Aug 09, 2010 at 07:37:13PM -0400, James Vega wrote:
On Sun, Aug 08, 2010 at 11:12:01PM -0400, James Vega wrote:
On Mon, Aug 09, 2010 at 09:28:01AM +0800, Nazri Ramliy wrote:
I stumbled into this problem (works fine in my environment, but fails in
/bin/dash) when I first attempted
28 matches
Mail list logo
