Christian Brabandt wrote:
Forwarding to vim-dev
On Mi, 29 Mai 2013, Ben Fritz wrote:
I like the proposal by glts myself:
- :set nonu nornu means: I don't want any line numbers;
- :set nu nornu means: I want to see only absolute numbers;
- :set nonu rnu means: I want to see only relative
Hello!
I've used an after/syntax/help.vim help file (see attached). I've also
just gotten around to upgrading to vim 7.3.1115.
I have noticed that the help is now excruciatingly slow -- and I've
tracked it down to the line
setlocal fdm=syntax
in my after syntax help file. Commenting
Ben Fritz wrote:
On Wednesday, June 5, 2013 12:55:00 AM UTC-5, kartikkg wrote:
Tried to mail to this ndrochips
@pcampbellafamily.mbiz but seems like that address is invalid.
It shows in his files as ndroch...@pcampbellafamily.mbiz.
Remove NOSPAM and it's a valid address.
I don't see any
Christian Brabandt wrote:
Hi Bram!
On Mo, 13 Mai 2013, Bram Moolenaar wrote:
Not. I only want to work with the syntax files that I have, which are
the distributed ones. I'm not going to download and install syntax
files for this test.
There are more than 500 syntax files, that should be
Jan Pobrislo wrote:
Glib inside gvim, since gtk+ uses glib internally. More precisely glib is
that part of gtk+ that does not deal with gui, so there's no gvim without
glib. (Unless there's implementation of gvim not based on gtk which I'm
unaware of).
A gvim can be compiled using motif under
OmnipotentEntity wrote:
On a as expected? That wasn't the behavior I was expecting. Sorry if it was unclear. I
expected the cursor to be on e at the end of line because I didn't expect :set cuc to modify
the cursor column (because it's not a motion.)
Having :set cuc modify the cursor
Ben Fritz wrote:
On Monday, March 18, 2013 2:18:57 PM UTC-5, Charles Campbell wrote:
Next: $hj moved the cursor to the . in the second line.
Next: set cucenter k
This ended up with the cursor on a. Again, this is what I'd expect --
because the cursor got onto the . via a vertical move
Charles Campbell wrote:
Hello!
I seem to have run into a font problem -- as in the font I was using,
Luxi Mono 10, is no longer a valid font.
Here's what happened:
* used gvim with Luxi Mono 10
* broke for lunch
* returned
* updated vim from 7.3.784 to 7.3.796
* Luxi mono font no longer
Michael Henry wrote:
All,
By default in Gvim, creating or destroying a vertical split
causes the left-side scrollbar to automatically be created or
destroyed. There appears to be some kind of timing-related bug
wherein Gvim is not always able to maintain the value of
'columns' at its original
Nazri Ramliy wrote:
This is a reply of an almost 3-year old thread (but still relevant :)
On Fri, Jul 30, 2010 at 4:19 AM, Bram Moolenaar b...@moolenaar.net wrote:
Nazri Ramliy wrote:
What if we had some helper command that dumps how the
current screen look like so that it can be compared
Dominique Pellé wrote:
On Mon, Feb 11, 2013 at 4:11 PM, Charles Campbell
charles.e.campb...@nasa.gov wrote:
Charles Campbell wrote:
Christian J. Robinson wrote:
On Fri, 1 Feb 2013, Charles Campbell wrote:
My vim's status:
* :set guifont=Luxi\ Mono\ 10 used to work (in fact, still
Dominique Pellé wrote:
Charles Campbell wrote:
and I cannot find a glibconfig.h under /usr/include (literally; I used the
find command).
Using xubuntu-12.10:
$ locate glibconfig.h
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h
$ apt-file search /usr/lib/x86_64-linux-gnu/glib-2.0
Charles Campbell wrote:
Christian J. Robinson wrote:
On Fri, 1 Feb 2013, Charles Campbell wrote:
My vim's status:
* :set guifont=Luxi\ Mono\ 10 used to work (in fact, still does on my
home computer)
*snip*
If your Vim is built with Motif, it simply will not be able to use the
new
Charles Campbell wrote:
Christian J. Robinson wrote:
On Fri, 1 Feb 2013, Charles Campbell wrote:
My vim's status:
* :set guifont=Luxi\ Mono\ 10 used to work (in fact, still does on my
home computer)
*snip*
If your Vim is built with Motif, it simply will not be able to use the
new
Bram Moolenaar wrote:
Ilya Esteban wrote:
[snip]
2) If you use a plugin or a customization that visually shows the
marks, you end up with visual garbage in your files (the old tags),
that you cant get rid of unless you delete viminfo or reuse the marks
in a different file.
Solving this
Bram Moolenaar wrote:
Lech Lorens wrote:
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
Bram Moolenaar wrote:
Patch 7.3.802
Problem:After setting 'isk' to a value ending in a comma appending to the
option fails.
Solution: Disallow a trailing comma for 'isk' and similar options.
Files: src/charset.c
Hello, Bram!
This patch appears to be missing from
Bram Moolenaar wrote:
Patch 7.3.806
...snip...
Hello, Bram!
7.3.806 is missing from ftp.home.vim.org .
Regards,
Chip Campbell
--
--
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
Dominique Pellé wrote:
Charles Campbell wrote:
Hello!
I upgraded from 784 to 798 -- (and am doing without gtk, so I'm using the
motif).
What should I do to eliminate the following two messages that I get when I
fire up vim:
Warning:
Name: subMenu
Class: XmCascadeButton
Illegal
Nazri Ramliy wrote:
On Fri, Feb 1, 2013 at 7:18 PM, Nazri Ramliy ayieh...@gmail.com wrote:
The patch do not include Christian's fix for the problem
reported by François Ingelrest.
Attached is the updated (and less buggy) toy patch that include
Christian's fix and test89, and also test90 for
Hello!
I upgraded from 784 to 798 -- (and am doing without gtk, so I'm using
the motif).
What should I do to eliminate the following two messages that I get when
I fire up vim:
Warning:
Name: subMenu
Class: XmCascadeButton
Illegal mnemonic character; Could not convert X KEYSYM
Christian J. Robinson wrote:
On Fri, 1 Feb 2013, Charles Campbell wrote:
My vim's status:
* :set guifont=Luxi\ Mono\ 10 used to work (in fact, still does on my
home computer)
*snip*
If your Vim is built with Motif, it simply will not be able to use the
new style fonts like Luxi Mono
+viminfo +vreplace +wildignore +wildmenu +windows +writebackup
+X11 +xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
Any help or suggestions about how to get Luxi Mono 10 back with gvim?
Thank you,
Charles Campbell
--
--
You received this message from the vim_dev maillist.
Do not top
-1.0.3'
No luck with Luxi Mono yet.
Regards,
Charles Campbell
--
--
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
Taylor Hedberg wrote:
Charles Campbell, Fri 2013-02-01 @ 11:30:47-0500:
Taylor Hedberg wrote:
Is the font *only* missing in Vim, or has it disappeared from other
applications as well? Does it show up under xfontsel and/or fc-list on
your system?
xfontsel : trying family, no luxi present
fc
James McCoy wrote:
On Feb 1, 2013 11:43 AM, Charles Campbell
charles.e.campb...@nasa.gov mailto:charles.e.campb...@nasa.gov wrote:
I've found some more out -- it appears that several directories and
files got changed so that only root had access. fc-list now shows
Luxi Mono fonts
Tony Mechelynck wrote:
On 01/02/13 18:11, Charles Campbell wrote:
James McCoy wrote:
On Feb 1, 2013 11:43 AM, Charles Campbell
charles.e.campb...@nasa.gov mailto:charles.e.campb...@nasa.gov wrote:
I've found some more out -- it appears that several directories and
files got changed so
Hello!
I don't know (yet) which patch was responsible, but one of the patches
from 785-796 has caused me to no longer have Luxi Mono 10 available
(scientific linux 6.3, huge). I tried reversing the patches, but the
resulting vim still no longer provides Luxi Mono 10. So, I'm now in the
Paul Ruane wrote:
Hi,
I asked on the Vim reddit (http://www.reddit.com/r/vim/comments/
17gg56/) if anyone knew how to achieve this with existing
functionality or plug-in but apparently not. I would simply like to
have the option, when relativenumber is turned on, to have the current
line show
Bram Moolenaar wrote:
I think the information is useful. Who is against showing the current
line number instead of zero?
Is the width of the column a problem?
Not if its optionally a part of relative numbering.
Regards,
C Campbell
--
--
You received this message from the vim_dev
Ben Fritz wrote:
On Wednesday, January 23, 2013 1:28:16 PM UTC-6, Dominique Pelle wrote:
Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.3.782
--- runtime/doc/options.txt 2013-01-23 18:24:48.0 +0100
***
*** 3518,3523
--- 3560,3569
to set
Bram Moolenaar wrote:
Patch 7.3.764
Problem:Not all message translation files are installed.
Solution: Also install the converted files.
Files: src/po/Makefile
*** ../vim-7.3.763/src/po/Makefile 2010-08-15 21:57:26.0 +0200
--- src/po/Makefile 2013-01-17
Charles Campbell wrote:
Hello, Marcin:
I've expanded on the idea of selectable LaTeX syntax suppression; I've
attached syntax/tex.vim and syntax.txt.
In particular, you'll be wanting to use
let g:tex_fast= 'M'
to suppress region-based LaTeX highlighting (except for math-associated
Hello!
I've put a new syntax/tex.vim on my website
(http://www.drchip.org/astronaut/vim/index.html#SYNTAX_TEX). It uses a
new optional variable, g:tex_fast, to allow for fast syntax highlighting
with LaTeX/TeX. I've included some additional text I'll be proposing to
Bram for inclusion in
Ben Fritz wrote:
On Wednesday, December 5, 2012 10:47:42 PM UTC-6, So8res wrote:
Oops, sorry, I was misunderstanding how synID* worked.
I've updated the patch to add the combine {what} to synIDattr, which is the
bare minimum we need here.
synID should definitely return only one ID in this
John Little wrote:
I've just spent a few hours trying to track this down. It was very frustrating
as vim's behaviour became unpredictable, though I think I know the cause.
Using :Decho went bananas until I found the comment that explained that
DechoTabOn was necessary, but even that was
Bram Moolenaar wrote:
Patch 7.3.718
Problem:When re-using the current buffer the buffer-local options stay.
Solution: Re-initialize the buffer-local options. (Christian Brabandt)
Files: src/buffer.c
Hello!
This patch hasn't been entered onto
Bram Moolenaar wrote:
Patch 7.3.717
Problem:When changing the font size, only MS-Windows limits the window
size.
Solution: Also limit the window size on other systems. (Roland Puntaier)
Files: src/gui.c
Hello!
This patch hasn't been entered onto
Bram Moolenaar wrote:
Patch 7.3.716
Problem:Error on exit when using Python 3.
Solution: Remove PythonIO_Fini(). (Roland Puntaier)
Files: src/if_python3.c
Hello!
This patch hasn't been entered onto
ftp://ftp.home.vim.org/pub/vim/patches/7.3/7.3.716 yet...
Chip Campbell
--
You
Charles Campbell wrote:
Bram Moolenaar wrote:
Patch 7.3.718
Problem:When re-using the current buffer the buffer-local options
stay.
Solution: Re-initialize the buffer-local options. (Christian Brabandt)
Files:src/buffer.c
Hello!
This patch hasn't been entered onto
ftp
Bram Moolenaar wrote:
Patch 7.3.725
Problem::aboveleft and :belowright have no effect on :copen.
Solution: Check for cmdmod.split. (Christian Brabandt)
Files: src/quickfix.c
Patches 716-725 are missing from ftp://ftp.home.vim.org/pub/vim/patches/7.3!
Regards,
Chip Campbell
--
You
Hello!
I've attached a patch which allows subdirectories with help. Actually,
the tags system already permitted subdirectories; what this patch does
is extend helptags to search through subdirectories, creating
appropriate tags.
The patch is experimental, and I've only tested it under Linux
Alexey Radkov wrote:
Hi.
I found another issue with vim sources syntax highlights.
In the following code:
fun! VimwikiLinkHandler(link)
let link = a:link
if link =~ vlocal: || link =~ vfile:
let link = link[1:]
else
return 0
endif
blah-blah
endif
Hello!
I will accept the
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 88 by j.kenton...@gmail.com: fn; jumps to top of document
http://code.google.com/p/vim/issues/detail?id=88
What steps will reproduce the problem?
1. Open a text file with more than one line
2. Move
Charles Campbell wrote:
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 88 by j.kenton...@gmail.com: fn; jumps to top of document
http://code.google.com/p/vim/issues/detail?id=88
What steps will reproduce the problem?
1. Open a text file
ngollan wrote:
Trying to use :e http://www.ietf.org/rfc/rfc1918.txt; without elinks causes
vim to try links with the -source parameter; links does not decode the stream, and dumps
a raw binary gzip stream into the buffer, which is at least inconsistent with the
behaviour of elinks.
Using the
ZyX wrote:
пятница, 19 октября 2012 г., 18:15:39 UTC+4 пользователь Charles Campbell
написал:
I would appreciate some feedback from folks about this proposed change.
My own linux systems use elinks rather than links. My understanding is
that web pages are typically in ascii, not compressed
Bram Moolenaar wrote:
Patch 7.3.684
Problem:make test does not delete lua.vim.
Solution: Add lua.vim to the clean target. (Simon Ruderich)
Files: src/testdir/Makefile, src/testdir/Make_dos.mak,
src/testdir/Make_ming.mak, src/testdir/Make_vms.mms
Friendly reminder: this
Christian Brabandt wrote:
On Tue, October 9, 2012 16:53, Charles Campbell wrote:
Bram Moolenaar wrote:
Patch 7.3.684
Problem:make test does not delete lua.vim.
Solution: Add lua.vim to the clean target. (Simon Ruderich)
Files: src/testdir/Makefile, src/testdir/Make_dos.mak
RH-maillist wrote:
Perhaps my bug-search foo is off, but can't find any posts on this.
When typing, or having / it gets into view = syntaxed, this in a file
vim
freeze. Ctr-C is only way to escape.
As more dots are added vim works like crazy.
To reproduce:
1. In a file with :set
Danek Duvall wrote:
snip
In os_unix.c, the path we trace through mch_FullName() grabs the cwd into buf
(an input parameter) with mch_dirname(), which succeeds, since it's just short
enough to fit into the 1024-byte buffer (with the trailing NUL). We then get
the strlen() of buf, returning 1023,
Simon Ruderich wrote:
On Wed, Sep 05, 2012 at 03:46:00PM +0200, Bram Moolenaar wrote:
Thanks for pointing me to this patch. It fixes a few tab related
issues I just noticed (and tried to fix - you saved me some time,
thanks).
Which patch is that, who sent it?
It's Dominique
Charles Campbell wrote:
Simon Ruderich wrote:
On Wed, Sep 05, 2012 at 03:46:00PM +0200, Bram Moolenaar wrote:
Thanks for pointing me to this patch. It fixes a few tab related
issues I just noticed (and tried to fix - you saved me some time,
thanks).
Which patch is that, who sent it?
It's
Dominique Pellé wrote:
Dominique Pellé wrote:
Hi
Attached patch fixes the following item in in :help todo:
==
:e ~brTab does not complete to :e /home/bram/. Would need to use
getpwent() to find all the matches.
, the erroneous variable still seems to be used.
A simple patch is appended.
Thanks! I've incorporated it into netrw v146l (but I haven't released
it yet, as I'm working to fix another problem).
Regards,
Charles Campbell
--
You received this message from the vim_dev maillist.
Do not top-post
Wensen Leung wrote:
I am writing Perl scripts using vim. I really love this software, and when I
find this bug, I really want it to be fixed right away.
The situation is:
platform: Ubuntu 12.04 LTS, terminal
case:
I split the screen into 3 parts used :vs under command mode, and each part of it
lines of the syntax/fasm.vim script. He may or may not pay
attention to this list. May I suggest that you forward a copy directly
to him.
Regards,
Charles Campbell
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Thomas Köhler wrote:
Hi Thilo,
snip
BTW, some files might not be changed because there is not much need.
I last changed uil.vim and prolog.vim in 2009 to support some new
feature available in vim (and uil.vim yesterday due to
Dominique's patch for @Spell support), and before that, I think I
Benjamin R. Haskell wrote:
snip
The hard part of supporting a given language in Vim is the first step:
writing the syntax file in the first place. Once there's a
relatively-complete syntax file (and most of the syntax files included
in Vim are fairly mature), the changes to that syntax file
Dominique Pellé wrote:
Hi
Attached patch adds @Spell to the runtime/syntax/ocaml.vim file
so that Vim only highlights spelling mistakes in comments and
strings when editing an ocaml source file with those settings:
:syntax on
:set spell
Dominique: did you contact the syntax file
John Little wrote:
There's a copyright notice:
# Copyright (©) 2001 by Jörg Zieflejoerg.ziefle@gmx.obfuscated
The © and the ö are encoded in ISO 8859-1, aka latin1
sed: RE error: illegal byte sequence
This looks to me like weirdness in the OS X implementation of sed. Mine (GNU
Tomek wrote:
The Windows distribution of Vim which I use, gVim 7.3, has support for
NSIS
syntax coloring. The syntax kicks in correctly when opening a .nsi
file,
but it's not the case with .nsh (NSIS header) files.
For an intermediate vimer like myself, it's a little pesk:
- copy filetype.vim
John Beckett wrote:
The problem is that (I think) Vim uses the 'shell' option to
determine what shell to use to run :! commands, and some users
would change that to some quirky shell like 4NT or a host of
others. If netrw checks for 'cmd', it could conceivably fail the
check but 'move' and
John Beckett wrote:
Charles Campbell wrote:
So, how best to make this work? I was thinking
if has(win32) || has(win95) || has(win64) || has(win16)
if executable(cmd)
let g:netrw_localmovecmd= cmd move
endif
endif
No, as Ben said it would have to be cmd /c move
John Beckett wrote:
Charles Campbell wrote:
So, how best to make this work? I was thinking
if has(win32) || has(win95) || has(win64) || has(win16)
if executable(cmd)
let g:netrw_localmovecmd= cmd move
endif
endif
You probably saw the other message that the current
Hello,
I have a request of a windows person out there (I currently don't have
access to a windows box).
The latest netrw asks users to consider setting up local commands for
copy/mkdir/rmdir, but I've been told that there really aren't any such
commands available under Windows; instead,
Tony Mechelynck wrote:
Error detected while processing
/usr/local/share/vim/vim73/autoload/netrw.vim:
line 327:
E580: :endif without :if: endif
All Mercurial changesets published to date are installed; latest
change in this file was in changeset 4dde9b516e72 dated Thu Apr 05
17:33:26 2012
Marcin Szamotulski wrote:
Hello,
The variable g:tex_isk which sets keyword option in the syntax/tex.vim file is
not documented (vim-7.3.487) under :help. For example g:sh_isk is, and as I
recall
g:tex_isk used to be somewhere in the help files, am I right?
I've sent a patch to Bram
v...@googlecode.com wrote:
Comment #4 on issue 59 by sbje...@gmail.com: netrw breaks scripts.vim
http://code.google.com/p/vim/issues/detail?id=59
hi dr campbell, i am still seeing the previous version on your
homepage. do you have a repository (like git) that i can follow and
submit patches?
Kevin Goodsell wrote:
Opening a zip file with Vim doesn't work properly if the zip file
includes a comment. For example, create a zip file this way:
$ touch foo.txt
$ zip -z foo.zip foo.txt
adding: foo.txt (stored 0%)
enter new zip file comment (end with .):
Comment!
.
When opening this
Ivan Krasilnikov wrote:
I've found that vim syntax file (runtime/syntax/vim.vim) doesn't know
about some options of :command -complete=.
For example, it highlights color in the line below as an error:
command -nargs=1 -complete=color ...
Please consider updating the list of keywords in it on
Thilo Six wrote:
Hello Charles,
Excerpt from Charles Campbell:
Ivan Krasilnikov wrote:
I've found that vim syntax file (runtime/syntax/vim.vim) doesn't know
about some options of :command -complete=.
For example, it highlights color in the line below as an error:
command -nargs=1
Benjamin R. Haskell wrote:
On Tue, 13 Mar 2012, Charles Campbell wrote:
Dominique Pellé wrote:
This is a minor issue: vim --help does not describe the command
line options -E and --echo-wid.
Is this intentional to keep make help short?
If not, attached patch adds them.
I see help for -E
Hello!
wincmd r, wincmd x modify windows (rotate and exchange, respectively).
This process carries window variables along.
However, wincmd s and wincmd v, which split and duplicate windows,
don't duplicate window variables.
Shouldn't they? I know that I'd find that convenient for netrw.
Kosta Zertsekel wrote:
Please read the message that showed up at the bottom of your email,
courtesy of the list's s/w. It contains a link; the site pointed to by
that link tells you how to unsubscribe. Needless to say, you did not
unsubscribe with your post.
Regards,
Chip Campbell
Yes, its back!
Albeit at a new webhost (apply your favorite search engine to hostbig).
You may find it at:
http://www.drchip.org/
Hopefully all my vim pages and content are there and accessible. Let me
know if there's problems/something missing.
Chip Campbell
--
You received this
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 50 by asom...@gmail.com: tex.vim does not understand
IEEEeqnarray environment
http://code.google.com/p/vim/issues/detail?id=50
What steps will reproduce the problem?
1. Open a LaTeX document that
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 50 by asom...@gmail.com: tex.vim does not understand
IEEEeqnarray environment
http://code.google.com/p/vim/issues/detail?id=50
What steps will reproduce the problem?
1. Open a LaTeX document that
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 47 by weasley...@gmail.com: In Win32, mouse wheel do not
scroll the window under cursor
http://code.google.com/p/vim/issues/detail?id=47
In a gVim for windows, when there are more than one
Bram Moolenaar wrote:
Recently there was a discussion about getcharmod() and it became clear
it's not so easy to get a flag value out of a number. Vim doesn't have
AND and OR operators.
They are very easy to add. We just need to decide what the syntax is.
The | operator can't be used, it ends
Bram Moolenaar wrote:
Ivan Krasilnikov wrote:
Attached are stack traces of these warnings. Warnings are printed
inside removeEventHandler() at gui_beval.c:479..487 as a result of
some letbeval = ... statement.
Apparently, removeEventHandler() is called twice somewhere.
Just
Peter Odding wrote:
Have you tried the advice at
http://vim.wikia.com/wiki/Keep_folds_closed_while_inserting_text?
It's obviously not originally meant to speed things up, but has that
nice side effect.
I use this tip, and yet occasionally encounter such slowdowns (often
when
editing large
Christian Brabandt wrote:
Hi Bram!
On Sa, 22 Okt 2011, Bram Moolenaar wrote:
Tom Minilith wrote:
Yesterday, I uploaded a small plugin:
http://www.vim.org/scripts/script.php?script_id=3780
I then wanted to make minor changes to the plugin description. Unexpectedly,
I was
Bram Moolenaar wrote:
Christian Brabandt wrote:
On Sa, 22 Okt 2011, Bram Moolenaar wrote:
Tom Minilith wrote:
Yesterday, I uploaded a small plugin:
http://www.vim.org/scripts/script.php?script_id=3780
I then wanted to make minor changes to the plugin description.
Charles Campbell wrote:
Bram Moolenaar wrote:
Christian Brabandt wrote:
On Sa, 22 Okt 2011, Bram Moolenaar wrote:
Tom Minilith wrote:
Yesterday, I uploaded a small plugin:
http://www.vim.org/scripts/script.php?script_id=3780
I then wanted to make minor changes to the plugin description
Christian Brabandt wrote:
On Wed, October 19, 2011 10:22 pm, Charles Campbell wrote:
but this time applied to maps). There was a prior discussion about map
restoration; the problem involves options such asbuffer,silent,
etc. I'd like plugins to be able to save user maps, override them
Thilo Six wrote:
Thilo Six wrote the following on 17.10.2011 20:18
Hello
-- snip --
Several other critical options are already mentioned. Can we collect them all?
Which ones are missing?
-- snip --
Here is a (probably incomplete) list of options i have identified so far:
Thilo Six wrote:
Charles Campbell wrote the following on 19.10.2011 17:11
-- snip --
I suggest looking at pluginkiller
(http://drchip.0sites.net/astronaut/vim/index.html#PLUGINKILLER) - it
has a large list of options which can cause plugins grief.
Regards,
Chip Campbell
Yes
Danek Duvall wrote:
Thilo Six wrote:
attached is full list of affected files. Those files below /doc can be ignored i
assume. I would like to see the rest fixed, too. Can we join forces?
...snip...
I used
comm -13 =(grep -l set cpo **/*.vim) =(grep -l ^[[:space:]]*
**/*.vim)
agentsmith wrote:
Hello, Charles!
I have elaborated a bit on the differences between my home vim version
and the current version. As a result I've found that g:netrw_winsize
was initialized by 25 in new version, diff :
if !exists(g:netrw_winsize)
let g:netrw_winsize=
endif
Tony Mechelynck wrote:
On 26/09/11 22:34, Charles Campbell wrote:
Charles Campbell wrote:
Hello,
I've been getting these messages in the shell after exiting vim:
(gvim:16151): Gtk-WARNING **: unable to find signal handler for
object(GtkWindow:0xac9380) with func(0x5e4f1e) and data(0xafd030
Hello,
I've been getting these messages in the shell after exiting vim:
(gvim:16151): Gtk-WARNING **: unable to find signal handler for
object(GtkWindow:0xac9380) with func(0x5e4f1e) and data(0xafd030)
and
(gvim:16320): Gtk-WARNING **: unable to find signal handler for
agentsmith wrote:
Hello, everyone!
I experienced a different behavior of :Vex command after vim update on
my Fedora 15.1.
Before update this command had split window on two equal parts with a
list of the current dir on the left side(by default).
After update :Vex causes small vertical list of
agentsmith wrote:
On Sep 26, 7:43 pm, Charles Campbellcharles.e.campb...@nasa.gov
wrote:
agentsmith wrote:
Hello, everyone!
I experienced a different behavior of :Vex command after vim update on
my Fedora 15.1.
Before update this command had split window on two equal
agentsmith wrote:
After vimball installing and
vim netrw.vba
:so %
(why is it so complicated???)
got following error messages:
Error detected while processing function vimball#Vimball:
line1:
E117: Unknown function: Dfunc
Looks like you somehow got a vimball set up for debugging; just
Charles Campbell wrote:
Hello,
I've been getting these messages in the shell after exiting vim:
(gvim:16151): Gtk-WARNING **: unable to find signal handler for
object(GtkWindow:0xac9380) with func(0x5e4f1e) and data(0xafd030)
and
(gvim:16320): Gtk-WARNING **: unable to find signal
Donald Allen wrote:
In netrw, the mf command does not work with 'syntax off' in my .vimrc
file. In gvim, s-leftmouse does work. mf does work without the 'syntax
off' in the .vimrc file. If I eliminate the 'syntax off' in my .vimrc
file, bring up vim and do a :syntax off, then mf works!
/Don
Benjamin R. Haskell wrote:
On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Is this something that is likely to get fixed?
Seems very likely to me. And probably soon, based on his usual
turnaround time.
As far as I can tell, the source of
Hello!
I recently checked my plugins' ratings:
08/09/11 script 677/279/10776: Manpageview.vim
08/31/11 script -133/1094/10866: Manpageview.vim
This seems like an odd thing -- is this preparation for a general
bombing of plugins' ratings?
Regards,
Chip Campbell
--
You received this message
Charles Campbell wrote:
Benjamin R. Haskell wrote:
On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Is this something that is likely to get fixed?
Seems very likely to me. And probably soon, based on his usual
turnaround time.
As far
201 - 300 din 419 matches
Mail list logo
