On Jul 24, 8:02 am, Bram Moolenaar wrote:
> Nico Raffo wrote:
> > Due to a syntax change between python 2 and python 3, there is no way
> > to insert a new line at an arbitrary line number into a buffer using
> > the python interface without using undocumented parameters in
ffer.insert() method if people
think it's a good idea.
Nico
--
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 Jul 22, 5:18 am, James Vega wrote:
> On Thu, Jul 22, 2010 at 12:36:27AM -0700, Nico Raffo wrote:
> > If Vim is compiled with both --enable-pythoninterp and --enable-
> > python3interp, errors occur when importing many python modules. To
> > reproduce, compile as describ
t the bottom of
http://docs.python.org/extending/embedding.html
without much luck.
Nico
--
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
ll from hg repository. Built with --with-
features=huge --enable-pythoninterp --enable-python3interp
Nico
--
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
ow if you move the cursor down the line, it skips over the "c"
character. Also, if you put the cursor on "d" and run getpos(".") you
get the incorrect value "3"
Nico
--
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
2.6 as well, whenever the next one is built?
Nico
--
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
ds barely work and suck up too much cpu.
If I knew C I would attack these myself, but until then thanks for
considering this request.
Nico Raffo
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
er as part of VimL or only the
python interface would be terrific.
This and not having a keypress event have been my two largest
obstacles with plugin coding.
Nico Raffo
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
On Dec 7, 3:46 am, Dominique Pellé wrote:
> Nico wrote:
> > After receiving several bug reports from users in one of my scripts, I
> > came across this strange behavior. If GVim is being run in a different
> > language, most functions cannot be called with floating point num
F-8
GDMSESSION=gnome
SPEECHD_PORT=7560
SHLVL=1
HOME=/home/nraffo
LANGUAGE=de_DE.UTF-8
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
LOGNAME=nraffo
XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-
P3ijeYIX6T,guid=xxxxxx
DISPL
After receiving several bug reports from users in one of my scripts, I
came across this strange behavior. If GVim is being run in a different
language, most functions cannot be called with floating point numbers
as arguments. Here are the steps to reproduce:
file: test.vim
: garbage_collect() now contains a single step labeled "1." --
perhaps get rid of the number?
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Hi Bram
On 05.05.2009, at 03:41, Bram Moolenaar wrote:
> Nico Weber wrote:
>
>> Valgrind memory checker finds several errors in vim-7.2 (patches
>> 1-148) with the reproduction steps described at
>> http://groups.google.com/group/vim_mac/browse_thread
commented line
> PROFILE_CFLAGS = -DEXITFREE in src/Makefile)
> so normally all blocks should be freed when exiting.
Thanks for checking.
I've attached an updated version of the patch that fixes some of the
leaks. The copy()d dicts in the script don't get freed, but I don
t. When the previou_funccal list is freed, these dictionaries and
lists are freed a second time.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
F
column's background? That'd be
awesome (I believe there is a line drawing function already that is
used to draw the squiggly lines below misspelled words in gui mode).
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev&qu
> This patch is completely rewritten, with very little in common with
> the previous one. Again, some review is much needed. I didn't adjust
> the documentation; is it customary for me to do that, or to have Bram
> do it?
That&
GUI frontend process). The mapping
from vim processes to MMVimController objects is done by
MMAppController (connectBackend:...).
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
> This code looks OK to me. Maybe it's a bug in gcc or maybe this
> construction is just not portable. I suspect it's a bug in gcc but
> I'm not 100% sure.
Isn't it better to file this as a bug with gcc?
--~--~-~--~~~---~--~~
You received this message from the "vi
24d7d32cb17fc1cefb0c61bd2 was
> committed to
> macvim/master instead of macvim/vim. Maybe there are some more?
> Anyway, I
> tried it for interest and the first conflict where git am failed was
> at patch
> 290 out of 672.
As far as I know, macvim/vim conta
t;.shellescape(fname,1)." ".redir)
exe "silent !open ".shellescape(fname,1)." ".redir
If I remember correctly, you added that about a year ago after I sent
you a patch. So I guess the wiki is just outdated.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
oblem happens more often than it should, I
have the following in my .vimrc (all one line):
command QPd %!python -c 'import fileinput, quopri; print
quopri.decodestring("".join(list(fileinput.input('
It converts the current buffer from quoted-printable to normal text.
t line 444, you could use
:match Error /\%444l/
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
?
== acts according to 'ignorecase'. Use ==# to always compare case-
sensitively. See `:h ==#` for more information.
HTH,
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ut I didn't feel I had to do the
> switching for now... :-)
Fair enough. If you submit a patch to MacVim, it's usually merged in a
few days instead of a few months, though.
Nico
--~--~-~--~~~---~--~~
You received this message from the &quo
//groups.google.com/group/vim_dev/browse_thread/thread/4e3ce55c4a833e66/53cb9dbeb302a499?lnk=gst&q=2.1#53cb9dbeb302a499
and http://code.google.com/p/nerdcommenter/issues/detail?id=17 .
Thanks for reporting it anyways :-)
Nico
--~--~-~--~~~---~--~~
You rec
Hi,
> but that is not true. Reading the same file with a command like grep,
> takes 567msecs.
is it faster if you do `set swapsync=` and `set nofsync` before
reading the file? If so, ext3 is to blame:
http://taint.org/2008/03/12/122601a.html
without breaking
old scripts with just slightly awkward syntax" :-)
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ve the tabs a much nicer look (at least on GTK,
where most tabs include file icons. In OS X, tabs usually don't have
file icons, so I wouldn't want it in the OS X version).
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
), but `:h tabpagebuflist()` should get you started.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ay etc). Can you get in
touch with me to discuss this? (I didn't get your original mail, so I
don't have your email address).
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
n just grammar checking, you also
need type checking, checks if a variable is defined before use, etc.
>
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ibutors. It uses a
library-based design, so you could run only the parser and not the
type analysis for example.
Writing your own frontend is madness :-)
The real challenge is to come up with a general interface between vim
and the languag
nage to create a flexible on-the-fly code checking
system with an example code-checker for C based on clang (that'll also
provide C++ and Obj-C support), that'd be quite useful.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_
bly already is a currency conversion lib available in
python. Chances are, in vim there's none.
The again, you're the Bram ;-)
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
e the results if you just do `gvim[-re].exe -u NONE -U NONE -c
wq!`?
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
e used as
a = PUSH(s);
or in other places where an expression is expected. If you convert the
macro to a function, it should work on all compilers (and I guess it
won't even be slower since the compiler will inline the function call
automatically).
Nico
--~--~-~--~
t be
bothered to check that ;-)
Tcl does do a longest match, Javascript does the same as Python, Ruby
and Perl (at least the Spidermonkey implementation; the spec suggests
that this is correct (
http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf
, 15.10.2.3)).
> I have never invoke functions in the ``:s/'' before.
If I understand you correctly, \zs might be even easier in this context:
:%s/d\.%\zs/0/g
See `:h \zs`.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information,
windows box...
There surely is a distribution-dependent way, that's "easy" (where
"easy" means "similar to windows"). For example, I'm sure you can
upgrade Vim through the add/remove programs dialog in Ubuntu. But
uncompressing the sour
that function set col to 0?
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
on which you
> want to
> operate, you can use an ex-command with a range, such as
>
> :2435,2457d
Most of the time it's even faster to use v/ (and perhaps 'n' a few
times) to jump to the line where you want to go in my experience.
Nico
--~--~-~--~---
);
Adding an explicit cast makes the warning go away:
sprintf((char *)num, "%d", (int)STRLEN(xp->xp_pattern));
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
> Is this close enough?
> :command BDP bp | bd #
> :command BDN bn | bd #
Yes. Thanks :-)
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
was my ignorance preventing me from deleting buffers without
> closing the split window that's holding it
I'd like to have that too.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ts even discovery, authenticaion and security are problems
you have to deal with locally as well. (I'm not saying doing this over
the web doesn't make it quite a bit harder, but I don't see any value
in this feature without web support.)
>
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
> - add collaborative editing: changes made to a file show up in another
> Vim in a second
Do you mean "changes to a file" (ie. contents are only synced on file
write) or do you mean "changes to a buffer" (ie collaborative real-
time editing ov
Hi,
you can use '\*' to match a literal '*' (with 'magic' set). I can't
find this mentioned anywhere in the documentation. User error or
missing documentation?
Thanks,
Nico
--~--~-~--~~~---~--~~
You received this message fr
or in front of "\|" or "\)" ("|" or ")" after "\v"):
matches end-of-line ; at other positions, matches literal '$'.
I'm having the impression that $ in front of "\n" and "\%(" matches
as well. Must
> Ted Pavlic mentioned on the vim-mac list that --remote-tab-silent is
> not mentioned in the --help output and suggests to add it. I think
> that's a good idea. What do you think?
There has been some positive feedback on this, so here's a patch to
imple
Hi all,
Ted Pavlic mentioned on the vim-mac list that --remote-tab-silent is
not mentioned in the --help output and suggests to add it. I think
that's a good idea. What do you think?
Nico
--~--~-~--~~~---~--~~
You received this message from the &qu
nsell_color_system
)? It's a (the?) color system based on perceived colors, so perhaps
is coul be used for your purpose.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
roficient in this kind
> of code, so I'm thankful for comments.
For the records: The patch had one serious problem, but a fixed
version is now included in MacVim and seems to work.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_de
Hi,
I'm using the Taglist plugin version 4.5. If I open a taglist window
with `:Tlist` in one tab, switch to another tab and back again, I get
Error detected while processing function
17_Tlist_Refresh_Folds:
line 24:
E16: invalid range: 67,145fold
>
> setf objc
> elseif exists("c_syntax_for_h")
>setf c
> elseif exists("ch_syntax_for_h")
>setf ch
> else
>setf cpp
> endif
> endfunc
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
e.vim that adds objc detection for .h
files. I don't know if this is of general interest, but I think so.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
objc.patch
Description: Binary data
ordinary regex patterns with 'magic' set are accepted. Everything
except branches seems to work (I tried character classes and
wildcards), but the above does not. Is this a bug, or am I missing
something?
Thanks,
Nico
--~--~-~--~~~---~--~~
Yo
the "hit enter" prompt is not in
the last line (i have 'lines=50')? Do you have Focus* autocommands set?
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
> Patch 7.1.160
> Problem:When a focus autocommand is defined, getting or losing
> focus
> causes the hit-enter prompt to be redrawn. (Bjorn Winckler)
> Solution: Overwrite the last line.
If you do `:intro` and lose or gain focus, the problem still
;
> I just tried it and saw no problem -- the cursor was atop the
> "." (using
> either vim or gvim, BTW) as expected.
>
> (I'm using FC5 Linux, vim version 7.1 patches 1-162, huge)
FWIW, I can reproduce it (vim 7.0.234 and MacVim 7.1.156).
Nico
--~--~-~--~---
forks and exec()s a new (!) vim instance in the child process. But if
the gui is started via `:gui`, no forking is done. I did some basic
testing and it seems to work, but I'm not very proficient in this kind
of code, so I'm thankful for comments.
This should work for all vim g
nother process. Apart from that, you only need to look
at the required modifications to vim's core (macvim-*-patch.tar.gz in
the downloads section). But it's still a lot of work.
Sorry for the bad news :-|
Nico
--~--~-~--~~~---~--~~
You received t
as ignored
completely. So this is a general vim bug, not a MacVim bug.
Another thing I noticed: If I write "neccessary" and `:set spell`, z=
suggests "Necessary" but the popup menu suggests "necessary". Is this
intentional?
Nico
--~--~-~--~~
> 1. The snapshot archives contain multiple items at the top level.
> This is fairly
> nonstandard IMHO
This is the normal way of packaging stuff in OS X because
BOMUnarchiver (the program the finder invokes when you double-click a
zip) creates a folder with the name of the zip for you.
-
dy), it's just
something that might be useful to other people. I'm sure you can tell
git to ignore config.h and friends when generating patches too.
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Hi all,
everytime I do some hacking on vim, I put my modified files into a
local svn repository -- which is a bit cumbersome. I found this
article today: http://live.gnome.org/GitForGnomeDevelopers This
sounds as it could be very useful to other people working on vim as
well.
Nico
> (the last screenshot shows that the "new" character is drawn twice:
> once at its original position, and once one to the right). The file I
> used for testing is attached.
FWIW, it's in utf8.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" ma
I
used for testing is attached.
I'd vote for using this patch and working on the display problems
after that (except for the windows case, these display problems
already exist with the current version, as the first line in all
screenshots shows).
Nico
--~--~-~--~~-
> Apparently, it happens with plain vim (taken from svn). file-opened-
> in-another-session is a file which I have open in another Vim[*]
> window (application). Application just crashes.
The official version works for me (I did `gvim ~/_vimrc` twice,
worked fine).
--~--~-~--~~---
tta <[EMAIL PROTECTED]> wrote: _open_osfhandle()
> is defined in io.h as:
>
> io.h:int _RTLENTRY _EXPFUNC _open_osfhandle(long __osfhandle, int
> __oflag);
>
>
> Nico Weber <[EMAIL PROTECTED]> wrote:
> > I was thinking the same thing but I just wanted to let
that fixes this, let's see what the cleanest fix is...
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
> Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
> .\if_cscope.c:
> Error E2451 .\if_cscope.c 912: Undefined symbol 'intptr_t' in
> function cs_create
> _connection
> Error E2121 .\if_cscope.c 912: Function call missing ) in function
> cs_create_con
> nection
> Error E2121 .\if_c
minal version survives somehow.
>
> Any thoughts?
I think you've come to the right place.
does it work with the unpatched version? If so, Jigod can probably
fix this (he's the author of that patch). I believe he's monitoring
this list.
HTH,
Nico
--~--~-~--~-
, MacVim is mainly about the gui version of
vim. It's a rewrite of the GUI using different technologies. Making
the clipboard work in an xterm/Terminal.app could probably done with
the "normal" mac vim version without too much effort.
Nico
--~--~-~--~~~
do it for hlsearch either atm. Even if
this is not done, the default (!) colorscheme should Just Work. And
if we expect each and every colorscheme author to manually take care
of this, we can be sure that there are going to be lots of
colorschemes that don
in the same line as the error, Errors are displayed
with a light grey background and white text -- barely readable
(tested on gvim/ubuntu and carbon vim/osx).
Any ideas what could be done about this?
Thanks,
Nico
--~--~-~--~~~---~--~~
You received this message
>> Like Nico says, clipboard support is in all versions of Vim on the
>> Mac.
>> For instance, in MacVim.app check out the following functions in
>> gui_macvim.m:
>
> So this isn't in the official Vim distribution, correct?
It works in the official Carbon vi
ed, I
> wondered whether it would be easy for me to contribute by adding the
> functionality to Vim--perhaps even to be available only when
> 'encoding=utf8', which would be better than nothing!
Well, if I understand you correctly, this already does work. I didn&#x
> Try it out on the Vim search page (second box from the top):
>http://www.vim.org/search.php
Very nice. A bit feature-laden perhaps ;-)
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more informa
ith --enable-multibyte. This
option works for me...where did you get your source from?
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Hi,
> As a result, I understood 1% of the code and had a 'behaving` pum,
> which only redraws the screen at the start,end and when hiding the
> pvw.
> If there is any interest, I can post that patch.
I am interested.
Nico
--~--~-~--~~~---~--~-
then modify the char*, you get undefined
behaviour (I guess this is not a problem now, but if searchpath() is
changed to modify its argument array in the future, then this will
introduce a bug). I don't know if this is true in C as well, does
someone know?
Nico
--~--~-~--~~--
> Actually, I think I would make the strong claim that what I am
> talking about is not just some personal preference, but a fairly
> universal one.
FWIW, I prefer the current behaviour :-P
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" mailli
> Problem:Unnecessary screen redrawing. (Jjgod Jiang)
> Solution: Reset "must_redraw" after clearing the screen.
Yay! :-)
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.ph
IS_SPECIAL in
keymap.h for example. `:vim /IS_SPECIAL/ *.c | cw` shows you a 'few'
example calls ;-)
HTH,
Nico
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
86 matches
Mail list logo
