Charles Campbell wrote:
mattn wrote:
let g:foo = 1
The SynID of foo is not vimVar. Currently, it's vimIsCommand. IFAIK, it was
vimVar in few month ago. I'm thinking vimIsCommand is too generally pattern.
syn match vimIsCommand \\h\w*\ contains=vimCommand
syn match vimVar
Christian Brabandt wrote:
Hi Charles!
On Do, 26 Feb 2015, Charles E Campbell wrote:
Hello!
I've attached a script which illustrates the problem.
vim -u NONE -N prblm.vim
:so %
:q (in the gvim that's showing prblm.vim, NOT the remote gvim)
Behavior:
* a remote server gvim
Hello:
Please try the following on a linux system:
mkdir PROBLEM
cd PROBLEM
ln -s file1 file2
Doing ls shows file2 exists (but it points to a non-existing file).
Fire up vim:
vim -u NONE -N
:echo string(glob(*))
shows that glob() returns an empty string, whereas it should show
Hello!
Looks like patch#592 stops netrw from working with remote files: vim
scp://hostname/ no longer works.
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
Gary Johnson wrote:
I just updated to 7.4.579 on one of my Linux systems. With the
cursor over printf in a C file, typing K results in the following
error message.
Error detected while processing function
manpageview#KMap..manpageview#ManPageView:
Hello:
I've found something peculiar. When I put :echomsg GOT HERE into
autoload/netrw.vim just before the if v:version 704... test (line#25
with v153), no output appears. No output appears with a subsequent
:messages.
This difficulty means that an echomsg will show no output inside that
Bram Moolenaar wrote:
Sung Pae wrote:
On Thu 8 Jan 2015 at 05:15:55PM -0600, guns wrote:
On Thu 8 Jan 2015 at 03:06:45PM -0800, Amadeus Demarzi wrote:
Using vim with patches 1-567 I get a range error when calling wincmd in
certain contexts:
vim -u NONE
:split
:wincmd+ # works as
Bram Moolenaar wrote:
Marcin Szamotulski wrote:
On 04:17 Mon 08 Dec , Bram Moolenaar wrote:
Patch 7.4.542
Problem:Using a range for window and buffer commands has a few problems.
Cannot specify the type of range for a user command.
Solution: Add the -addr argument for user
Ken Takata wrote:
snip
To avoid this problem, maximum length should be limited to MAX_PATH
bytes. (If someone want to handle a file name which is longer than
MAX_PATH bytes and shorter than MAX_PATH characters, he should set
'enc' to utf-8.) I wrote a patch to fix this problem. Please check
Kenichi Ito wrote:
Hi Chip,
I tried vim.vim v7.4-30 in your website,
but nowait is not highlighted.
This patch fixes it.
---
diff --git a/runtime/syntax/vim.vim b/runtime/syntax/vim.vim
index e86611a..b9b815c 100644
--- a/runtime/syntax/vim.vim
+++ b/runtime/syntax/vim.vim
@@ -327,7 +327,7 @@
Hello:
I recently received a request that $\bar{a}$ be supported: ie. it should
be conceal-char'd and appear as a: a̅
So I tried
syn match texMathSymbol '\\bar{a}' contained conceal cchar=a̅
but this construct doesn't produce the desired output: instead, it shows
an a instead.
Charles Campbell wrote:
Hello:
Looks like I somehow omitted including it. Anyway, please try the
attached syntax/vim.vim .
Sorry about that, listers -- another case of my intending to respond to
one person but spamming the entire list instead.
Regards,
Chip Campbell
--
--
You received
Charles E Campbell wrote:
Bram Moolenaar wrote:
Charles Campbell wrote:
I find reading the folded lines to be less than ideal, as the extra
spacing required of the +---s varies and so lines: doesn't line up.
This patch makes all the +---... prefixes take up 5 spaces (using %-5s,
so it uses
Bram Moolenaar wrote:
Charles Campbell wrote:
Updated patch. The optionsptch patch will insert one line into the
options.txt help; I separated it out in case its not wanted.
Thanks, I'll put it in the todo list. I'll await comments for a little
while.
Hello!
I've attached an improved
Hello!
I find reading the folded lines to be less than ideal, as the extra
spacing required of the +---s varies and so lines: doesn't line up.
This patch makes all the +---... prefixes take up 5 spaces (using %-5s,
so it uses padding). By itself, this makes the folded sections, no
matter
Christian Brabandt wrote:
Am 2014-09-10 17:02, schrieb Charles Campbell:
Hello!
I find reading the folded lines to be less than ideal, as the extra
spacing required of the +---s varies and so lines: doesn't line up.
This patch makes all the +---... prefixes take up 5 spaces (using
%-5s, so
Daniel Hahler wrote:
When there is a `kdeinit4` process, but `kfmclient` is not installed
`BrowseX` fails to open an URL (it falls through to the last else block).
This happened on a non-KDE system, where `kdeinit4` was
installed/started for an unknown reason, but konqueror/kfmclient is not
matthias.hinkfo...@uni-rostock.de wrote:
Hello list,
the attached patch addresses 2 issues regarding comments in Makefiles:
1) a comment in a rule is not highlighted, e.g.:
target1: # comment1
here, comment1 is not highlighted.
2) (Makefile-) comments in repipes destroy the highlighting of
Tony Mechelynck wrote:
On 17/07/14 21:55, Bram Moolenaar wrote:
Charles Campbell wrote:
The following line, when in a buffer that vim is displaying:
m=⎣ℜ(b-a)⎦=1~1026
has the script R displayed correctly when the cursor is swept over it
from right to left,
but the script R is displayed
Hello:
The following line, when in a buffer that vim is displaying:
m=⎣ℜ(b-a)⎦=1~1026
has the script R displayed correctly when the cursor is swept over it
from right to left,
but the script R is displayed incorrectly when the cursor is swept
over it from left to right.
I'm using:
Enno wrote:
Le mardi 24 juin 2014 19:16:44 UTC+2, DrChip a écrit :
Enno wrote:
Le vendredi 13 juin 2014 18:53:06 UTC+2, Charles Campbell a écrit :
Enno wrote:
Ok, I understand that spell checking is only activated after a
keyword, such as the \section{..} command. But why is it that
\begin
Christian Brabandt wrote:
diff --git a/src/window.c b/src/window.c
--- a/src/window.c
+++ b/src/window.c
@@ -5650,7 +5650,10 @@ win_new_height(wp, height)
if (wp-w_height 0)
{
if (wp == curwin)
- validate_cursor(); /* w_wrow needs to be valid */
+
Enno wrote:
Ok, I understand that spell checking is only activated after a
keyword, such as the \section{..} command. But why is it that
\begin{document} does not belong to these keywords? This disables
spell checking for example for letter document classes without any
sectioning. How to
v...@googlecode.com wrote:
Comment #4 on issue 230 by brammool...@gmail.com: Vim: Caught deadly
signal SEGV
http://code.google.com/p/vim/issues/detail?id=230
The errors in the libfontconfig.so look like a library problem:
reading 4 bytes where there are only 2. Because of alignment this
Charles Campbell wrote:
v...@googlecode.com wrote:
Comment #4 on issue 230 by brammool...@gmail.com: Vim: Caught deadly
signal SEGV
http://code.google.com/p/vim/issues/detail?id=230
The errors in the libfontconfig.so look like a library problem:
reading 4 bytes where there are only 2
Charles E Campbell wrote:
Bram Moolenaar wrote:
Charles Campbell wrote:
Charles Campbell wrote:
v...@googlecode.com wrote:
Comment #4 on issue 230 by brammool...@gmail.com: Vim: Caught deadly
signal SEGV
http://code.google.com/p/vim/issues/detail?id=230
The errors in the libfontconfig.so
itchyny wrote:
let m = 5
let y = 20 * (m / 4) + m / 4
let z = 10
for i in range(10)
echo i
endfor
while i
let i -= 1
endwhile
Please try v7.4-30 which you can get from my website:
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM .
Thank you for the report,
Chip Campbell
--
--
G.raud wrote:
This bug is found in sh.vim Version 134 ASTRO-ONLY but _not_ in Version
132 ASTRO-ONLY (and _not_ in VIM 7.4.273 either):
$ cat test.sh EOF
#!/bin/bash
${var/#from/to} # the hash char # inside the param expansion starts a comment
# Note: /#from/to is a string replacement
Enno wrote:
Can one configure netrw so that when opening a file in netrw the just left
netrw buffer is automatically deleted?
For example type :e ., navigate to a file, hit CR. Then there is the netrw
buffer, created by :e . that we just left, and has done its service. Is there an
autocmd to
Enno wrote:
Le vendredi 23 mai 2014 10:42:55 UTC+2, Enno a écrit :
Can one configure netrw so that when opening a file in netrw the just left
netrw buffer is automatically deleted?
For example type :e ., navigate to a file, hit CR. Then there is the netrw
buffer, created by :e . that we just
Dan Sanduleac wrote:
Hi,
I've noticed that syntax highlighting inside bash subshells is lacking (comments are not
rendered as such, for instance). Turns out that was because the subshells were parsed as
`shCmdParenRegion` which is for stuff like `cat (one-line command)`. Instead
subshells
Charles Campbell wrote:
Dan Sanduleac wrote:
Hi,
I've noticed that syntax highlighting inside bash subshells is
lacking (comments are not rendered as such, for instance). Turns out
that was because the subshells were parsed as `shCmdParenRegion`
which is for stuff like `cat (one-line
Enno wrote:
This inconsistency is also discussed in the comments of the thread opener on
http://tex.stackexchange.com/questions/135337/how-to-set-up-spell-checking-with-vim
If set filetype=plaintex, then spell checking in a tex file checks the text in
the whole document for spelling errors.
Enno wrote:
Le jeudi 3 avril 2014 18:57:12 UTC+2, Enno a écrit :
Le mardi 12 novembre 2013 20:22:59 UTC+1, v...@googlecode.com a écrit :
Updates:
Status: Accepted
Owner: drc...@campbellfamily.biz
Comment #1 on issue 151 by drc...@campbellfamily.biz: file management
(copy/move)
G.raud wrote:
This bug is found in sh.vim Version 134 ASTRO-ONLY but _not_ in Version
132 ASTRO-ONLY (and _not_ in VIM 7.4.273 either).
$ cat test.sh EOF
#!/bin/sh
printf %s '\' starts a single quoted 'string'
EOF
$ vim -u NONE -c ':syntax on' test.sh
Regards
Hello!
Just wanted to let you
Hello:
I'm getting some compiler errors with Scientific Linux 6.4:
os_unix.c|2879 error| 'XATTR_NAME_SMACK' undeclared (first use in this
function)
os_unix.c|2879 error| (Each undeclared identifier is reported only once
os_unix.c|2879 error| for each function it appears in.)
os_unix.c|2880
Bram Moolenaar wrote:
I'm thinking of a kind of manifest that specifies these dependencies.
When we standardize that it's still possible to use a choice of plugin
managers.
FWIW, GLVS (getscript) supports plugin dependencies. A number of my
plugins have lines such as
LCD 47 wrote:
As the subject says, the new uniq() function should be highlighted.
/lcd
diff -r d96e8fbc3747 runtime/syntax/vim.vim
--- a/runtime/syntax/vim.vimTue Mar 25 18:24:23 2014 +0100
+++ b/runtime/syntax/vim.vimWed Mar 26 17:03:08 2014 +0200
@@ -73,7 +73,7 @@
syn
Bohr Shaw wrote:
ehttps://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim
Hello!
Please try netrw v151n, available from my website:
http://www.drchip.org/astronaut/vim/index.html#NETRW .
For the optional url redirecting; you may disable netrw by putting
let
G.raud wrote:
if true
then
eval $varname=\\
# comment highlighted as a string
fi
Hello!
I haven't fixed this yet, but I wanted to let you know its on my todo list.
Chip Campbell
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
G.raud wrote:
To reproduce:
$ cat test.sh EOF
#!/bin/sh
myfunc () (
set -e
for arg; do
test -e $arg
done
if [ $# -gt 0 ]; then exit 1; fi
# no 'comment
)
$ vim -u NONE -c ':syntax on' test.sh
Hello:
I haven't
Bram Moolenaar wrote:
Patch 7.4.208
Problem:Mercurial picks up some files that are not distributed.
Solution: Add patterns to the ignore list. (Cade Forester)
Files: .hgignore
snip
I suspect that this patch really shouldn't be in the patch list; there
is no .hgignore file in the
Tony Mechelynck wrote:
abo sv ftp://ftp.vim.org/pub/vim/patches/7.4/README
Hello, Tony:
My [Sent] folder isn't showing anything, but the message is marked as
replied to. So, anyway, at the risk of repeating myself: I didn't
notice any problem with netrw v151k with this (or with view, btw).
Tony Mechelynck wrote:
RFE: I propose a :noswapfile (or something) prefix, working in similar
fashion to the :verbose, :vertical, :top, :tab, etc. prefixes in front
of another ex-command, and with the meaning: If that _subordinate_
ex-command opens a new buffer, we want 'noswapfile' set on
Tony Mechelynck wrote:
The command
abo sv ftp://ftp.vim.org/pub/vim/patches/7.4/README
(in a script, at a point where another buffer is displayed in a
window), or even
:view
(at the Vim command-line, when looking at that README file, to see if
it has been modified), both give me
Tony Mechelynck wrote:
Using gvim 7.4.141 (Huge) for GTK2/GNOME2, changeset 2ca470c6096e
g:loaded_netrw == g:loaded_netrwPlugin == 'v149'
$VIMRUNTIME/plugin/gzip.vim dated 2010 Mar 10
While viewing
Ingo Karkat wrote:
On 11-Mar-2014 15:14 +0100, Ben Fritz wrote:
snip
Isn't this situation what shellescape() is designed for?
That's not saying shellescape() will work, but I think it's supposed
to work, unlike using a bare % which should always work for internal
Vim commands but will only
Yuri Vic wrote:
Attached patch fixes the problem when vim fails to highlight comments between
rules in yacc source.
Thanks! I've included it on my website:
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_YACC
Regards,
Chip Campbell
--
--
You received this message from the vim_dev
G.raud wrote:
#!/bin/sh
ls #\$#
Thank you for the feedback; please try syntax/sh.vim v132, available
from my website: http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH
Regards,
C Campbell
--
--
You received this message from the vim_dev maillist.
Do not top-post!
Yuri wrote:
On 02/26/2014 08:53, Charles E Campbell wrote:
I suggest that you try things out with the latest netrw, which you
can get from my website:
Yes, this fixed the problem.
Since you are the maintainer, I would like to ask if it is possible to
not change directory to the folder
Hello!
I thought I'd share the solution to what happened to luxi mono?,
just in case anyone else was being afflicted in a similar fashion:
* symptom: the font I prefer to use, Luxi Mono Bold 11, was no longer
available (I use a lot of math-oriented utf-8 characters, which Luxi
Mono
Tony Mechelynck wrote:
Using gvim 7.4.141 (Huge) for GTK2/GNOME2, changeset 2ca470c6096e
g:loaded_netrw == g:loaded_netrwPlugin == 'v149'
$VIMRUNTIME/plugin/gzip.vim dated 2010 Mar 10
While viewing
Dominique Pellé wrote:
François Ingelrest wrote:
On 26 December 2013 17:54, Dominique Pellé wrote:
You need to:
- build vim with -g -O0
- make sure vim is not stripped (uncomment #STRIP = /bin/true
in vim/src/Makefile). Or run vim from the vim/src/. directory,
as it is not stripped
Cade Foster wrote:
Problem: vim does not open local directory.
Steps to reproduce:
1. run
$ vim /etc/
Expected results:
use netrw plug-in to list directory content.
Actual results:
1. show error message
/etc/ Illegal file name
2. buffer remains empty.
I'm unable to duplicate your
Gary Johnson wrote:
On 2013-12-30, Charles Campbell wrote:
Cade Foster wrote:
Problem: vim does not open local directory.
Steps to reproduce:
1. run
$ vim /etc/
Expected results:
use netrw plug-in to list directory content.
Actual results:
1. show error message
/etc/ Illegal file name
Lech Lorens wrote:
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
mattn wrote:
On Thursday, December 5, 2013 1:18:17 PM UTC+9, Charles Campbell wrote:
mattn wrote:
Hi list.
Currently, vim bundle netrw v149. It doesn't work with multi-byte strings.
This problem occur in v149, 150j both.
Below is a patch for v150j.
--- autoload/netrw.vim.org 2013-11-29
+ glob(s:ComposePath(dirname,.*),0,1)
call Decho((LocalListing) filelist=.filelist)
Hello!
Please use netrw v150j on my website; this problem has been addressed
earlier.
http://www.drchip.org/astronaut/vim/index.html#NETRW
Regards,
Charles Campbell
--
--
You received this message from
+ glob(s:ComposePath(dirname,.*),0,1)
call Decho((LocalListing) filelist=.filelist)
I'm sorry; I just noticed that you mentioned v150j. The s:Strlen()
function is (by default) using strdisplaywidth(); does this not work?
Please give me an example so I can test things out.
Thank you,
Charles
Bram Moolenaar wrote:
Michael Henry wrote:
I've been wondering about the use of CTRL-C regarding timers.
There has been a lot of discussion on ways to regain control in
the face of a runaway timer, which is of course an important
consideration. I've been wondering, however, about any negative
).
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 are subscribed to the Google Groups
position when t was
used to select a file. It did not do so in the new tab page when
t was applied to a directory; that latter problem is what I
addressed in the attached copy of netrw.
Regards,
Charles Campbell
Would you please provide an exact sequence of steps that evokes
Dan Doel wrote:
On Thu, Oct 31, 2013 at 11:53 AM, Charles Campbell
charles.e.campb...@nasa.gov wrote:
MMAMBMB
# a b b
# b b
M
At the time the syntax hilighter sees the # in # b b, note that
'#\=\s*\zsb' DOES NOT MATCH.
However, the M syntax DOES MATCH, and so its highlighted as MyComment
ZyX wrote:
On Friday, November 1, 2013 10:51:48 AM UTC+4, Nirk Niggler wrote:
From structs.h:
# define DB_COUNT 4/* up to four buffers can be diff'ed */
Is there a compelling reason to keeping the limit at 4 rather than upping it to
a limit like 9?
I do not know reason for 4
MMAMBMB
# a b b
# b b
M
At the time the syntax hilighter sees the # in # b b, note that
'#\=\s*\zsb' DOES NOT MATCH.
However, the M syntax DOES MATCH, and so its highlighted as MyComment.
Syntax highlighting is tricky.
Regards,
Charles Campbell
--
--
You received this message from the vim_dev
Marvin Renich wrote:
The sh.vim syntax file does not recognize the escaped double quote
inside the double-quoted string in the following bash snippet:
---8
#!/bin/bash
for r in $reqFields ; do
if [[ -z ${keys[$r]} || ${keys[$r]} == \\ ]] ; then
missing=$missing $r
Ben Fritz wrote:
On Tuesday, October 29, 2013 9:17:43 PM UTC-5, Samuel Ferencik wrote:
It seems this got missed (back in 2010). Can we resurrect it, please?
Yes, please! I actually have removed the LargeFiles plugin, because I kept
losing all my undo history on files I already had open in
Christian Brabandt wrote:
Hi Charles!
On Do, 31 Okt 2013, Charles Campbell wrote:
Please try LargeFile v5k. This version should retain undo history
if your vim has persistent undo available. Its pretty new, so there
may well be bugs with the undo history stuff.
You may get a copy from my
Peter Aronoff wrote:
On Mon Oct 10/21/13 at 8:04, Ben Fritz wrote:
On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote:
Can I ask what email you used to reach him?
I've had luck in the past with the email address in the header of his
plugins.
But you need to remove the capital
Bram Moolenaar wrote:
Christian Brabandt wrote:
On Do, 19 Sep 2013, Jonathon Merz wrote:
With the new regexp engine, when searching for a null character using
decimal/octal/hex character matches, all lines are matched instead of only
the specified character.
The attached .txt file (ok to
Bram Moolenaar wrote:
Charles Campbell wrote:
I'm having a problem exemplified by the following code snippet: (lets
call this prblm.vim)
au BufEnter * sil! call Prblm(expand(amatch))
fun! Prblm(fname)
let g:junk= 1
echomsg TESTING.a:fname.
endfun
vsplit
Use vim -u NONE prblm.vim
Hello!
I'm having a problem exemplified by the following code snippet: (lets
call this prblm.vim)
au BufEnter * sil! call Prblm(expand(amatch))
fun! Prblm(fname)
let g:junk= 1
echomsg TESTING.a:fname.
endfun
vsplit
Use vim -u NONE prblm.vim
:so %
:echo g:junk
At this point, we get
tooth pik wrote:
On Mon, Aug 26, 2013 at 05:11:19PM -0400, Charles Campbell wrote:
Bram Moolenaar wrote:
Bruno Sutic wrote:
The change supporting this was done on July 12, 2013; its for v150,
which has not been released as yet. That was the bugfix that I
was referring to; I think I
Bruno Sutic wrote:
Hi,
I noticed a new behavior with vim 7.4 and netrw plugin.
Alternate buffer command (normal mode C-^ key) works differently than in vim
7.3.
Here are the steps how to see the difference:
*vim 7.3*
1. /usr/bin/vim -u NORC -N (starting vim7.3)
2. :e Gemfile
Bram Moolenaar wrote:
Bruno Sutic wrote:
Hi,
I noticed a new behavior with vim 7.4 and netrw plugin.
Alternate buffer command (normal mode C-^ key) works differently than in vim
7.3.
Here are the steps how to see the difference:
*vim 7.3*
1. /usr/bin/vim -u NORC -N (starting vim7.3)
2.
LCD 47 wrote:
..snip..
+1 for this. People routinely edit files that only make sense (and
will only ever run) on remote servers. There are legitimate situations
where editing a file has nothing to do with actually running it.
Except, if its embedded in vimscript, then it is intended to
Bram Moolenaar wrote:
Manuel Ortega wrote:
As noted in an earlier thread, I discovered that most attributes to
:command can be abbreviated. I discovered this only by accident, looking
in syntax/vim.vim.
Turns out, in that syntax file (a) there is no support for the attribute
-buffer (for
James McCoy wrote:
On Aug 21, 2013 1:42 PM, Charles Campbell
charles.e.campb...@nasa.gov mailto:charles.e.campb...@nasa.gov wrote:
LCD 47 wrote:
..snip..
+1 for this. People routinely edit files that only make sense
(and
will only ever run) on remote servers
Manuel Ortega wrote:
There are at least two bugs in vim syntax highlighting. It occurs
when one leaves out optional spaces in a List or Dictionary.
For example:
let foo = ['one','two','three']
shows distractingly bizarre highlighting. The second and third
elements have only their first
Cedric Bosdonnat wrote:
Hello Charles,
On Thu, 2013-08-01 at 14:56 -0400, Charles Campbell wrote:
I believe that this issue has been addressed previously. You can get
the latest zip plugin from my website:
http://www.drchip.org/astronaut/vim/index.html#ZIP
Indeed, that is fixed in your
Cedric Bosdonnat wrote:
Hello,
I'm editing OOXML files pretty often with vim and the zip plugin.
However those have a [Content_Types.xml] file inside the zip that can't
be opened.
You'll find attached a simple patch against trunk to fix that problem by
just escaping the name of the file to
David Larson wrote:
On Saturday, June 8, 2013 2:48:39 PM UTC-7, Bram Moolenaar wrote:
There are no options. Vim is written in C and I see no reason to
change. Perhaps, when Zimbu is ready I might consider rewriting some
pieces in Zimbu, but that's going to take several years during which no
Dimitar DIMITROV wrote:
There is no use case
If you do something stupid by accident most vim operations can be
aborted by ctrl-c (exception: python, rbuy, .. scripts)
Try to abort it you will see the success you have.
So there is still nothing to fix or talk about unless there is a use
In file included from regexp.c:7918:
regexp_nfa.c: In function 'addstate':
regexp_nfa.c:3850: warning: 'save_lpos.lnum' may be used uninitialized
in this function
regexp_nfa.c:3850: warning: 'save_lpos.col' may be used uninitialized in
this function
regexp_nfa.c:3852: warning: 'save_ptr' may be
Nikolay Pavlov wrote:
On Jul 14, 2013 9:36 PM, Tony Mechelynck
antoine.mechely...@gmail.com mailto:antoine.mechely...@gmail.com
wrote:
On 07/14/13 17:40, glts wrote:
Hi list,
sent this to the maintainer in May. Now resending an updated patch to
the list. I removed some mistaken
Manuel Ortega wrote:
1. command /usr/local/bin/vim -nNX -u NONE
Bram,
I looked at this and didn't remember offhand what the '-X' flag did.
No wonder: 'vim --help' has no entry for that flag. But ':h
startup-options' *does* say what the flag does. Please update the
output of 'vim
itchyny wrote:
Hi list. There is a problem in vim.vim for |command-completion-customlist|.
-
command! -nargs=+ -complete=customlist,s: X call s:x(q-args)
-
The above example is looks like:
Bram Moolenaar wrote:
Nikolay Pavlov wrote:
It's the other way around: On MS-Windows you can do:
:e foo\$bar
That is editing the file $bar in directory foo. On Unix this has a
different meaning, editing file foo$bar, thus not using $bar as an
environment variable. That's why test
Bram Moolenaar wrote:
Nikolay Pavlov wrote:
On Jul 4, 2013 10:25 PM, Bram Moolenaar b...@moolenaar.net wrote:
Nikolay Pavlov wrote:
It's the other way around: On MS-Windows you can do:
:e foo\$bar
That is editing the file $bar in directory foo. On Unix this has
a
different
Bram Moolenaar wrote:
Patch 7.3.1282 (after 7.3.1277)
Problem:'cursorline' not drawn in any other window. (Charles Campbell)
Solution: Do draw the cursor line in other windows.
Files: src/screen.c
Thank you -- ProcTrack is working again.
Chip
--
--
You received this message from
This problem appeared with a recent patch (I can't backtrack on the
patches to find out which one on my work machine -- however, I suspect
its patch#1277).
Have two files, tmp1 and tmp2, with several lines contained in each:
vim -O tmp1 tmp2
:set cul
:wincmd l
:set cul
:wincmd h
Note that
mattn wrote:
Hi list.
When below's text in foo.vim
-
augroup x
g:indent_guides_enable_on_vim_startup
-
The syntax is broken.
http://cache.gyazo.com/c7d8bdc05b41dde7621d2262d8a9ca56.png
This patch fixes syntax of global autoload variable like 'g:foo#bar#bar'.
Below is a
Yukihiro Nakadaira wrote:
On Wed, Jun 26, 2013 at 11:31 PM, Charles Campbell
charles.e.campb...@nasa.gov mailto:charles.e.campb...@nasa.gov wrote:
I tried it again with simple.vimrc:
set nocp
syn on
:filetype plugin on is also required to reproduce.
ftplugin/vim.vim executes
Yasuhiro MATSUMOTO wrote:
What value of your 're'?
Not sure what you want here. I usually interpret 're' in a vim context
as meaning regular expression.
Regards,
C Campbell
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
ZyX wrote:
The runtime update of Vim 7.3.488 (changeset 2cfb68fa26cd) adds : to
'iskeyword'; ostensibly To make syntax highlighting of 'vimVar's work
correctly. Since you, Charles, maintain the Vimscript syntax, I'd
thought this actually came from you. (I had earlier complained about the
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 144 by philippe...@gmail.com: Latex - Syntax highlighting in
lstlisting block
http://code.google.com/p/vim/issues/detail?id=144
What steps will reproduce the problem?
1. open vim
2. type :setf
Ken Takata wrote:
Thank you for updating the zip plugin, but checking PK doesn't work well.
When I try to open a file which matches g:zipPlugin_ext but doesn't start
with PK, an empty buffer is opened. I think the file should be read
by the plugin as same as unzip command returns an error.
v...@googlecode.com wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 140 by ondrej.pla...@gmail.com: netrw plugin NetrwTreeListing
http://code.google.com/p/vim/issues/detail?id=140
What steps will reproduce the problem?
1. command line $ echo test text.txt
2. $ vi
mattn wrote:
Remove *.ja from the extension list, and add new option to know which
the file extensions are zip or not.
v27a of the zip plugin
(http://www.drchip.org/astronaut/vim/index.html#ZIP) incorporates both
methods:
* checks that the first line of zip files starts with PK
* sets up
Bram Moolenaar wrote:
[snip] (discussion about relative numbers)
There is too much discussion about this. I think the current behavior
is OK and does not have enough disadvantage to justify adding yet
another option.
I won't be using the relative numbers option in its current state.
Regards,
101 - 200 din 419 matches
Mail list logo
