On 2013-07-17, Dimitar DIMITROV wrote:
Hi all,
According to :h:se, :se isn't supposed to output anything at all when in
default mode but it does when started like this:
command vim -nNX -u NONE
Actually, :help :set doesn't say that--it says it shows all
options that differ from their
On 2013-07-17, Gary Johnson wrote:
On 2013-07-17, Dimitar DIMITROV wrote:
Hi all,
According to :h:se, :se isn't supposed to output anything at all when in
default mode but it does when started like this:
command vim -nNX -u NONE
Actually, :help :set doesn't say that--it says
On 2013-07-19, Dimitar DIMITROV wrote:
Hi Dimitar,
It would be a big help to those of us with threading mail readers if
you would be sure that your replies include Re: at the start of
the Subject.
Thanks,
Gary
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type
On 2013-07-23, Nikolay Pavlov wrote:
On Jul 20, 2013 2:28 AM, Gary Johnson wrote:
On 2013-07-19, Dimitar DIMITROV wrote:
Hi Dimitar,
It would be a big help to those of us with threading mail readers if
you would be sure that your replies include Re: at the start of
the Subject
On 2013-07-23, Dimitar DIMITROV wrote:
Hi,
Found that many default compiler plugins lacked the makeprg setting.
I basically opened a perl file, then a c file and tried to compile it with
:mak
and it tried to use perl -c
this patch fixes it for gcc:
*** gcc.vim2013-07-23
On 2013-07-23, Dimitar DIMITROV wrote:
Hi,
Found that many default compiler plugins lacked the makeprg setting.
I basically opened a perl file, then a c file and tried to compile it with
:mak
and it tried to use perl -c
this patch fixes it for gcc:
*** gcc.vim
I just noticed this today with 7.4b but the behavior is the same
with 7.4a.9. It works correctly with 7.3.882.
The problem is that when I open a temporary file created by mutt
with the name /tmp/muttV1LGjR, the latest versions of vim do not
recognize this as a file name that should set
On 2013-08-02, Bram Moolenaar wrote:
Patch 7.4b.006 (after 7.3.1295)
Problem:Using \{n,m} in an autocommand pattern no longer works.
Specifically, mutt temp files are not recognized. (Gary Johnson)
Solution: Make \\\{n,m\} work.
Files:runtime/doc/autocmd.txt, src
On 2013-08-04, Andy Wokula wrote:
People, you can fill this thread with your complaints about the HTML
indent script.
I'm the current maintainer, lately I read lots of unspecific rants here and
there but direct feedback is rare for some reason.
The current version is a descendant of
On 2013-08-05, Andy Wokula wrote:
Am 05.08.2013 09:01, schrieb Gary Johnson:
I started looking for examples of indentation that I didn't like in
my HTML files. Then I looked in the indent/html.vim plugin and
discovered that it had changed a lot since the last time I tried
tuning it. I
On 2013-08-06, Dimitar DIMITROV wrote:
Hi all,
If you open the latest vim (vim -nNX -u NONE) and insert these lines:
.jpg 01;35
...
.emf 01;35
then go to the top (gg) and try vap...
There is an issue
:set paragraphs=
gg
vap
No issue.
:help 'paragraphs'
:help
The following problem appears in vim 7.3.882 and 7.4b.19 on Linux.
In the Vim src directory, in an 80x24 terminal, execute the
following.
vim -N -u NONE -c 'r !ls' +0 -c 'syn on' -c 'syn match Error /\.c\zs\n.*/'
Scroll down a bit and you will see a few files highlighted, starting
with
On 2013-08-08, Christian Brabandt wrote:
Hi Gary!
On Do, 08 Aug 2013, Gary Johnson wrote:
The following problem appears in vim 7.3.882 and 7.4b.19 on Linux.
In the Vim src directory, in an 80x24 terminal, execute the
following.
vim -N -u NONE -c 'r !ls' +0 -c 'syn on' -c
On 2013-08-09, Christian Brabandt wrote:
Hi Gary!
On Do, 08 Aug 2013, Gary Johnson wrote:
On 2013-08-08, Christian Brabandt wrote:
Hi Gary!
On Do, 08 Aug 2013, Gary Johnson wrote:
The following problem appears in vim 7.3.882 and 7.4b.19 on Linux.
In the Vim src
On 2013-08-09, Linda W wrote:
Gary Johnson wrote:
The following problem appears in vim 7.3.882 and 7.4b.19 on Linux.
I've seen similar behavior on any version of vim. Are you sure
you have your synchronization buffer set high enough for your
lang? It seems to be a different variable
On 2012-08-05, Christian Brabandt wrote:
Does this patch work for you?
diff --git a/src/spell.c b/src/spell.c
--- a/src/spell.c
+++ b/src/spell.c
@@ -10155,9 +10155,24 @@
intselected = count;
intbadlen = 0;
int
Christian,
On 2013-08-11, Christian Brabandt wrote:
On Sa, 10 Aug 2013, Gary Johnson wrote:
Now that 7.4 has been released and we can resume considering
features instead of just bug fixes, can we have this patch included?
If it isn't high on Bram's list, then Christian, would you please
On 2013-08-12, Christian Brabandt wrote:
Hi Gary!
On So, 11 Aug 2013, Gary Johnson wrote:
Christian,
On 2013-08-11, Christian Brabandt wrote:
On Sa, 10 Aug 2013, Gary Johnson wrote:
Now that 7.4 has been released and we can resume considering
features instead of just bug
On 2013-08-19, Manuel Ortega wrote:
On Mon, Aug 19, 2013 at 3:53 PM, Manuel Ortega mannyvim...@gmail.com wrote:
Dear Bram,
While perusing $VIMRUNTIME/syntax/vim.vim, I noticed that many of the
attributes to the command :command can be abbreviated. Namely:
instance:
I've been using Steve Losh's excellent Splice plugin to perform
merges under Perforce. This worked fine with Vim 7.3.882 but it
fails horribly with Vim 7.4. I have in my environment
P4MERGE=p4merge-splice
where p4merge-splice is the following script:
exec vim $1 $2 $3 $4 -c 'set
On 2013-08-22, Nikolay Pavlov wrote:
No, this is not a bug. Index of buffer within vim.buffers used to be an
unknown
integer: it was index of underlying C linked list of buffers. I changed the
code to make it more meaningful: now this index is buffer number. But there is
no buffer number
On 2013-08-26, David Fishburn wrote:
On Aug 26, 2013, at 1:34 PM, 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
On 2013-09-04, John Little wrote:
On Wednesday, September 4, 2013 10:00:34 PM UTC+12, Tony Mechelynck wrote:
.. So you got them from somewhere else and
did something that you ought NEVER to have done...
Maybe the Fedora packagers did it. I don't know about them, but
the Debian
On 2013-09-04, Ben Fritz wrote:
Windows 7: Start-Run... gvim -N -u NONE -i NONE
:help !!
I expect to see the help topic for normal-mode !!{filter} command,
just above :help v_!
Instead I'm taken to the help for :!!, 'Repeat the last :!{cmd}.'
This is in Vim 7.4.0, but I don't see any
On 2013-09-05, Tony Mechelynck wrote:
Using :%g/^! on the tags file shows that there are no other tags
starting with an exclamation mark, which is not surprising since the
tags file is sorted.
I see in $VIMRUNTIME/doc/tags that the tags are indeed sorted. In
that case, why does :help !C-D
On 2013-09-04, mattn wrote:
Hi.
:e foo:bar
:set swapfile
:swapname
foo:.bar.swp
Using Vim 7.4.9 on Linux, started as
vim -N -u NONE
I get
:swapname
.foo:bar.swp
as expected.
This swapfile name should be .foo%bar.swp
Why do you think the swapfile name should contain a
On 2013-08-12, Gary Johnson wrote:
On 2013-08-12, Christian Brabandt wrote:
Oh well, here is an updated version attached. Yes, it is really
attached...
I'm glad to have the updated patch. Thank you. It is working fine
so far. I'll let you know if that changes.
I just noticed an odd
On 2013-09-08, Christian Brabandt wrote:
On Sa, 07 Sep 2013, Gary Johnson wrote:
I just noticed an odd behavior of the spell feature with your patch
included. ...
That is actually a strange behaviour of normal Vim and has nothing to do
with my patch.
...
Here is a patch, that prevents
I've discovered that with 'cindent' set and with 'cinkeys'
containing 0# as it does by default, the command has no effect on
a line having a # in column 1.
To demonstrate this, start Vim as
vim -N -u NONE
and enter this line with the # in column 1:
#define this
Type and . Note that
On 2013-09-24, Christian Brabandt wrote:
On Di, 24 Sep 2013, Gary Johnson wrote:
I've discovered that with 'cindent' set and with 'cinkeys'
containing 0# as it does by default, the command has no effect on
a line having a # in column 1.
To demonstrate this, start Vim as
vim
On 2013-09-25, Ben Fritz wrote:
On Wednesday, September 25, 2013 6:18:00 AM UTC-5, Bram Moolenaar wrote:
For portability and readability I would encourage keeping the # in the
first column.
Agree, that makes sense. And thus the default 'cindent' settings
should also place it in
On 2013-09-27, Andrew wrote:
Hi,
I'd like to install GUI vim (gvim) to GNU/Linux. I use MobaXterm.
I'm no expert on vim configuration because for me (now that I'm not
using HP-UX), it just works. I'll see what I can figure out,
though.
I followed a link
On 2013-09-30, David Barnett wrote:
I've found the built-in ftplugin files are all over the place with
respect to handling 'formatoptions'. Some ftplugins don't touch
it, many clobber useful user preferences. I put together a patch
that batch-changes the ftplugin files to stop clobbering
On 2013-10-02, Bram Moolenaar wrote:
David Barnett wrote:
+Nikolai +Bram +Tim (authors of the majority of these plugins)
I'm confident we can get consensus to at least remove a few of those
formatoptions modifications. You should also add setlocal
formatoptions-=3Dt in pretty much
On 2013-10-02, Amadeus Demarzi wrote:
This is a feature I would find highly useful, and could enable
many plugins to operate more efficiently.
Has this ever come up for discussion? Perhaps there's a reason it
hasn't been done already?
I know with my workflow, I often first cd into a
On 2013-11-13, Alexander Shukaev wrote:
Snapping is a feature of Windows. It makes the window you drag to the edge
to
automatically take half of the screen. I don't know if your current Gnome
supports it.
I'm afraid you misunderstood my post. I also see the vertical split at far
left
on
that
Gary Johnson, also on Windows, experiences the first snap but not the
snap-back; I suppose you both could try and find what is different
between your two installations.
The difference was the L flag in 'guioptions', as discussed in other
posts. I don't use scrollbars, so my _vimrc removes L
On 2013-11-13, Christian Brabandt wrote:
Hi Tony!
On Mi, 13 Nov 2013, Tony Mechelynck wrote:
There is a distribution for Windows, unofficial but built from
official sources and updated more or less regularly, unlike the
official release which is only built once per major/minor version.
On 2013-11-13, Ben Fritz wrote:
I cannot get this patch to apply using either whatever patch
utility is installed on Solaris or GNU patch on Windows. Can you
please post in a different patch format? No matter how I tweak the
patch file, and no matter what I put for the -p value, I cannot
get
On 2013-11-26, Ben Fritz wrote:
On Tuesday, November 26, 2013 2:59:21 AM UTC-6, Jorge Solis wrote:
Le jeudi 21 novembre 2013 10:22:39 UTC+1, Jorge Solis a écrit :
gg=G does not work in vim 7.4
Ok, is true that I need to give more information...
In addition to what Ben wrote,
On 2013-12-27, Rob Owens wrote:
My apologies if this has been reported already. I follow this list, but not
as
closely as I'd like to.
Using gvim 7.4 on Windows, syntax highlighting is on by default. But if I
create $HOME/_vimrc (even if it is empty), syntax highlighting gets turned
On 2013-12-29, Ernie Rael wrote:
On 12/29/2013 8:10 PM, vim wrote:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 189 by jason...: Windows Vim installer adds
Edit with Vim to Explorer context menus, but not to web-browser
context menus
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
2.
On 2013-12-30, Charles Campbell wrote:
Gary Johnson wrote:
On 2013-12-30, Charles Campbell wrote:
Please run the internal debugger (:he netrw-debug) and send me a
trace.
I will try to get that later today.
I'll take a look when you get the trace. That entire sequence of
commands worked
The :tjump command displays the character constant '\n' incorrectly
as '\\n'.
To demonstrate this, create two files, foo.h and bar.h, each
containing this one line:
char newline = '\n';
Execute:
$ ctags foo.h bar.h
$ vim -N -u NONE
:tjump newline
The output is:
# pri
On 2014-01-06, Gary Johnson wrote:
The :tjump command displays the character constant '\n' incorrectly
as '\\n'.
[Description skipped]
Assuming that this behavior is considered a defect and not a
feature, I have attached a proposed patch. It discards each
backslash in the tagaddress
On 2014-01-10, Bram Moolenaar wrote:
Patch 7.4.138 (after 7.4.114)
Problem:Directory change messages are not recognized.
Solution: Fix using a character range literally. (Lech Lorens)
Files:src/option.h
It looks to me that this fix does not use a character range but
allows
On 2014-01-10, Lech Lorens wrote:
On 10 January 2014 20:16, Gary Johnson garyj...@spocom.com wrote:
On 2014-01-10, Bram Moolenaar wrote:
Patch 7.4.138 (after 7.4.114)
Problem:Directory change messages are not recognized.
Solution: Fix using a character range literally. (Lech Lorens
On 2014-01-12, Bohr Shaw wrote:
Sometimes I define an augroup at a file beginning and END it at
the file end. Thus, with the default 'indentexpr' settings, I
would indent almost the whole files one more level, which is not
expected.
And because that arbitrary commands can come after an
On 2014-01-14, Ben Fritz wrote:
On Tuesday, January 14, 2014 11:23:53 AM UTC-6, parcs wrote:
I wonder if instead of printing Scanning %s for each buffer in
the session during keyword completion, Vim could instead print
say Scanning buffers. just once. This would reduce the amount
of
One problem I've found with using the quickfix window is that when
it is open, the quickfix list traversal commands :cn, :cp, etc., no
longer display (n of m) in the command line.
To work around that problem, I set a 'statusline' in my
~/.vim/after/ftplugin/qf.vim which is the same as the value
On 2014-02-02, ZyX wrote:
Historically environment variables cannot be deleted, only made empty.
It's not a good idea to check for existence, check for it being
non-empty instead.
Do not tell it me. There is an example: if PYTHONDUMPREFS variable
is set for debug build of python, no
On 2014-02-03, nag wrote:
Hi,
I am working on RHEL 5.9 systems. The default installed vim editor
is not working fully. My problems:
No syntax highlighting.
No cursor position display
No column and row numbers.
No visual selection (visual block, ctrl+v)
cursor is not appearing at last
On 2014-02-12, Eduardo Lúcio Amorim Costa wrote:
I would like to do some tricks with VIM and so I ask the help of you guys!
It is possible to detect whether a plugin is active/running/open?
You can close a plugin by its name?
You can close a plugin when it loses focus?
The goal is to create
I have a plugin that needs to track the line number of the cursor in
order to display some information in the status line. The
CursorHold event works fine for this except when a buffer is first
opened, as when opening a quickfix error file with -q. I thought
that I could use the BufWinEnter
I created a quickfix error file containing one error and opened it
like this:
$ vim -N -u NONE -i NONE -q make.out
At the bottom of the screen I see the message:
(3 of 3): warning: incompatible imlicit declaration of built-in function
'exit'
So far, so good. But if I look at all
On 2014-02-17, Christian Brabandt wrote:
On So, 16 Feb 2014, Gary Johnson wrote:
I have a plugin that needs to track the line number of the cursor in
order to display some information in the status line. The
CursorHold event works fine for this except when a buffer is first
opened
Hi Christian,
On 2014-02-17, Christian Brabandt wrote:
Hi Gary!
On Mo, 17 Feb 2014, Gary Johnson wrote:
Yes, --cmd does execute its arguments early, before processing any
vimrc file, but I am using it to define an autocommand. It's the
timing of the triggering of the autocommand
Hi Christian,
On 2014-02-17, Christian Brabandt wrote:
Hi Gary!
On Mo, 17 Feb 2014, Gary Johnson wrote:
Hi Christian,
On 2014-02-17, Christian Brabandt wrote:
Hi Gary!
On Mo, 17 Feb 2014, Gary Johnson wrote:
Yes, --cmd does execute its arguments early, before
On 2014-02-18, Christian Brabandt wrote:
Gary,
Am 2014-02-17 23:52, schrieb Gary Johnson:
Thanks for your patience with this and willingness to work it
through. I think we're still not on the same page, however.
In my example I use the following autocommand:
au BufWinEnter * let
On 2014-02-18, Gary Johnson wrote:
With this patch, Vim passes my example, but the plugin still has the
problem of not displaying the right information, so I have some more
debugging to do.
I found the problem. I had been fiddling with the autocommand
events in that plugin and had left
On 2014-02-21, Bram Moolenaar wrote:
Christian Brabandt wrote:
Gary,
Am 2014-02-17 23:52, schrieb Gary Johnson:
Thanks for your patience with this and willingness to work it
through. I think we're still not on the same page, however.
In my example I use the following
On 2014-02-20, Gary Johnson wrote:
On 2014-02-21, Bram Moolenaar wrote:
Christian Brabandt wrote:
Gary,
Am 2014-02-17 23:52, schrieb Gary Johnson:
Thanks for your patience with this and willingness to work it
through. I think we're still not on the same page, however
On 2014-02-25, Johannes Hoff wrote:
Hi!
It's not clear to me how to send pull requests to vim, so here's a
suggestion in email form.
Issues with a plugin are normally sent to the maintainer of the
plugin, whose e-mail address is usually at the top of the plugin, as
it is in the case of the
There is a difference between the expansion of % and Ctrl-R % on the
command line.
I use Dropbox to keep a number of my configuration files, including
my ~/.vim directory, synchronized between various machines running
Linux and Windows.
Today I discovered this file in the ~/Dropbox/vimfiles of a
On 2014-03-04, Christian Brabandt wrote:
Am 2014-03-04 08:15, schrieb Gary Johnson:
There is a difference between the expansion of % and Ctrl-R % on the
command line.
I use Dropbox to keep a number of my configuration files, including
my ~/.vim directory, synchronized between various
On 2014-03-05, Nikolay Pavlov wrote:
On Mar 5, 2014 12:49 AM, Jean-François Bignolles wrote:
Le mardi 4 mars 2014 15:48:49 UTC+1, ZyX a écrit :
Swap files to XDG_RUNTIME_DIR and do so by default.
According to the spec (v0.7):
The lifetime of the directory MUST be bound to the user
On 2014-03-04, Gary Johnson wrote:
On 2014-03-04, Christian Brabandt wrote:
Am 2014-03-04 08:15, schrieb Gary Johnson:
There is a difference between the expansion of % and Ctrl-R % on the
command line.
I use Dropbox to keep a number of my configuration files, including
my ~/.vim
On 2014-03-08, Bram Moolenaar wrote:
Gary Johnson wrote:
On 2014-03-04, Gary Johnson wrote:
On 2014-03-04, Christian Brabandt wrote:
Am 2014-03-04 08:15, schrieb Gary Johnson:
There is a difference between the expansion of % and Ctrl-R % on the
command line.
I use
On 2014-03-11, Charles Campbell wrote:
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
On 2014-03-11, Nikolay Pavlov wrote:
On Mar 11, 2014 9:51 PM, Charles Campbell wrote:
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
On 2014-03-12, Viktor Kojouharov wrote:
I was hoping using the python sys.argv would return the vim path
as the first item, but its filled with garbage? Is there any way
to get it, either from a built-in viml function or from the python
interface?
I don't know about Windows, but on Linux you
On 2014-03-13, Viktor Kojouharov wrote:
On Thursday, March 13, 2014 11:25:35 PM UTC+2, Gary Johnson wrote:
On 2014-03-13, Viktor Kojouharov wrote:
Hi Bram,
I made a patch which adds a new variable, 'v:progpath'. Quite
similar to 'v:progname', but including the full invocation path
On 2014-03-19, Charles Campbell wrote:
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
On 2014-03-19, celelibi wrote:
Le mercredi 19 mars 2014 13:30:13 UTC+1, cptstubing a écrit :
You can still make use of the termcap values by calling
system('tput kPRV') rather than hard coding the escapes. This
would be a little better if vim exposed tgetstr and friends to
avoid the
On 2014-03-12, Nikolay Pavlov wrote:
On Mar 11, 2014 11:53 PM, Gary Johnson wrote:
On 2014-03-11, Nikolay Pavlov wrote:
After my patch was included you can use (mentioned in second or
third message in this thread)
:w !diff %:S
Appending :S is easy enough to be a good
On 2014-05-09, Dominique Pellé wrote:
Gary Johnson wrote:
I triggered a seg fault when I accidentally hit '' instead
of '^' in normal mode. I can easily reproduce it with the attached
viminfo file (compressed for integrity) and by starting vim as
vim -N -u NONE -i vimrc
On 2014-05-30, Christian Brabandt wrote:
Hi Praful!
On Do, 29 Mai 2014, Praful Kapadia wrote:
I have had an annoying issue with gvim 7.4, with patches 1-307.
If I open a large file (e.g. containing 200,000 lines) and use
the global command to delete lines, the operation takes a very
Hi Christian,
On 2014-05-31, Christian Brabandt wrote:
Hi Gary!
On Fr, 30 Mai 2014, Gary Johnson wrote:
On 2014-05-30, Christian Brabandt wrote:
Hi Praful!
On Do, 29 Mai 2014, Praful Kapadia wrote:
I have had an annoying issue with gvim 7.4, with patches 1-307.
If I
On 2013-02-18, Christian Brabandt wrote:
Bram,
one of my annoyances with vim currently is, that when using n/N for
searching the direction depends on the previous search command. But I
usually forget if I initially used / or ? and then my brain gets stuck
whether I need to press n to
On 2013-02-25, Alex Noot wrote:
I work in an environment where I access and manage several hundred
unix servers. However, the amount of time I typically spend on
each server does not justify copying vimrc files around.
I wonder if there's an easier way to load settings on a
per-session
On 2013-03-05, Hong wrote:
On Tuesday, March 5, 2013 8:16:48 AM UTC-8, Lech Lorens wrote:
Wouldn't it be better to use the existing 'cinoptions' entry jN? It's
related to Java...
This is also what I am hesitating at. But people who need the
original 'j' option may not need this
On 2013-03-05, Hong Xu wrote:
On 3/5/13 10:15 AM, Gary Johnson wrote:
On 2013-03-05, Hong wrote:
On Tuesday, March 5, 2013 8:16:48 AM UTC-8, Lech Lorens wrote:
Wouldn't it be better to use the existing 'cinoptions' entry jN? It's
related to Java...
This is also what I am hesitating
On 2013-03-20, John Beckett wrote:
Why would someone who does not want to upgrade their operating
system want to upgrade their editor?
It may not be a matter of not _wanting_ to upgrade their operating
system. They may be stuck using it for one reason or another, while
at the same time they
On 2013-03-19, Christian Brabandt wrote:
Hi Bram!
On Di, 19 Mär 2013, Bram Moolenaar wrote:
Thanks. Looks like some stuff was left behind, commented with //.
The logic is a bit hard to follow, perhaps typebuf_norm_remap() should
only check for remapping and ex_normal_busy is
On 2013-03-16, Bram Moolenaar wrote:
Hayaki Saito wrote:
Hi, Bram
I wrote a quick fix patch for this.
I guess this patch does not fix the fundamental problem.
In $TERM=3Dansi environment, the incomplete sequence ESC [ seems to be =
registered at termcode map.
Thanks for the fix,
On 2013-03-21, Jürgen Krämer wrote:
Hi again,
Jürgen Krämer wrote:
In the same thread somebody else replied with suggesting a script that
probably can be found on vim.org and might be tested more.
Alas, I cannot find the original thread at the moment.
Found it:
On 2013-04-24, Sung Pae wrote:
So I retract my last response: a global-local formatprg is clearly
useful for both prose and code, and comes at the cost of a small
non-breaking change.
Tony Mechelynck's criticism is that it is superfluous. I disagreeน, but
you will have to convince him
On 2013-04-30, Fanhe Fanhed wrote:
matchparen plugin in CursorMoveI autocmd is too slow while typing.
So I wish disable it in insert mode.
I don't understand. I don't even notice a delay when I type the
closing parenthesis and then more characters. Typing after the
closing parenthesis seems
On 2013-04-30, Fanhe Fanhed wrote:
In a 1000+ lines file, typing in the clsoing parenthesis. eg.
func(|)
| means the cursor, go to type.
The cursor will go to blink or shake. So I prefer disable matchparen in insert
mode.
That's odd. I created a 2000+ line file, moved the cursor to the
50%
On 2013-05-01, Fanhe Fanhed wrote:
I just reproduce.
eg: edit tag.c of vim sorce code file, and go to 2000 line number, input the
follow
func(() , snekjglenlnsekgnel|)
'|' means the cursor. Then go to type.
Highlights the leftmost parenthesis and the cursor smoothly.
And
On 2013-05-25, Marcin Szamotulski wrote:
Dear Vim Dev,
I have a proposition for a small but nice feature. Whenever I do
diff then diffo (or diffo!) some settings are lost, for example the
foldmethod is always reset to manual. It would be nice if vim could
restore fdm setting to what it
On 2013-05-26, Christian Brabandt wrote:
Hi Gary!
On Sa, 25 Mai 2013, Gary Johnson wrote:
On 2013-05-25, Marcin Szamotulski wrote:
Dear Vim Dev,
I have a proposition for a small but nice feature. Whenever I do
diff then diffo (or diffo!) some settings are lost, for example
On 2013-05-27, Marc Weber wrote:
Excerpts from Gary Johnson's message of Mon May 27 21:47:26 +0200 2013:
Would you please explain this problem more fully? I don't observe
it. Vim always loads the plugins in my ~/.vim/after directories.
vam, vundle, pathogen (and others) do no longer
On 2013-05-27, Marc Weber wrote:
Let's keep it short and sipmle. Try this:
mv .vim .other
then in your .vimrc add a early line like this:
:set rtp=~/.other
Now it should behave normal, because you told Vim where your .vim
directory is.
It depends what you mean by normal. It will
On 2013-05-27, Marc Weber wrote:
You'll notice that the ftdetect files and the after files from the
plugin were not sourced.
I would expect the ftdetect files from the plugin to not be sourced
because the plugin wasn't added to 'rtp' until after the sourcing
was done by the :filetype command.
On 2013-05-29, Shougo wrote:
Hello.
I developed completeselect option feature in Vim.
It determines how to select candidate in ins-completion.
The possible values are:
0 select and insert first candidate
1 select first candidate but not insert
2 no selected candidate
I think it
On 2013-05-30, Ron Aaron wrote:
Heh :)
I didn't bother trying to investigate it much, just thought it was
a pretty funny idea.
What surprised me was how much my finger memory depends on
context. When I'm editing text, I don't even think about which of
hjkl I'm typing to move some
On 2013-05-31, John Szakmeister wrote:
One issue I've run into a few times is that when jumping to a tag, I'd
really like to center the line in the middle of the screen after
jumping. The problem is that I also want to be able to use the
taglist functionality, and I'd like this to work when
On 2013-05-31, A. S. Budden wrote:
Forwarding to vim-dev as requested... any cscope/vim experts here?
Not an expert but a daily user.
When using cscope, the path as provided to the cs add command is
used. If the working directory changes, this is potentially no longer
valid. This causes
1 - 100 din 860 matches
Mail list logo
