2010/11/29 Bram Moolenaar b...@moolenaar.net:
Pádraig wrote:
Ensure vim is not recursively invoked (man-db does this)
when doing ctrl-[ on a man page reference
Shouldn't that be ctrl-] ?
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
On Mon, Aug 23, 2010 at 4:45 PM, ZyX wrote:
Ответ на сообщение «Re: [BUG] Being provided some equal recursive structures,
equality operator never stops comparison»,
присланное в 17:34:55 23 августа 2010, Понедельник,
отправитель Adrien Axioplase Piérard:
But in vim, you cannot use assignment
On Tue, Aug 17, 2010 at 5:26 PM, Bram Moolenaar wrote:
Björn Winckler wrote:
I for one would be very happy if the next version (vim74?) used this
scheme (i.e. where all new work happens on the default branch).
In my opinion the default branch should contain the stable version.
Most users
2010/8/14 Dominique Pellé dominique.pe...@gmail.com:
* I did set mouse=a. I can use the mouse to position the cursor
and mouse also works fine with Netrw (clicking on directories opens
them...). However, I cannot use the mouse to resize Vim's windows
(nothing happens when I click the
On Wed, Jul 28, 2010 at 9:20 AM, Ingo Karkat sw...@ingo-karkat.de wrote:
Sorry, I haven't tried your patch yet, only reviewed it. I'd like to point out
the naming peculiarities for ftplugins (:help ftplugin-name), which I think
require additional filtering of the retrieved *.vim names:
| The
On Wed, Jul 28, 2010 at 9:24 PM, Benjamin Fritz fritzophre...@gmail.com wrote:
On Wed, Jul 28, 2010 at 3:39 PM, Bram Moolenaar b...@moolenaar.net wrote:
The documentation clearly says:
By default, HTML optimized for old browsers is generated. If you prefer
using
cascading style sheets
On Tue, Jul 27, 2010 at 9:17 AM, Dimitar DIMITROV wrote:
I tried with Vim 7.3b and the problem is gone when cursorline is on but I
still
find it strange that vertical bars and stars would appear when highlighting
the
text. It may be relevant for other filetypes but I don't think it is for
On Tue, Jul 27, 2010 at 12:12 PM, Matt Wozniski wrote:
On Tue, Jul 27, 2010 at 9:17 AM, Dimitar DIMITROV wrote:
I tried with Vim 7.3b and the problem is gone when cursorline is on but I
still
find it strange that vertical bars and stars would appear when highlighting
the
text. It may
To reproduce:
:echo repeat([{'a':'1'}], 2)
[{'a': '1'}, {...}]
expected output: [{'a': '1'}, {'a': '1'}]
:echo repeat([[0]], 2)
[[0], [...]]
expected output: [[0], [0]]
This seems to be caused by echo_string deciding that the data
structure is recursive, despite the fact that it definitely
On Fri, Jul 23, 2010 at 2:06 PM, Nikolai Weibull n...@bitwi.se wrote:
On Fri, Jul 23, 2010 at 19:33, James Vega james...@jamessan.com wrote:
On Fri, Jul 23, 2010 at 1:25 PM, Nikolai Weibull n...@bitwi.se wrote:
Sort of like a modeline?
Sort of, except modelines can be at the top or the
Please bottom post on this list... I'm reformatting...
On Wed, Jul 21, 2010 at 6:05 AM, mikeyao yaoweiz...@gmail.com wrote:
On Jul 21, 5:38 pm, Bram Moolenaar b...@moolenaar.net wrote:
Mikeyao (?) wrote:
Why not javascript interface ?
The code has developed.
On Wed, Jul 21, 2010 at 10:11 AM, duffman wrote:
Hi,
I tried to look up information online on this but wasn't able to find
anything that worked. I used Vi at my old job and loved the editing
features it provided. I've moved to a new place now and I am the only
developer here. I logged
On Wed, Jul 14, 2010 at 4:57 PM, Bram Moolenaar wrote:
Matt Wozniski wrote:
[about a patch to support #rrggbb in a terminal]
Where can I find the latest version of this patch? I only see one that
is two years old.
As Benjamin Haskell noted, I decided to shoot for a vimscript
On Thu, Jul 8, 2010 at 6:55 PM, Tony Mechelynck wrote:
If you want to usefully contribute memory leak reports, please use the
latest version, either the latest stable version (currently 7.2.445) or the
bleeding-edge development version (7.3a, available only over Mercurial, not
as a bz2
On Thu, Jul 1, 2010 at 10:55 AM, ZyX wrote:
Ответ на сообщение Re: Bug: Making sc abbreviation is not possible,
присланное в 00:10:21 01 июля 2010, Четверг,
отправитель Bram Moolenaar:
Most likely has something to do with keyword characters, since
'iskeyword' has a different value in help
On Tue, Jun 15, 2010 at 9:08 AM, Vince Negri wrote:
From: Dominique Pellé [mailto:dominique.pe...@gmail.com]
Thinking about it further, this second attached patch
also fixes the fold column redraw bug with less redraws
than patch in previous email.
However, unlike previous patch, it does
On Sun, Jun 6, 2010 at 4:26 PM, Bram Moolenaar wrote:
James Vega wrote:
On Sat, Jun 05, 2010 at 10:37:39PM +0200, Patrick Texier wrote:
Le Sat, 05 Jun 2010 16:16:06 +0200, Bram Moolenaar a écrit dans le
message 201006051416.o55eg6to002...@masaka.moolenaar.net :
Patch 7.2.442 (after
On Tue, May 25, 2010 at 4:53 PM, Bee beeyaw...@gmail.com wrote:
On May 25, 1:19 pm, Tony Mechelynck antoine.mechely...@gmail.com
wrote:
On 25/05/10 18:03, Bee wrote:
Is this a bug? Seems inoremap is not working here.
I recommend
:set timeout timeoutlen=5000 ttimeoutlen=100
(or
On Tue, May 18, 2010 at 11:04 AM, Cesar Romani wrote:
On 18/05/2010 04:24 a.m., Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout the
web in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're
On Tue, May 4, 2010 at 8:14 PM, Tom Sorensen wrote:
On Tue, May 4, 2010 at 7:14 PM, Paul LeoNerd Evans
leon...@leonerd.org.uk wrote:
Over the past 7 years, I have been a member of the #vim channel on
Freenode. Almost every week we get somebody in the channel who wonders
such things as how to
On Wed, May 5, 2010 at 11:20 AM, Ben Fritz wrote:
On May 4, 6:14 pm, Paul LeoNerd Evans leon...@leonerd.org.uk wrote:
Vim's keyboard input system revolves centrally around a queue of bytes.
This worked well when all the world was serial terminals. In this new
world of GUIs this model doesn't
On Mon, Apr 26, 2010 at 11:14 AM, Tom Sorensen wrote:
It was written by Matt Wozniski, not James. The issues I had with it
were that it would not perform correctly on both Windows and Linux. As
I recall (based on my log searches) it would do nothing the first time
you edited the file
On Mon, Apr 12, 2010 at 10:36 AM, Tom Link micat...@gmail.com wrote:
I believe this is a special case, that is mentioned at :h /star
Thanks. I missed that paragraph.
Regards,
Tom
O_o I never knew that one, either. Huh.
~Matt
--
You received this message from the vim_dev maillist.
Do
On Mon, Apr 12, 2010 at 5:45 PM, Lech Lorens wrote:
On 11-Apr-2010 Bram Moolenaar wrote:
Lech Lorens wrote:
While
10G
does add to the jump list,
:10
does not.
I believe that both the methods of moving from line to line should be
consistent with regard to the jump list. This
On Wed, Mar 17, 2010 at 9:51 AM, graywh gra...@gmail.com wrote:
I found a bug where Vim tries to set foreground/background color -1.
I noticed the issue when running Vim inside Tmux and
using :CSApproxSnapshot. Tmux doesn't handle the escape sequences
(\E[3-1m and \E[4-1m) the same as Xterm
On Fri, Mar 12, 2010 at 6:19 AM, Tom Link micat...@gmail.com wrote:
Maybe it /would/ make GVim more attractive if it had, let's say, a
more modern toolbar.
Maybe MS Office like ribbons would help to improve vim's popularity.
I've been told that a future version of OpenOffice will have similar
2010/3/10 Dominique Pellé dominique.pe...@gmail.com:
SungHyun Nam wrote:
Hello,
With the attached files (vimrc and mb.txt), if I open the mb.txt
and just type A,
gvim -u vimrc -U NONE --noplugin mb.txt
A,
Now, I should saw (X = cursor):
,X
But, I saw
, X
On Sat, Feb 27, 2010 at 2:39 PM, Jean Johner jean.joh...@cea.fr wrote:
On Feb 27, 1:54 pm, Bram Moolenaar b...@moolenaar.net wrote:
If I understand you correctly, that's the selection mechanism that lets
you copy text from the screen to the command you are typing.
Hello Bram,
What I wanted
Is it intentional that moving the cursor by clicking the mouse doesn't
modify the jumplist? It seems strange that you can't jump back to
where you were before clicking with `` for instance. You can get
around it with a mapping like
noremap LeftMouse m'LeftMouse
but that seems like it
On Tue, Jan 5, 2010 at 8:52 AM, Sergey Khorev wrote:
Hi,
has(win64) returns 0 even for x64 version of Vim. It seems we need
to define WIN64 for this to work. Something like that:
*** ../vim72.323/src/Make_mvc.mak Wed Dec 23 09:36:54 2009
--- src/Make_mvc.mak Tue Jan 5 16:46:26
On Tue, Jan 5, 2010 at 2:17 PM, Sergey Khorev wrote:
Well,
Isn't that only checking the type of CPU that the vim binary was built
with, instead of whether it was built as an x64 binary? Or does
defining WIN64 cause an x64 binary to be built instead?
CPU in makefile defines target CPU.
On Thu, Dec 17, 2009 at 10:59 AM, ron wrote:
Hi, Peter -
Thanks, that is a help. I'm using KDE though, so maybe some DCOP
incantation or similar would be what I need?
wmctrl is window manager agnostic - its basic features should work in
just about every window manager. So, while you might
On Wed, Sep 23, 2009 at 11:02 AM, Nikolai Weibull wrote:
With
set backupcopy=auto
Vim on Cygwin 1.7 removes write permission when writing a file not
owned by the current user on a Samba share. I realize that this can
be a Cygwin (1.7) problem, so I’m mainly asking whether anyone else
On Thu, Sep 10, 2009 at 4:13 AM, John Beckett wrote:
Aleafs wrote:
:1,$ s/\t0\n/\n/g
Note that :% is a shortcut for :1,$
In a substitute, \n means two different things:
- In the pattern, it refers to a newline.
- In the replacement, it refers to a null byte (8 zero bits).
You can see
On Thu, Sep 3, 2009 at 7:13 AM, Bram Moolenaar wrote:
Perhaps we should use :py3, with the requirement that white space
follows. It's not perfect, but probably the best compromise.
Is :py_3 better? Looks strange.
- When Vim was compiled with Python 2.x :py3 gives an error
- When Vim was
On Fri, Aug 14, 2009 at 6:25 PM, Britton Kerin wrote:
I dislike this message. Also the one about the number of
files to edit. These make it hard (or impossible, when
doing things like 'view -M -') to make vim completely
silent for use for interactive stages in shell scripts and
the like.
On Wed, Aug 12, 2009 at 4:42 AM, Dimitar DIMITROV wrote:
Hi,
I just wanted to support all the complainers.
Even if the standard plugins do not slow Vim down, some of them are useless.
tohtml for instance produces code which is not compliant with any modern
standards. It is a shame to have
On Sat, Aug 8, 2009 at 4:49 AM, Ian00 wrote:
This looks like a bug that I've worked around. I've noticed in windows
vista that mapping alt keys doesn't work in ~/.vimrc. Mapping after
vim loads works fine, and creating a separate file with the mappings
and then sourcing it from an
On Mon, Jul 13, 2009 at 7:31 PM, Tony Mechelynck wrote:
On 14/07/09 01:08, James Vega wrote:
On Tue, Jul 14, 2009 at 12:46:37AM +0200, Tony Mechelynck wrote:
On 13/07/09 18:08, Ingo Karkat wrote:
The default window navigation commands are a bit tedious, I mapped
CTRL-JKHL to
go to the
On Mon, Jul 13, 2009 at 6:17 PM, Tony Mechelynck wrote:
On 13/07/09 18:00, Raúl Núñez de Arenas Coronado wrote:
Usually Vim is called modal because it can be in insert mode or
normal mode. I don't consider things like that. I prefer to consider
Vim as a command-driven application, one of
On Fri, Jul 3, 2009 at 2:28 PM, Thomas Rowe wrote:
Path completion on Windows and Unix are different regarding case
sensitivity. Given file './Blah' on Windows, vim command ':e btab' will
expand out to ':e Blah'. On Linux it does not expand, even though bash
does as I have 'set
Oops, accidentally sent this to Bram off-list.
Bram Moolenaar wrote:
Matt Wozniski wrote:
Bram Moolenaar wrote:
Any comments on adding the :unsilent command modifier?
Maybe we could add
a :msgonly modifier that behaves like :silent but does add to the
message history?
The message
On Sun, Jun 7, 2009 at 10:07 PM, Cesar Romani wrote:
Thanks a lot for your help.
Actually when I press backspace, it behaves like the cursor left and
when I press escape the characters left behind are deleted.
CTRL-h cannot delete either, neither :fixdel can fix the backspace.
But When I
2009/5/28 Raúl Núñez de Arenas Coronado:
Hi all :)
I don't know if this is my fault, my terminal's fault or a Vim bug. It
happens both in my distro's Vim and my self compiled Vim (which is
newer). Latest version showing this problem is 7.2.184, tested under a
terminal virtual and a Linux
On Tue, May 5, 2009 at 12:50 PM, Michael Hordijk wrote:
Vim doesn't seem to handle a comma in $HOME at all. In this case, $HOME
= /u/hordijk,spin strace shows that Vim seems to be doing some odd
parsing around the comma:
stat64(/u/hordijk/syntax/synload.vim, 0xbfa03e9c) = -1 ENOENT (No
On Fri, May 1, 2009 at 2:42 PM, Gary Johnson wrote:
On 2009-05-01, Bram Moolenaar wrote:
Pankaj Garg wrote:
On Apr 30, 9:30 am, Ben Fritz wrote:
On Apr 29, 11:42 am, Bram Moolenaar wrote:
The name 'guidecolumn' starts with gui, which is confusing, since it
also works in a
On Wed, Apr 15, 2009 at 1:18 AM, Dennis Benzinger
dennis.benzin...@gmx.net wrote:
Hi!
Am 14.04.2009 23:18, _Lone schrieb:
To set 'guidecolumn' you can do
:set guidecolumn=N
where N is the column. If N is 0 then guidecolumn is turned off. It is
highly unlikely that a user would want the
On 4/13/09, Gary Johnson wrote:
On 2009-04-14, Lech Lorens wrote:
The attached patch changes the default 'foldmethod' for the quickfix
window to manual.
I'm a little concerned about applying such fine tuning of individual
window behavior to the source code. If there is a general
On 4/13/09, Tony Mechelynck wrote:
On 14/04/09 00:50, Matt Wozniski wrote:
On 4/13/09, Gary Johnson wrote:
On 2009-04-14, Lech Lorens wrote:
The attached patch changes the default 'foldmethod' for the quickfix
window to manual.
I'm a little concerned about applying such fine tuning
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense of aesthetics, I'm not on a Mac.
Usually, yes - but lore tells of shells where test isn't POSIX
On Fri, Apr 10, 2009 at 10:53 PM, Tony Mechelynck wrote:
On 11/04/09 04:16, Matt Wozniski wrote:
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense
On Fri, Apr 3, 2009 at 11:51 AM, fREW Schmidt wrote:
It looks kosher, leading me to believe it may be some funky
mapping/abbrv you have in place. Do you experience the same
problem when you start with
vim -u NONE
If it does, then you'd have to track down which mapping is
impeding your
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Vim is now capable of displaying any Unicode codepoint for which the
installed 'guifont' has a glyph, even outside the BMP (i.e., even above
U+), but there's no easy way to represent those high codepoints by
Unicode value in strings: I mean,
On Sat, Apr 4, 2009 at 3:17 PM, Yakov Lerner wrote:
If vimscript functions had remark Added in vim7.1.129, it would be useful.
For example, if you want to know how portable the script is.
Probably not exactly what you're looking for, but I keep copies of vim
6.4.10 and 7.0.0 around just so
On Thu, Apr 2, 2009 at 2:57 AM, George V. Reilly wrote:
On Wed, Apr 1, 2009 at 11:23 PM, Ron Aaron wrote:
I am currently working on three OSes at the same time: Win32, Linux
and Mac OS/X - and I am using the same vimrc settings on all three.
Mostly the same, anyway.
One area which causes
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
commit e458c019b0ff0515259aebca8e04ce06b9a2646c
Author: Matt Wozniski m
On Tue, Mar 17, 2009 at 4:19 PM, Bram Moolenaar b...@moolenaar.net wrote:
Yakov Lerner wrote:
We have separae highlighting, StatusLineNC, for non-current.
I wish I had different *format*, too, for noncurrent statusline. I do
not think differnt format for non-current statusline is
On Fri, Mar 13, 2009 at 12:01 PM, Mike Williams wrote:
Matt Wozniski wrote:
This sounds like a very good idea to me. I don't know of any other
programs that allow you to change encoding used internally, and we
would be in good company if we chose to always use a unicode encoding
internally
On Sun, Mar 8, 2009 at 5:40 AM, Corinna Vinschen wrote:
On Mar 7 20:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
to run, as explained on my Windows HowTo
Hm. Support for using cygwin's gcc to do cross-compile
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
On 08/03/09 02:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote:
On 08/03/09 03:15, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
using the -mno-cygwin option of the Cygwin gcc
compiler and the appropriate corresponding option of the linker.
This option will be removed
On Sat, Mar 7, 2009 at 10:29 PM, Tony Mechelynck wrote:
On 08/03/09 03:49, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote:
[...]
The _option_ to compile native-Windows programs
using Cygwin gcc _is_ a useful thing, I can't imagine on what grounds
someone would
On Sat, Mar 7, 2009 at 9:21 PM, Steve Hall wrote:
On Sun, 2009-03-08 at 03:05 +0100, Tony Mechelynck wrote:
The only interest of Make_cyg.mak is to compile Vim binaries which
don't need Cygwin to run, using the -mno-cygwin option of the
Cygwin gcc compiler and the appropriate corresponding
Motif and Athena recognize the 'ToolTip' highlight group, and will
change the fonts and colors of the balloons popped up over toolbar
entries. However, the colors aren't used for the balloons popped up as
a result of a balloonexpr.
This patch fixes that issue.
~Matt
diff --git
On 2/17/09, Larson, DavidX S wrote:
Hello all,
I was working on my script when I ran across this unexpected behavior
with the if statement. The doc says:
:if {expr1} *:if* *:endif* *:en* *E171* *E579* *E580*
:en[dif]Execute the commands until the
On Tue, Feb 17, 2009 at 9:19 PM, Markus Heidelberg wrote:
Bram Moolenaar, 18.02.2009:
Markus Heidelberg wrote:
After reaching the end of the more prompt, hitting SPACE jumps out of
it. Add 'f' to avoid this problem and for consistency with 'b' in
scroll down a screen.
This also
src/fileio.c : vim_tempname() contains these lines:
if (GetTempFileName(szTempFile, buf4, 0, itmp) == 0)
return NULL;
/* GetTempFileName() will create the file, we don't want that */
(void)DeleteFile(itmp);
Is this really right? Is there any reason to call DeleteFile()
On Tue, Feb 10, 2009 at 9:48 PM, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
But let's not forget that they have significant disadvantages, too...
Vimballs made with new versions of the plugin don't work on older
vims.
There's been one problem with that -- 7.0 vimball doesn't
On Wed, Feb 11, 2009 at 11:06 AM, Tom Link micat...@gmail.com wrote:
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
IMHO reliance on compiled-in +python support
On Wed, Feb 11, 2009 at 7:29 PM, Tony Mechelynck wrote:
On 11/02/09 16:23, Matt Wozniski wrote:
[...]
Well, of course I didn't mean that we should add the features to the
zip format. Rather, I meant we should do something more like XPI -
create a zip file, rename it to .vba, and let vim
On Tue, Feb 10, 2009 at 4:35 PM, Charles Campbell wrote:
James Vega wrote:
I'm still curious what purpose vimballs serve over a standard archive
format like zip or tar.gz. From a distribution perspective, all they've
done is made my work harder when trying to include vim scripts in a
On Mon, Feb 9, 2009 at 5:56 PM, Andy Wokula wrote:
Here is another way to get the option names, it's basically
:set C-A
snip
The output is almost sorted and includes all and termcap as the
first two entries.
Wow. That is quite clever, I definitely wouldn't have thought of
that.
On Sun, Feb 8, 2009 at 11:40 PM, Garrett Whelan whaled...@gmail.com wrote:
I would like to be able to access all the variables at a given time in Vim
without necessarily knowing what they are. Basically everything you would
see if you typed :let and :set. So in increasing order of difficulty
Bram Moolenaar wrote:
Chris Littell wrote:
In the help file index.txt, the description for CTRL-W = should
mention that it also makes window widths equal. Right now it looks
like there is no command to do this until you see the detailed
description.
I'll make it: make all
:help 'path' says
- When using |netrw.vim| URLs can be used. For example, adding
http://www.vim.org; will make :find index.html work.
This, however, does not actually work (and hasn't since vim 6.4.10, at
least). Attached patch fixes.
~Matt
On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote:
On 06/01/09 12:31, anhnmncb wrote:
Hi, list, as title, if so, why can't many functions
still handle correctly with unicode? For example the func:
getline('.')[col('.')-1]
Can't return a charactor outside the range of ascii.
On 1/6/09, Tony Mechelynck wrote:
On 07/01/09 00:39, Matt Wozniski wrote:
On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote:
On 06/01/09 12:31, anhnmncb wrote:
Hi, list, as title, if so, why can't many functions
still handle correctly with unicode? For example the func
On 1/6/09, Tony Mechelynck wrote:
On 1/6/09, Matt Wozniski wrote:
echo matchstr(getline('.'), '\%' . col('.') . 'c.')
Again, col('.') is a byte index, not a column. What about virtcol('.')
instead?
Nope. \%15c is also a byte index, not a column (which is also
counter-intuitive, and brings
On Sat, Jan 3, 2009 at 11:27 PM, Adam Osuchowski wrote:
Cases like mbox files are not so rare. There are many examples of
simultaneously access to single file, but problem exists even without
concurrent modification.
A simple example: editing config file for some daemon. When vim
truncates
On Wed, Dec 31, 2008 at 8:11 AM, Tony Mechelynck wrote:
On 31/12/08 07:48, Matt Wozniski wrote:
On Tue, Dec 30, 2008 at 1:14 PM, Daniel Schierbeck wrote:
I hope there's a simple workaround.
Sorry I couldn't come up with the solution earlier on IRC, but after
some sleep, I think I see
On Tue, Dec 30, 2008 at 1:14 PM, Daniel Schierbeck wrote:
I have added several directories to my runtimepath, each corresponding
to a git repository. For example, I have a directory ~/Projects/vim-
rack that contains ftdetect/rack.vim and syntax/rack.vim. I'm able to
manually :set
On Sat, Dec 27, 2008 at 3:15 AM, Dominique Pelle wrote:
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce
On Fri, Dec 26, 2008 at 6:49 AM, Florian Rehnisch wrote:
Hi folks,
it is said, that translators are the best profreaders.
;-)
Sometimes, I make annotations. Let's see what I have:
# type: Plain
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce this are
complicated, and possibly very specific to the version of the runtime
files and such
On Thu, Dec 18, 2008 at 8:01 AM, Markus Heidelberg wrote:
When typing ^Vu and the codes above in terminal Vim, I always get these
squares, i.e. the characters cannot be displayed, in vim -g it works. Is
this a font issue?
Yes; your font just must be missing those glyphs.
Also, Konqueror
function! ReturnArgs(...)
return a:000
endfunction
Seems to work fine?
echo ReturnArgs(1, 2, 3)
SEGV
echo string(ReturnArgs(1, 2, 3))
function! MakeArgsDict(...)
return { 'args': a:000 }
endfunction
E685 Internal Error
echo MakeArgsDict(1, 2, 3)
SEGV
echo string(MakeArgsDict(1, 2,
On Mon, Dec 15, 2008 at 2:42 PM, Dominique Pelle wrote:
Matt Wozniski wrote:
function! ReturnArgs(...)
return a:000
endfunction
function! MakeArgsDict(...)
return { 'args': a:000 }
endfunction
I can reproduce that with vim-7.2.69 on Linux.
Following patch seems to fix it, but I'm
On Mon, Dec 15, 2008 at 4:49 PM, Matt Wozniski wrote:
On Mon, Dec 15, 2008 at 2:42 PM, Dominique Pelle wrote:
Matt Wozniski wrote:
function! ReturnArgs(...)
return a:000
endfunction
function! MakeArgsDict(...)
return { 'args': a:000 }
endfunction
I can reproduce that with vim
For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
vim -u NONE -N
:set Home? xHome?
t_kh Home ^[[1~
t_kh Home ^[[1~
:set Home=
:set xHome?
E518: Unknown option: xHome?
Is this intentional behavior? What's the point of
John Beckett wrote:
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize,
eg, xHome and Home as separate keycodes.
Perhaps the following is an explanation:
:help version7
/xHome
Previously Home and xHome could be mapped separately.
This had the disadvantage
Bram Moolenaar wrote:
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
That's a bug. This patch should fix it:
Yes, that seems to fix it for me, xterm on Linux.
~Matt
At :help :set-termcap, an example shows the command
:set M-b=^[b
This command does not work as expected when 'encoding' is set to
something multibyte. The reason seems to be that vim recognizes the
input bytes 0x1B 0x62 as a metafied 'b', and then stuffs 0xE2 into its
internal text buffers - a
On Tue, Dec 9, 2008 at 3:40 AM, Patrick Texier wrote:
Attached patch disallows 'encoding' in a modeline but not in secure
mode.
Looks like a good idea to me, especially since the vim help explicitly
says that 'encoding' should either be set in ~/.vimrc or not at all...
In fact, I think it
On Mon, Nov 17, 2008 at 6:02 PM, Dominique Pelle wrote:
2008/11/17 Dominique Pelle:
Hi
I observe a bug with the latest Vim-7.2.42 (huge) on Linux x86.
It's not recently introduced since I can reproduce at least with
Vim-7.1.314 which comes with Ubuntu-8.10. It only happens in
a terminal
On Sat, Nov 8, 2008 at 11:18 PM, Tony Mechelynck wrote:
Configure is supposed to check whether one of the system provided
string-move operations handle overlap. Here's what I see in the logs and
files produced by configure on my system:
snip
So I suppose mch_memmove should be used
On Tue, Oct 21, 2008 at 4:29 PM, Tony Mechelynck wrote:
On 21/10/08 13:53, Nikolai Weibull wrote:
Here's a patch:
Please apply your patches to the latest version of the file. In eval.txt
dated 2008 Sep 14, line, 4482 to 4489 are
...
within the help for remote_send(); IOW your pointer is 14
On Mon, Oct 13, 2008 at 8:37 PM, John Little wrote:
On Oct 14, 12:13 pm, frankjas wrote:
I have been encountering an intermittent coredump ...
I rebuilt vim from source with symbols after I stumbled on a
reproduceable test case today...
Brilliant.
follows. It looks like the field
On Sun, Sep 28, 2008 at 4:35 PM, Tony Mechelynck wrote:
On Sun, Sep 28, 2008 at 9:40 AM, John Hughes wrote:
I am trying to write a command that substitutes some Ascii characters
with a Unicode character. The following substitution works when
entered directly:
:%s/\.\.\./…/eg
However, when
These two functions ought to behave identically, but don't... For some
reason, the :catch never gets triggered for the Broken one.
function! Working()
try
let y = x
return y
catch /^Vim\%((\a\+)\)\=:E121/
Handle 'Undefined variable' errors
return 42
endtry
endfunction
1 - 100 din 134 matches
Mail list logo
