Ah, confirmed. I can now reproduce it too on Linux
with Vim-7.3.138 in the terminal as well as with gvim (gtk2) with:
$ vim -u NONE -c 'set lazyredraw'
... then typing :verCR does not show anything.
I just came here to say the same thing. :messages and probably other
commands are also
Hi,
So here is a patch, that allows 99 capturing groups in
the replacement part. This uses the perl-like syntax ${1} until ${99}
for the capturing groups in the replacement part.
While I personally like seeing the limit lifted, I personally would
prefer named matching groups. This is how ruby
As you can see, the autoload script is loaded, even so vim shouldn't
need to. Is that the way autoloading is supposed to work or is this a
bug?
The line has to be parsed because how would you know if it isn't
an :endif. Maybe that's when the autoload function is loaded?
Anyway, you still can
Hi,
When code is evaluated in a sandbox, vim disallows using certain
commands and setting certain options. It doesn't disable setting
variables though.
Is there a way to mark a variable as security relevant so that code
evaluated in the sandbox isn't allowed to change it? Something like:
:let
Hi,
When I type
:echo eval('1.0')
I get an E806 error using Float as a String. This happens with gvim
7@ubuntu 10.04 as well as gvim 7.2.330 (the version that shipped
with ubuntu 10.04) built with gtk2-gnome features=huge. It doesn't
happen with the terminal version vim 7.3.5 and 7.2.330
Can you give the output of the shell command locale?
LANG=de_DE.utf8
LC_CTYPE=de_DE.utf8
LC_NUMERIC=de_DE.utf8
LC_TIME=de_DE.utf8
LC_COLLATE=de_DE.utf8
LC_MONETARY=de_DE.utf8
LC_MESSAGES=de_DE.utf8
LC_PAPER=de_DE.utf8
LC_NAME=de_DE.utf8
LC_ADDRESS=de_DE.utf8
LC_TELEPHONE=de_DE.utf8
I haven't had much trouble with filenames personally, as long as I stick
to forward slashes (which work on Windows) instead of backslashes (which
don't work on anything but Windows) and don't mangle user-provided
pathnames starting with drive letters on Windows. Could you be more
specific in
Which executable do you intend to execute in a cross-plattform
portable way?
(c)make/(b)jam/aap, gcc, doxygen, ctags, latex, ...
In my experience the major problem with running external apps like
those listed above is filenames -- e.g. when I use cygwin tools from
windows gvim or when I
llor...@neo ~ $ which cmd
llor...@neo ~ $ type cmd
-bash: type: cmd: not found
This seems to answer the question of portability of using cmd ;-)
Which executable do you intend to execute in a cross-plattform
portable way?
--
You received this message from the vim_dev maillist.
Do not
In your watchlist, click the link: Edit raw watchlist
I believe you could just add lines like the following:
Script:123
Script:4321
Is this trick still possible? I remember having edited the raw
watchlist before but now I cannot find the right link. I cannot seem
to edit
Hi,
Using
set columns=1000 lines=1000
is a commonly used trick to maximize gvim's window. If I execute this
line twice:
set columns=1000 lines=1000
set columns=1000 lines=1000
the command line vanishes and vim behaves as if it actually had that
much space available.
Version: 7.2-330
Hi,
When I run gvim -u vimrc0 where vimrc0 is
set nocp
echom serverlist()
I get different results for gvim on windows (the list contains GVIM)
and on linux/gnome (the list is empty) -- assuming that no other
instance of gvim is running.
I'd expect serverlist() to behave the same on windows and
Log in as other than root, and you'll see gvim for Linux set itself up
as a server too (if, of course, it is compiled with +clientserver).
I didn't mean that it doesn't set itself up as a server but that on
windows the server is registered rigth from the start (i.e. before
sourcing vimrc any
Hi,
I have just noticed that vim allows to use ** as regular expression.
Shouldn't this throw a Nested * exception like .** does?
Examples:
echo match(abc, **)
= 0
echo match(abc, .**)
= E61: Nested *
Regards
Tom
--
You received this message from the vim_dev maillist.
Do not top-post! Type
Attached patch provides clean up required.
ruby_dyn3.txt
This seems to work. I had to make a few changes to Make_cyg.mak in
order to compile it with USE_DLL=no.
BTW since ruby 1.9 tends to break code ruby written for ruby 1.8, I
think there should be an easy way to query ruby's version
I am not sure I understood you correctly. Compiler detects Ruby
version at compile time already (see numerous #ifdefs in if_ruby.c).
And I do not think there is a point in detecting version at run-time:
it looks Ruby developers do not care of C code compatibility.
I currently use has('ruby')
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
gui elements. Hence, they have to be useful.
--
You received this
But what about spammers? I rememember there was an issue with comments
on 'Tips' on vim.sf.net.
IIRC you were able to post a tip or commment on a tip as anonymous
user without being logged in.
Since there already are several vim-related collaborative media in use
(vim-use, vim.wikia) I wonder
On the vim homepage/community, there is a link to http://vi-improved.com/wiki
The domain seems no longer to be active and is now redirected to a
GoDaddy page.
Regards,
Tom
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
It should be http://vi-improved.org/
This isn't the wiki though it once referred to. It seems to be rather
related to the #vim IRC channel, isn't it?
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
It would help if the items listed on the vim-patches page mentioned any
restrictions on OShttp://groups.google.com/group/vim_dev/web/vim-patches
BTW what is the procedure to determine whether these patches are ever
included in vim? Since some of these patches were written for older
versions
The procedure is straightforward: Bram M decides whether a patch goes
into the vim source.
When I asked Bram about that particular patch he said that there were
some problems with it and that he waited for a new version that solves
these issues. These problems were reported by the author of the
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if both plugins should be merged.
WinZip (for instance) can uncompress .gz files as an easy preliminary step.
7zip[1], which is GPL licensed, handles all formats well.
The point was though that vimballs cannot readily include binary data
which isn't all wrong I think.
[1] http://www.7-zip.org
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.
installing zip-based plugins basically is a matter of
exec '!unzip '. shellescape(expand('%')) .' -d ~/vimfiles'
Hi folks,
Maybe somebody has some use for this. I wrote a small ruby script that
allows the creation of vimballs (plain text or gzipped) from the
command line. It's still young and fresh and experimental. I ran it
over my own plugins and the generated vimballs are identical to those
created by
You can specify the base path with the final arg to MkVimball.
If you wanted to create vimballs from cygwin bash by calling Windows
gvim (you could of course use cygwin's vim but ...), you'd have to
convert the path which works most of the time but can be cumbersome.
But thanks for reminding me
On Feb 7, 1:00 pm, Ingo Karkat sw...@ingo-karkat.de wrote:
Which takes us back to the original topic of this thread: There are many
different plugins in various states (mostly of disarray), and it's hard for
users to judge the applicability and how well it is being maintained.
On Feb 7, 7:14
Luc, which unit testing framework are you talking about?
A vim.sf.net search points to
http://www.vim.org/scripts/script.php?script_id=1125
I once wrote
http://www.vim.org/scripts/script.php?script_id=1730
that is supposed to solve a similar purpose although it's still quite
minimalist.
So for a start, I am proposing a VimLib project, maintainable by the Vim
community, written entirely in VimL and except from one function (see
below) it will independent from the vim official distribution.
It's based on personal experiments and from the work
of Marc Weber and Luc Hermitte.
shell extension opening a file 'with existing vim' deletes current
file on current tab. then load the file in current tab.
I guess you could create a key in the registry HKEY_CLASSES_ROOT/*/
Shell/Open in Vim Tab/command and set (Standard) (a REG_SZ) to a
value you like, maybe 'gvim
Write a short overview in the style you can find on the wiki and send it to
the list (I think the wiki is still locked down, atm).
??. Display soft-wrapped lines flushed left at the proper
indentation level if 'linebreak' is set
Author: Václav Šmilauer
Status: Almost complete, needs
Hi,
I noticed that the breakindent patch[1] isn't listed on the vim patch
page. I've been using this patch for a month now and it works great
(for me). Unfortunately, I cannot find the original post that
contained the patch. IIRC the author listed a few gotchas -- I assume
he tested the patch
33 matches
Mail list logo