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
, Cygwin). This might mean
that the test file should source unix.vim. Or perhaps check for Vim
having been compiled with X11 support.
--
Lech Lorens
--
--
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
On 5 November 2013 08:22, Christian J. Robinson hept...@gmail.com wrote:
On the 2nd I built 7.3.054 under cygwin, then some new patches came down and
when I tried to build again I got this:
In file included from /usr/lib/../include/w32api/minwindef.h:146:0,
from
On 5 November 2013 10:56, Christian J. Robinson hept...@gmail.com wrote:
On Tue, 5 Nov 2013, Lech Lorens wrote:
On 5 November 2013 08:22, Christian J. Robinson hept...@gmail.com wrote:
/usr/lib/../include/w32api/winnt.h:4951:15: error: two or more
data types in declaration
On 08-Nov-2013 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
Attached is a patch fixing E315 error caused by delete ex command not
resetting visual selection.
Test included.
Note that this is related to pressing Escape when in visual mode
triggering a yank
On 08-Nov-2013 Lech Lorens lech.lor...@gmail.com wrote:
On 08-Nov-2013 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
Attached is a patch fixing E315 error caused by delete ex command not
resetting visual selection.
Test included.
Note
I guess this will be a solution to a bug reported by Matteo Cavalleri in
vim_use. At least it solves the totally messed-up numbers when diffing
2 windows, each with 'rnu' set that have been annoying me for a long
time.
--
Lech Lorens
--
--
You received this message from the vim_dev
On 12 December 2013 22:47, Lech Lorens lech.lor...@gmail.com wrote:
I guess this will be a solution to a bug reported by Matteo Cavalleri in
vim_use. At least it solves the totally messed-up numbers when diffing
2 windows, each with 'rnu' set that have been annoying me for a long
time
are not removed which
means editing foo is virtually imposible.
This is with Vim 7.4.131 on Debian Wheezy 64 bits (big build) and Netrw
v147nNR.
7.4.131 on 32 bits Linux Mint, Netrw v149.
CC: Charles Campbell.
--
Lech Lorens
--
--
You received this message from the vim_dev maillist.
Do not top-post
On 05-Nov-2013 Lech Lorens lech.lor...@gmail.com wrote:
On 5 November 2013 10:56, Christian J. Robinson hept...@gmail.com wrote:
On Tue, 5 Nov 2013, Lech Lorens wrote:
On 5 November 2013 08:22, Christian J. Robinson hept...@gmail.com wrote:
/usr/lib/../include/w32api/winnt.h:4951
On 30-Dec-2013 Charles Campbell charles.e.campb...@nasa.gov wrote:
Hello!
I'm using vim 7.4.131 (Huge version with GTK2-GNOME GUI), and
haven't used Dominque's patch. When trying your problem out, netrw
went up a directory, even though foo no longer existed; both
going-up-directory
Hi,
Yesterday while remotely debugging some Vim scripts I discovered
(actually it is mentioned in the documentation) that remote_expr()
imposes a limitation on the type of expressions handled: the expression
must be a string or a list (although the implementation correctly
handles integers
On 06-Jan-2014 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
Yesterday while remotely debugging some Vim scripts I discovered
(actually it is mentioned in the documentation) that remote_expr()
imposes a limitation on the type of expressions handled: the expression
On 06-Jan-2014 Lech Lorens lech.lor...@gmail.com wrote:
On 06-Jan-2014 Bram Moolenaar b...@moolenaar.net wrote:
[…]
What happens with nested lists and dicts?
Whatever you think would be best. Currently exactly the same that would
happen locally for string(list_var) or string(dict_var). I
On 10 January 2014 20:16, Gary Johnson garyj...@spocom.com 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
to
translate instead of two shorter strings? Why start it with \n btw?
3.
+ MSG_PUTS(_(\nCould not remote security context ));
s/remote/remove/
--
Lech Lorens
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
On 15 January 2014 10:13, Christian Brabandt cbli...@256bit.org wrote:
On Wed, January 15, 2014 09:59, b...@airbladesoftware.com wrote:
Hello!
A user of one of my plugins recently reported this error: `E117: Unknown
function: gettabvar`. He also told me the version of Vim he's using.
How
winnr() returns the index of the window 1-based while v:beval_winnr
(:help 'bexpr') is 0-based. I believe the latter should be fixed. The
attached patch adds increments the value of v:beval_winnr by 1.
--
Lech Lorens
--
--
You received this message from the vim_dev maillist.
Do not top
On 17-Jan-2014 Ingo Karkat sw...@ingo-karkat.de wrote:
On 16-Jan-2014 23:46 +0100, Lech Lorens wrote:
winnr() returns the index of the window 1-based while v:beval_winnr
(:help 'bexpr') is 0-based. I believe the latter should be fixed. The
attached patch adds increments the value
On 17-Jan-2014 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
winnr() returns the index of the window 1-based while v:beval_winnr
(:help 'bexpr') is 0-based. I believe the latter should be fixed. The
attached patch adds increments the value of v:beval_winnr by 1
On 19-Jan-2014 Bram Moolenaar b...@moolenaar.net wrote:
Anhad Jai Singh wrote:
When I do 'o' (plain old 'o', no fancy mappings nothing, the deafult
open-INSERT-mode and take me to the next line 'o'), at a specific location
in a specific file, vim hits 100% CPU usage, becomes
On 20-Jan-2014 Yukihiro Nakadaira yukihiro.nakada...@gmail.com wrote:
On Sun, Jan 19, 2014 at 1:45 PM, Anhad Jai Singh
anhadjones5...@gmail.comwrote:
When I do 'o' (plain old 'o', no fancy mappings nothing, the deafult
open-INSERT-mode and take me to the next line 'o'), at a specific
On 20-Jan-2014 Christian Wellenbrock christian.wellenbr...@gmail.com wrote:
On Monday, January 20, 2014 1:08:07 PM UTC+1, Lech Lorens wrote:
I can confirm – it is caused by the indent script. The attached patch
marks the place that is incorrect (and might fix the problem
, 'text': getline(lnum)})
endwhile
let @/ = failingSearchPattern
normal ggn
call setloclist(0, qf)
lopen
#v-
--
Lech Lorens
--
--
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
an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Vim filetype plugin file
Language:XXD
Maintainer: Lech Lorens lech.lor...@gmail.com
Last Change: 2014 Feb 4
When the cursor is in the hexadecimal data representation, highlights
On 05-Feb-2014 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
I'd like to propose the attached ftplugin for XXD I've been using for
a long time. The plugin highlights the corresponding hexadecimal
representation for the character the cursor is on and the other way
On 05-Feb-2014 Bram Moolenaar b...@moolenaar.net wrote:
Christian Brabandt wrote:
any plans for Vim to participate in this years GSOC?
There is a good week left to apply for organizations.
https://www.google-melange.com/gsoc/homepage/google/gsoc2014
There is some work to be done,
This should have gone to the list, not only to Bram.
On 5 February 2014 20:44, Lech Lorens lech.lor...@gmail.com wrote:
On 05-Feb-2014 Bram Moolenaar b...@moolenaar.net wrote:
Looks useful. How much does this slow down moving the cursor around?
Would need to try it on a slow computer.
I've
On 15-Mar-2014 Andre Sihera andre.sih...@hotmail.co.jp wrote:
Hi all,
I have found an annoyance with the tab indenting (SHIFT + '', SHIFT
+ '') and
was wondering if this was by design or should be fixed.
My .vimrc contains the following:
set ts=4
set shiftwidth=4
So, when I
On 16-Mar-2014 James McCoy james...@jamessan.com wrote:
On Sat, Mar 15, 2014 at 03:37:27PM +0100, Lech Lorens wrote:
I believe what you are trying to achieve is what I did in the patch
I posted 4 years ago here:
https://groups.google.com/forum/#!msg/vim_dev/JDLJgDk-ZrQ/nROMNPdwfhwJ
I
On 5 February 2013 17:02, Nazri Ramliy ayieh...@gmail.com wrote:
On Tue, Feb 5, 2013 at 5:11 PM, Nazri Ramliy ayieh...@gmail.com wrote:
Attached is an updated patch for the 'linenumber' option (it's getting
hairier and hairier! But not that much. I'd say it's less toy-ish by
now :)
It
On 28 February 2013 06:19, Ben Fritz fritzophre...@gmail.com wrote:
Ugh, I can't reproduce it at home with the example config on Windows Vista.
There has to be something else interfering. I hope it's not some video card
thing or something. I'll try it on a few more computers at work I
On 29-Mar-2013 Cody Cutler ccut...@csail.mit.edu wrote:
Hello list. The attached patch allows optional regexs to be passed to
:tj and friends. these regexs is then used to further refine available
tags before they are printed.
This patch is useful when you have many tags for a single
People using ctags while working on code which is edited by multiple
people in various editors will be familiar with this situation: the code
ends up with a mix of line endings – some of them are Unix-style, some
of them are DOS-style.
The problem is that if Vim reads such a file with ff=unix,
On 01-Apr-2013 David Fishburn dfishburn@gmail.com wrote:
On Mon, Apr 1, 2013 at 11:16 AM, Lech Lorens lech.lor...@gmail.com wrote:
People using ctags while working on code which is edited by multiple
people in various editors will be familiar with this situation: the code
ends up
On 01-Apr-2013 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
People using ctags while working on code which is edited by multiple
people in various editors will be familiar with this situation: the code
ends up with a mix of line endings – some of them are Unix-style
On 02-Apr-2013 Nazri Ramliy ayieh...@gmail.com wrote:
On Mon, Apr 1, 2013 at 11:16 PM, Lech Lorens lech.lor...@gmail.com wrote:
The problem is that if Vim reads such a file with ff=unix, it will fail
to find tags if the tag pattern searched should match on a DOS-style
line. The attached
On 02-Apr-2013 glts 676c7...@gmail.com wrote:
On Tue, Apr 2, 2013 at 1:59 AM, Lech Lorens lech.lor...@gmail.com wrote:
On 01-Apr-2013 Bram Moolenaar b...@moolenaar.net wrote:
How about this alternative: Filter your tags file to change the patterns
to include an optional CR before the $: \r
On 03-Apr-2013 Benjamin Fritz fritzophre...@gmail.com wrote:
On Wed, Apr 3, 2013 at 5:22 AM, Lech Lorens lech.lor...@gmail.com wrote:
How do
you cope with that? In this case I can't simply check in the file
– I have to undo the line endings modifications which is quite a tedious
The attached patch makes it possible to move the vimrc and gvimrc files
to your vim settings directory:
~/.vim/ (UNIX)
~\vimfiles\ (Windows)
etc. This makes it easier to move Vim settings from machine to machine:
you just copy one directory to the right place and it works.
Please, check and
:help :read! does not mention that it's possible to specify options with
this form of the :read command.
diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt
index 4db4341..0048c75 100644
--- a/runtime/doc/insert.txt
+++ b/runtime/doc/insert.txt
@@ -1869,7 +1869,8 @@ NOTE: These commands
On 12-Apr-2013 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
On 12 April 2013 13:45, Bram Moolenaar b...@moolenaar.net wrote:
The updated docs say:
Unix$HOME/.gvimrc or $HOME/.vim/gvimrc
Unix$HOME/.vimrc or $HOME
On 12-Apr-2013 Gary Johnson garyj...@spocom.com wrote:
On 2013-04-12, Lech Lorens wrote:
On 12 April 2013 13:45, Bram Moolenaar wrote:
The updated docs say:
Unix$HOME/.gvimrc or $HOME/.vim/gvimrc
Unix$HOME/.vimrc
On 13-Apr-2013 Bram Moolenaar b...@moolenaar.net wrote:
Thanks. Thus only when ~/.vimrc does not exist then ~/.vim/vimrc will
be used. That should work for places where a new Vim is installed. For
older Vim versions one would have to create a ~/.vimrc file that sources
~/.vim/vimrc.
Do we
On 29-Mar-2013 Cody Cutler ccut...@csail.mit.edu wrote:
Hello list. The attached patch allows optional regexs to be passed to
:tj and friends. these regexs is then used to further refine available
tags before they are printed.
This patch is useful when you have many tags for a single
On 16 April 2013 06:20, Yegappan Lakshmanan yegapp...@gmail.com wrote:
I spent some time trying to narrow down the patch that introduced
this problem. I am not able to reproduce the crash with the
7.2.446 release. But I am able to reproduce the crash with Vim 7.3
version.
I found that the
Search for \v.*\/(.*)\n.*\/\1$ in a file with the following contents.
This should find adjacent lines with paths to files with the same base name.
With re=2 I get the first pair of lines highlighted (which is
nonsense). With re=1 I get a correct highlighting of the other pair.
#v+
On 15-Jun-2013 Mats Bertil Tegner mats.bertil.teg...@gmail.com wrote:
On 06/15/2013 03:10 PM, Bram Moolenaar wrote:
Patch 7.3.1196
Problem:Old regexp engine does not match pattern with backref correctly.
(Dominique Pelle)
Solution: Fix setting status. Test multi-line
as follows (both produce 1):
set re=1
echo string !~ regexp == . string(string !~ regexp)
set re=2
echo string !~ regexp == . string(string !~ regexp)
--
Lech Lorens
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
On 19 June 2013 12:31, Anton Konstantinov avtomorf...@gmail.com wrote:
May be this bug is not sufficient, but i spent a lot time trying to solve
this problem.
Thank you.
Have you tried increasing the value of 'synmaxcol'?
--
Cheers,
Lech
--
--
You received this message from the vim_dev
bar.bat
baz.bat
foo.com
bar.com
baz.com
foo.txt
bar.txt
baz.txt
#v-
creating 3 folds, 3 elements each. With re=2 it creates a single fold
containing all the lines.
--
Lech Lorens
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
On 26 June 2013 15:57, Charles Campbell charles.e.campb...@nasa.gov wrote:
mattn wrote:
Hi list.
[...]
I'm afraid that I don't see this problem with synax/vim.vim v7.3-25. You
can get a copy from my website:
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM .
Please try it out
, enter the visual mode and more some of the text,
5. open MS Notepad and press Ctrl-V (paste),
6. your console Vim has just crashed.
--
Lech Lorens
--
--
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
On 27-Jun-2013 Lech Lorens lech.lor...@gmail.com wrote:
[…]
Actually attaching the patch.
--
Cheers,
Lech
--
--
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
I discovered a problem with the 'scrollbind' setting which causes one of
the bound windows to scroll unexpectedly introducing an offset to the
bounding thus effectively destroying the desired setup.
The attached script scb-problem.vim when sourced will make the problem
apparent. The intention
On 30-Jun-2013 Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
I discovered a problem with the 'scrollbind' setting which causes one of
the bound windows to scroll unexpectedly introducing an offset to the
bounding thus effectively destroying the desired setup
is executed.
--
Lech Lorens
--
--
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
position, and your mapping eats it.
I think we can void the problem by doing the 'ambiwidth' check in the
second row instead of the first one. The returned sequence will then be
Esc[2;2R.
Just wanted to confirm that this problem indeed has been solved. Thanks!
--
Lech Lorens
--
--
You received
On 30-Jun-2013 Lech Lorens lech.lor...@gmail.com wrote:
On 30-Jun-2013 Bram Moolenaar b...@moolenaar.net wrote:
The fix seems OK. But the test already passes without it.
Yes, this is what I tried to explain above but somehow didn't make it
clear ;-)
Also, the test changes the window
On 10 July 2013 12:25, Bram Moolenaar b...@moolenaar.net wrote:
Milan Vancura wrote:
The biggest additions since 7.3:
- A new, faster regular expression engine.
- More than a thousand fixes and small improvements.
...and all the work about python? What's the current status, why it is
, people whose work
could replace what I have done (I have seen one of the issues in
todo.txt solved 3 times before it got removed from todo.txt) but this
doesn't make it any less wrong. I don't deserve it. And I don't deserve
to have this email ignored.
Lech Lorens
--
--
You received
:help :mksession states:
10. If a file exists with the same name as the Session file, but ending in
x.vim (for eXtra), executes that as well. You can use *x.vim files to
specify additional settings and actions associated with a given Session,
such as creating menu items in the GUI
Problem:
The cursor position is not updated after deleting a fold based on
markers. This results in an invalid memory reference in some scenarios.
How to reproduce:
In normal mode perform zRgg$zdaa while editing a file with the following
contents:
[[[
blah blah blah
]]]
vim: fdm=marker
Dnia 19-12-2008 Dominique Pelle dominique.pe...@gmail.com pisze:
Actually, testing a bit further, although your patch fixes
something (the valgrind error, and the crash for you), I still
observe something wrong.
I can reproduce the E38 error all the time. According to :help E38
it's an
The attached patch fixes 3 problems with folding in Vim:
1. Cursor position not being updated after deleting a marker fold
(details were provided in 20081217234549.ga23...@localdomain on
18-Dec-2008).
2. Folds being incorrectly refreshed after deleting a marker fold.
The problem was reported by
Dnia 26-12-2008 Matt Wozniski m...@drexel.edu pisze:
diff --git a/doc/usr_44.txt b/doc/usr_44.txt
index f5506b4..7aa324a 100644
--- a/doc/usr_44.txt
+++ b/doc/usr_44.txt
@@ -503,9 +503,10 @@ For example, add keywords that are not used in C:
This works just like in any other syntax
The attached patch fixes the problem with displaying the value of the NL
character in files edited with 'ff' set to mac. The solution was to
replace CARs with NLs when printing their values for mac-format files.
--
Cheers,
Lech
--~--~-~--~~~---~--~~
You received
The attached patch fixes the problem with highlighting not being removed
after r + CTRL-R is pressed in Visual mode.
--
Cheers,
Lech
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit
The attached patch causes the tab line to be redrawn with + indicating a
change to a file whenever 'bomb' is set.
--
Cheers,
Lech
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit
The attached patch gets rid of the unnecessary screen redraw when
'guifont', 'guifontset' or 'guifontwide' is set in Vim running in a console.
--
Cheers,
Lech
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit
On 31-01-2009 Dominique Pelle dominique.pe...@gmail.com wrote:
Lech Lorens wrote:
The attached patch makes it possible for the last argument in the
:cscope find [sgdctefi0-8] ...
command to be preceded by multiple spaces.
But isn't being able to search for something beginning
on 7.2). I'll
CC Lech. Lech, is there somewhere I can get the latest vim with your
patches included?
I do, but it also includes a number of other patches. I'll try to
extract the SmartTag
part tomorrow and put it somewhere on the web.
--
Pozdrawiam,
Lech Lorens
--
You received this message
Most of the Vim code is indented in the following way:
#v+
{
if (condition1
condition2)
action();
doit(arg1,
arg2,
arg3);
}
#v-
However, this has to be adjusted manually, because as close as Vim can
get automatically is with the setting cino=(0
On 27-Nov-2011 Scott Smedley sc...@smedleyfamily.net wrote:
Hi Christian,
I'm trying to debug another anomaly, but Vim crashes when I call
SmartTag#SmartTag(debug).
Can you provide an easy example of how to crash Vim?
Simply create source file from this link invoke
this out soon.
Like the idea.
Hate the syntax.
Have no clue what better syntax might look like.
--
Pozdrawiam,
Lech Lorens
--
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
On 16 January 2012 22:16, Christian Brabandt cbli...@256bit.org wrote:
Hi Dominique!
On Mo, 16 Jan 2012, Dominique Pellé wrote:
To fix it, we'd need to have a different syntax group for Subject: (without
spelling checking) and for the actual text of the subject right after it
(with
spell
request and added documentation; I do explicitly
mention the interaction with (N and wN.
I also added tests (which helped me find that the original
implementation behaved inconsistently at places and fix these
problems).
--
Pozdrawiam,
Lech Lorens
--
You received this message from the vim_dev
Hi,
I'm sending in a patch for what has recently bitten me: the setting of
ft=asm in a modeline overriding the setting of asmsyntax=foo in a
file's comment.
Perhaps adding such a note will save someone a headache.
Cheers,
Lech
--
You received this message from the vim_dev maillist.
Do not
confusing.
--
Pozdrawiam,
Lech Lorens
--
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
-w_buffer-b_mod_set)
{
# ifdef FEAT_WINDOWS
win_T *wwp;
it it the line that checks whether wb-w_buffer-b_mod_set is non-zero:
if (wp-w_buffer-b_mod_set)
wp-w_buffer is NULL.
--
Pozdrawiam,
Lech Lorens
--
You received this message from the vim_dev maillist.
Do
Hi,
There's a problem with tabpages and BufWinLeave autocommand: when
exiting a buffer which is displayed in the only window in a tab,
the autocommand fires already in a different tab. This can be shown by
executing the following commands in a new Vim session:
#v+
tabnew
tabdo windo echo Buffer
The attached patch causes Vim to handle pointer lines which consist of
a sequence of '-', '.', ' ' or tabs (I added tab handling; the rest was
obviously there).
As a result an error report like this can be handled correctly:
#v+
foo.c, line 234: undefined identifier Foo
for (foo = bar;
The attached patch adds the j flag to 'formatoptions' which is
described in todo.txt as follows:
7 Add 'j' flag to 'formatoptions': Remove comment leader when joining lines.
It makes it possible to perform a join on the following lines:
#v+
/*
* Comment
*/
#v-
to obtain:
#v+
/* Comment */
On 6 June 2012 17:15, Gary Johnson garyj...@spocom.com wrote:
I'm seeing some unexpected behavior from this patch.
$ vim -N -u NONE foo.vim
where
$ cat foo.vim
This is the first line
and this is the second line
- Now a list item
- A second list item
Add 'j' to
On 6 June 2012 19:35, Tony Mechelynck antoine.mechely...@gmail.com wrote:
Compiling gvim (Huge) wigh GTK2/Gnome2 GUI after applying patches 7.3.539 to
7.3.544:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
On 7 June 2012 16:09, David Pineau dav.pin...@gmail.com wrote:
Hello,
While configuring my indentation, I came across a behaviour that seemed
unintuitive to me (I did not manage to find anything related to this on the
mailling lists, sorry if I missed it).
When a value in the cinoptions
Hi!
Some time ago I remember being surprised that if in an assembly file
there's a modeline stating ft=foo and there's asmsyntax=bar
declaration, ft=foo will have precedence.
Perhaps adding a note to the documentation will save someone from
such a surprise. Find a patch attached.
Cheers,
Lech
On 7 June 2012 20:57, David Pineau dav.pin...@gmail.com wrote:
2012/6/7 Lech Lorens lech.lor...@gmail.com
Admittedly, I did not read the message carefully. I just fixed it to
find out that you already did that.
Next time just go ahead and attach the patch.
In my patch, I didn't update
Not terribly valuable input on the patch but I suppose this:
+ ) || curwin-w_buffer == NUL
should in fact read:
+ ) || curwin-w_buffer == NULL
Cheers,
Lech
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
On 25 June 2012 10:43, Kerneels Roos kerne...@gmail.com wrote:
Hi. What I meant is that if the TO field is consistently to the list then
all the filters work :) but if the list's email is in the Reply-To or in
the Cc fields then I have to create a new rule :) and do it in Thunderbird
since
On 13 June 2012 14:05, Bram Moolenaar b...@moolenaar.net wrote:
I wrote:
Patch 7.3.550 (after 7.3.541)
Problem: With j in 'formatoptions' a list leader is not removed. (Gary
Johnson)
Solution: Don't ignore the start of a three part comment. (Lech Lorens)
Files
The attached bash script crash.sh causes Vim to crash. I found where a
NULL pointer is being dereferenced and fixed it (find the backtrace at
the moment of the crash below at [1]). However (here's the question to
Tim Pope), if I apply the patch (the attached fix.patch) that avoids
the crash, I am
On 30 June 2012 13:01, Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
[...]
I can't see any spaces I wouldn't expect; for me there are only single
spaces at the joining points. Can you specify explicitly what would
you expect to be converted into what?
The example that Gary used
The attached patch makes it possible to move a tab X places to the right
by issuing:
:tabmove +X
and X places to the left:
:tabmove -X
A set of tests has been added and the undocumented possibility of
specifying the argument as :3tabmove has been removed to prevent the
inconsistency which
On 2 July 2012 20:12, Bram Moolenaar b...@moolenaar.net wrote:
Thanks, sounds useful. I'll add it to the todo list.
I do think we need to keep the existing behavior of :3tabmove, it's
consistent with using a count for an Ex command. Just document that the
+3 and -3 only work when the count
On 10 July 2012 23:36, I wrote:
[...]
I forgot to explain that the unpleasant scroll of the window contents
is caused by curwin-w_wrow being set to 0.
Calling win_new_height() inside f_winrestview() is intended to
recompute curwin-w_wrow.
Cheers,
Lech
--
You received this message from the
I have found a 100%-reproducible scenario in which Vim crashes. I work
on 2 computers sharing a mouse and a keyboard between them with
Synergy 2. One of the computers runs Windows 7 with Cygwin, the other
is running Linux.
Under Cygwin (no matter whether it is mintty or Cygwin/X with xterm;
it
On 13 July 2012 20:19, Dominique Pellé dominique.pe...@gmail.com wrote:
Lech Lorens lech.lor...@gmail.com wrote:
This may be too obvious, but have you made sure that you
compiled Vim with -O0 -g and made sure the the executable
was not stripped. Vim's makefile strips the executable
On 21 July 2012 16:45, Lech Lorens lech.lor...@gmail.com wrote:
On 20 July 2012 21:48, Bram Moolenaar b...@moolenaar.net wrote:
Lech Lorens wrote:
checkpath.patch contains a patch fixing the problem.
Thanks!
I found one more problem with :checkpath! and there are no tests
On 31 July 2012 21:36, Mikey smieciar...@gmail.com wrote:
Using C-c as a leader key breaks 'Does not trigger the InsertLeave
autocommand event'
I use GVim 7.3.600.
Steps to reproduce:
gvim -u NONE -U NONE
set nocompatible
au InsertLeave * :echo InsertLeave event triggered
nnoremap C-ca k
1 - 100 din 293 matches
Mail list logo
