On Mon, July 29, 2013 14:59, Dimitar DIMITROV wrote:
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches any
char including end of line and * is greedy
/pattern\_.* does what I expect: it matches from pattern to
On Mon, July 29, 2013 16:14, Dimitar DIMITROV wrote:
Hi all,
Not sure why /\_.* matches at every line Vs only once...
I would expect a single match at start of file because \_. matches
any
char including end of line and * is greedy
/pattern\_.* does what I expect: it matches from
Hi Ingo!
On Fr, 26 Jul 2013, Ingo Karkat wrote:
Hello Vim developers,
Patch 7.3.590 allows to set the visual selection directly via the marks
' and '. I've found a problem with :set selection=exclusive (while
developing a custom mapping): When the first selection after Vim startup
is
Hi Mike!
On So, 21 Jul 2013, Mike Williams wrote:
On 20/07/2013 10:13, LCD 47 wrote:
I believe this can be fixed with a counter that means something
along the lines of: this line is longer than tw, and it has no
breaking point for the first X characters. Then X would be updated
every
On Mi, 24 Jul 2013, Jeroen Budts wrote:
I have a feature request for gvim, I'm not sure if I should ask it
here or on the dev list?
Would it be possible to add support for strikethrough text in Gvim?
Since gvim can already display bold, italic, underline and undercurl
text I guess it can't
On Tue, July 16, 2013 16:57, Benjamin Fritz wrote:
Eric Van Dewoestine found this while investigating an eclim issue I was
having.
When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to that of the buffer having its variable set. I think this
should not happen.
On Mon, July 29, 2013 19:32, Seungbeom Kim wrote:
The 'equalalways' option makes all the windows the same size after a
window is split or closed. However, it doesn't when the Vim window
(either
the terminal or the GUI) is resized. I hear many people run [g]vimdiff
or
':vsplit', enlarge the Vim
On Wed, July 31, 2013 17:17, Ben Fritz wrote:
A while ago there was a similar problem where :vimgrep was causing
directory changes due to 'autochdir'. The fix for :vimgrep also had to
deal with autocmds which might change the directory.
Are you talking about issue 72? As far as I know, this
Hi Bram!
On Mi, 31 Jul 2013, Bram Moolenaar wrote:
[Christian, for some reason quoted long lines are wrapped badly]
Yeah, Squirrelmail messed it up. I usually reformat mails using Vim (of
course! ;)), but forgot this time.
[adjust Vim windows, when vim is resized and 'equalalways' is set]
On Fri, August 2, 2013 04:46, richard emberson wrote:
Interesting ...
If you define a file XXX with the content:
vv
1
2
3
4
5
6
7
8
9
function! Load()
let list = [
\ {
\ 'filename': 'XXX',
\ 'lnum': 2,
\ 'col': 5,
\ 'vcol':
Hi Benjamin!
On Di, 06 Aug 2013, Benjamin R. Haskell wrote:
On Tue, 6 Aug 2013, Ben Fritz wrote:
On Tuesday, August 6, 2013 11:21:02 AM UTC-5, Benjamin R. Haskell wrote:
On Tue, 6 Aug 2013, Dimitar DIMITROV wrote:
Hi all,
If you open the latest vim (vim -nNX -u NONE) and insert these
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 'syn match Error /\.c\zs\n.*/'
Scroll down a bit
On Do, 08 Aug 2013, glts wrote:
When I run an external command like :!find I can see the output in the
messages area and the prompt
Press ENTER or type command to continue
By reflex I hit u to scroll up and I got
Press ENTER or type command to continuePress ENTER or type command to
Bram,
I had a problem with the NrrwRgn Plugin that seems to hang vim.
Debugging it, I could make vim hang with this input:
vim -N -c 'try|noa sview $VIMRUNTIME/doc/options.txt|finally |bw|endtry
(It seems my .vimrc interferes, not sure which setting does).
This hangs in buffer.c
,
|
On Sa, 10 Aug 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
I had a problem with the NrrwRgn Plugin that seems to hang vim.
Debugging it, I could make vim hang with this input:
vim -N -c 'try|noa sview $VIMRUNTIME/doc/options.txt|finally |bw|endtry
(It seems my .vimrc
On Sa, 10 Aug 2013, Gary Johnson wrote:
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;
int
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 fixes, can we have this patch included
On Fr, 09 Aug 2013, Ben Fritz wrote:
On Friday, August 9, 2013 11:20:37 AM UTC-5, Dimitar DIMITROV wrote:
I don't see anything wrong. For me it selects all text from the opening {
to the closing }. What do you
see?
I tried gvim 7.3.822 on Windows, and also vim (not gvim) 7.4b.14 on
On Do, 08 Aug 2013, Dimitar DIMITROV wrote:
As per the subject :)
Can you check, whether the attached patch fixes it for you?
regards,
Christian
--
Was die Welt in diesem Augenblick sucht, ist viel weniger ein
Gleichgewicht als eine Sprache.
-- Jean Giraudoux
--
--
You
On Fr, 09 Aug 2013, Gary Johnson wrote:
In your video, you paged forward and back using ^F and ^B. I just
tried that and it works for me, too. However, scrolling forward and
Ah, from your initial description it wasn't clear to me, that scrolling
actually means using up/down and not paging
On Tue, August 13, 2013 01:00, Einar Lielmanis wrote:
Encrypted file contents are destroyed, if something (e.g autocmd)
triggers write event, while user is being asked for password.
To repro:
1. have an encrypted.txt ready (:X)
2. gvim, :au focuslost * w
3. :e encrypted.txt, don't type in
Hi Péter!
On Mi, 14 Aug 2013, Péter Kasza wrote:
Dear vim_dev list!
I've been using the tslime plugin for some time now, but after an update it
somehow doesn't seem to work anymore. The call to system(tmux load-buffer
-, buf) hangs forever. I can make it work by changing the
On Di, 13 Aug 2013, Christian Brabandt wrote:
On Tue, August 13, 2013 01:00, Einar Lielmanis wrote:
Encrypted file contents are destroyed, if something (e.g autocmd)
triggers write event, while user is being asked for password.
To repro:
1. have an encrypted.txt ready (:X)
2. gvim
On Thu, August 15, 2013 14:57, Dimitar DIMITROV wrote:
Hi all,
I've noted this behaviour with omaps: in my omap I jump to a place in the
buffer, then after an if test I select visually something. So all is good
when
the test succeds and only the visual area gets modified. Now if the test
On Thu, August 15, 2013 15:53, Dimitar DIMITROV wrote:
Hi all,
I've noted this behaviour with omaps: in my omap I jump to a place in
the
buffer, then after an if test I select visually something. So all is
good
when
the test succeds and only the visual area gets modified. Now if the
test
On Mon, August 19, 2013 11:30, John Beckett wrote:
Dimitar DIMITROV wrote:
Now try :ec getpos('.') - [0, 4, 17, 0]
Move away and :call setpos('.',[0,4,17,0])
If you use up down k or j you will not move just
above/below the char but in some weird location
Say the cursor is in column 20, then
On Do, 15 Aug 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Wouldn't it be a good idea, to have the file set readonly for as long it
hasn't been encrypted (e.g. the current windows behaviour)?
You mean, until it has been decrypted. That makes sense.
Actually, when a file
Hi Jesus!
On So, 18 Aug 2013, Jesus Antonio Santos Giraldo wrote:
Not to mention that there is already a patch for it... :(
All whitespace as something different? Can't you use the conceal feature
for that?
:syn match MyWhitespace /\s/ conceal cchar=_ containedin=ALL
:setl conceallevel=2
On Mo, 19 Aug 2013, Christian Brabandt wrote:
May be another optional parameter to the setpos() function, that
if given specifies the desired cursor position?
Like the attached patch does.
regards,
Christian
--
Es gehört viel dazu, eine Brücke hinter sich abzureißen, wenn man auch
keine vor
On Tue, August 20, 2013 09:02, Ingo Karkat wrote:
Note that concealing has to extend the existing syntax, which can break
it.
Well changing the syntax rules is of course a way of breaking it, but
I think it should work well enough most of the times. And while I am not
very proficient with
Hi Marius!
On Di, 20 Aug 2013, Marius Gedminas wrote:
Vim 7.4 broke my svn filetype plugin (http://mg.pov.lt/vim/ftplugin/svn.vim).
The plugin opens a new split window and puts the output of 'svn diff' in
there when I run 'svn commit'. This window gets some attributes set,
including
On Thu, August 22, 2013 07:40, Marius Gedminas wrote:
On Tue, Aug 20, 2013 at 05:15:49PM +0200, Christian Brabandt wrote:
snip patch
Your patch fixes the bug, thanks!
What are the next steps to get it included upstream?
Bram will include it eventually.
regards,
Christian
--
--
You
On Thu, August 22, 2013 17:23, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 19 Aug 2013, Christian Brabandt wrote:
May be another optional parameter to the setpos() function, that
if given specifies the desired cursor position?
Like the attached patch does.
Hmm, I wonder
On Do, 22 Aug 2013, Nikolay Pavlov wrote:
I bet there is a bunch of scripts using 4-variable lets. Simple grep over
What do you mean with 4-variable lets?
the mess in $HOME/.vam (I hold all but my plugins there) found at least
LaTeX_box plugin (ftplugin/latex-box/common.vim) and
[redirected to vim-dev, it is better suited there]
On Do, 22 Aug 2013, Andrew Stewart wrote:
On 21 Aug 2013, at 19:05, Josh wrote:
This is already a feature
request:https://code.google.com/p/vim/issues/detail?id=117q=Sign .
Bram,
attached patch adds a 'signcolumn' option, that let's the
On Mi, 21 Aug 2013, Dimitar DIMITROV wrote:
Tested with the latest version of Vim from Mercurial.
After a * search, then cgn and then . to repeat it for all matches,
I cannot continue past the end of file and change any matches before my
initial position
Try the attached patch.
regards,
On Do, 22 Aug 2013, Bohr Shaw wrote:
However, the document says the register 1 always hold the text
deleted by the delete operator with these movement commands:|%|, |(|,
|)|, |`|, |/|, |?|, |n|, |N|, |{| and |}|.
I think the help is clear here.
,[ :h quote1 ]-
| Numbered register 1
Bram,
this patch adds a digraph function. This allows plugin writers to
generate needed digraphs easily and one does not need such a crude
workaround anymore:
:exe :norm! :let x = '\C-ka:'\cr
regards,
Christian
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type
On Do, 22 Aug 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Bram,
this patch adds a digraph function. This allows plugin writers to
generate needed digraphs easily and one does not need such a crude
workaround anymore:
:exe :norm! :let x = '\C-ka:'\cr
Thanks, I'll add
completion entry selection after backspace
https://groups.google.com/d/topic/vim_dev/AcTTNQzfB2o/discussion
In this thread, Christian Brabandt sent two patches, and the first patch
has this problem. The second patch didn't have such problem and it was merged
as the patch 7.3.854. But four months later
On Mon, September 9, 2013 12:31, Mike Williams wrote:
On 09/09/2013 10:56, Nikolay Pavlov wrote:
On Sep 9, 2013 1:40 PM, Mike Williams
mike.willi...@globalgraphics.com
wrote:
I had tried calls to escape(..., '\') and that made no difference.
Where did you do that? You need to make sure, that
On Wed, September 11, 2013 14:07, Dmitry Frank wrote:
So, is this issue fixed now? If yes, then which patch should fix it?
7.4.018
regards,
Christian
--
--
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
On Wed, September 11, 2013 13:43, jan.stoc...@t-online.de wrote:
Hi,
if you read with
- Vim 7.4.22 (32bit)
- Windows 7 (x64)
from a command line output by
:[range]r[ead] [++opt] !{cmd}
and using parenthesis the command is completly broken.
On Wed, September 11, 2013 15:35, Jan Stocker wrote:
:r! cmd /c echo B(la)h
is broken. It is neither executed nor a piped outline file is
created, so VIm can't read the output and throws a read error on
temp
file. This is working under 7.3 without problems.
Anyone an idea
On Wed, September 11, 2013 21:10, Andrew McNabb wrote:
Vim (vim-enhanced-7.4.0-2.fc19.x86_64 on Fedora) is currently reporting
'Found a swap file by the name .linalg.py.swp' along with
'process ID: 4157 (still running)'.
However, process 4157 is not a Vim process:
$ readlink /proc/4157/exe
On Tue, September 17, 2013 23:36, Lorenzo Bercelli wrote:
Oh God sorry I forgot to attach the patch, here it is.
You probably want :setlocal instead of :set in the filetype plugin.
regards,
Christian
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
On Mi, 18 Sep 2013, Christian Brabandt wrote:
On Mi, 18 Sep 2013, Christ van Willegen wrote:
I accidentally searched the following
/\(
This gives me the error message
E54: Unmatched \(
E54: Unmatched \(
twice.
This happens, because your 're' setting is 0. That means
On Do, 12 Sep 2013, shawn wilson wrote:
Can vim be made to DWIM here? I did a quick search and found I'm not the
only one who has run into this. For example:
http://briancarper.net/blog/341/
Just to re-explain what I want: when you visually select a block, you can
change or insert and it
On Thu, September 19, 2013 17:00, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Do, 12 Sep 2013, shawn wilson wrote:
Can vim be made to DWIM here? I did a quick search and found I'm not
the
only one who has run into this. For example:
http://briancarper.net/blog/341/
Just
On Do, 19 Sep 2013, Christian Brabandt wrote:
On Thu, September 19, 2013 17:00, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Do, 12 Sep 2013, shawn wilson wrote:
Can vim be made to DWIM here? I did a quick search and found I'm not
the
only one who has run
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 attach I hope) has a null character
(represented
Hi Bram!
On Fr, 20 Sep 2013, 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
Hi Dimitar!
On Mo, 23 Sep 2013, Dimitar DIMITROV wrote:
Hi,
Here is what I tried:
:setlocal spelllang=bg spell
then
:spelldump
and all I get is an empty window
'local' is the issue, with a simple :set it all works.
I reckon the solution would be to take the settings from the current
On Mo, 23 Sep 2013, Christian Brabandt wrote:
On Mo, 23 Sep 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Hi Dimitar!
On Mo, 23 Sep 2013, Dimitar DIMITROV wrote:
Hi,
Here is what I tried:
:setlocal spelllang=bg spell
then
:spelldump
On Mo, 23 Sep 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Hi Dimitar!
On Mo, 23 Sep 2013, Dimitar DIMITROV wrote:
Hi,
Here is what I tried:
:setlocal spelllang=bg spell
then
:spelldump
and all I get is an empty window
'local' is the issue
Hi Tim!
On Mo, 23 Sep 2013, Tim Chase wrote:
Playing around with the latest VimGolf challenge[1], I was attempting
to use gi to add some text, then control+O (or backtick-backtick) to
jump back to where I had issued the gi. I was somewhat surprised to
find that gi doesn't modify the
Hi Ingo!
On Sa, 21 Sep 2013, Ingo Karkat wrote:
On 21-Sep-2013 05:38 +0200, David Woodfall wrote:
I've noticed that the default spellcheckcap setting marks words as bad
after an ellipsis if they are not capitalised.
In fiction writing at least it is common to have an ellipsis and a
On Sat, September 21, 2013 21:02, Ingo Karkat wrote:
Another observation: (With the default settings,) when there's an empty
line before a lowercase word, e.g. That
word --, it always gets highlighted (except when 'spellcapcheck' is
completely empty, but also when it's set to something
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 -N -u NONE
and enter this line with the # in
On Di, 24 Sep 2013, Gary Johnson wrote:
On 2013-09-24, Christian Brabandt wrote:
I guess, the intention is, that in C code the defines need to be in the
first column.
Thanks for checking that.
[...]
Vim's behavior looks to me like a mistake in someone's understanding
of C.
I
On Wed, September 25, 2013 13:18, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Di, 24 Sep 2013, Gary Johnson wrote:
On 2013-09-24, Christian Brabandt wrote:
I guess, the intention is, that in C code the defines need to be in
the
first column.
Thanks for checking
On Wed, September 25, 2013 16:43, Axel Bender wrote:
Please compare the following case using the current (7.4.35) and a
previous (7.4ß = the last I can return to) version of gvim (here: Windows
7 64 bit).
In the current version a selection - after being copied over with the
contents of a
On Wed, September 25, 2013 15:21, Bram Moolenaar wrote:
'cinoptions' is for 'cindent' options.
So do we agree, that cino=#N with N being non-zero would allow to
indent 'defines'?
regards,
Christian
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Wed, September 25, 2013 15:21, Bram Moolenaar wrote:
'cinoptions' is for 'cindent' options.
So do we agree, that cino=#N with N being non-zero would allow to
indent 'defines'?
No one
On Mi, 25 Sep 2013, Christian Brabandt wrote:
On Wed, September 25, 2013 16:43, Axel Bender wrote:
Please compare the following case using the current (7.4.35) and a
previous (7.4ß = the last I can return to) version of gvim (here: Windows
7 64 bit).
In the current version a selection
On Mi, 25 Sep 2013, Ingo Karkat wrote:
On 25-Sep-2013 15:21 +0200, Bram Moolenaar wrote:
Christian Brabandt wrote:
Hi Tim!
On Mo, 23 Sep 2013, Tim Chase wrote:
Playing around with the latest VimGolf challenge[1], I was attempting
to use gi to add some text, then control+O
Hi studog!
On Do, 26 Sep 2013, studog wrote:
Full version info below; tl;dr == 7.3. I know this is old, but it's what's on
the server and I can't/don't have time to do anything about it.
I am editing source that has been badly converted dos=unix in the past, and
all the^M
lines^M
look
(CC'ing vim-dev)
On Do, 26 Sep 2013, studog wrote:
On Thursday, September 26, 2013 2:40:47 PM UTC-4, Christian Brabandt wrote:
On Do, 26 Sep 2013, studog wrote:
Is this a known issue? Is it fixed in 7.4?
When using f/t, Vim gets the following char literally, which means, you
don't
On Do, 26 Sep 2013, ZyX wrote:
But if t/T/f/F/r/gr are changed to accept C-v and C-k it will make
Actually, they do accept C-K.
them more consistent with other *normal-mode* things like `d`
operator: currently t/T/f/F/r/gr are not cancelled by C-c. In fact
Yeah, they accept C-C and try to
Bram,
there seems to be a problem with substitute¹:
#v+
~$ vim -u NONE -N :echo substitute('-bb', '\zeb', 'a', 'g') -c ':q!'
-aabab
Press ENTER or type command to continue
~$
#v-
That looks wrong. Attach is patch that fixes it.
¹)http://stackoverflow.com/questions/19041109
Mit freundlichen
Bram,
when using Visual-block insert or append, you can't use the cursor keys
to move the cursor to a different location. This will confuse vim.
e.g. consider this block
aaa
bbb
ccc
Put the Cursor on the first a, and press
lC-VjjlllIRightRightSpaceSpace
The result will look like
On Sa, 28 Sep 2013, Bram Moolenaar wrote:
Can't you just use the example you gave above? No CTRL-O there.
Here is an updated patch, including a test. Using :exe one can use the
cursor keys just like normal, while if you use Cursor Right literally in
the test file, this will look like ^[OC,
On Mon, September 30, 2013 17:53, eckes wrote:
+1 have this demand too:http://stackoverflow.com/q/19097216/520162
While I like the idea of having a :cdo and :ldo command, for the time
being, you can script yourself something similar, e.g.
http://article.gmane.org/gmane.editors.vim/92691
On Sun, September 29, 2013 16:01, ZyX wrote:
Try the following code:
let d={'0d': 1}
if 0 (d.0d)
endif
. This code is completely correct if you replace `if 0` with `if 1`, but
with `if 0` it throws
Error detected while processing /home/zyx/tmp/vim/subscript-bug.vim:
Hi Ryan!
On Mi, 02 Okt 2013, Ryan Carney wrote:
I think I may have found a bug, I have list the steps to reproduce it.
1. open a new buffer :tabe or :e test
2. put two single digits on different lines
3. search using the regex '\d' (without quotes)
4. put your cursor before or on the
On Mon, October 7, 2013 12:31, Wiktor Ruben wrote:
Hello,
I use Vim 7.4.052.
Help says that C-\C-O is like CTRL-O but don't move the cursor,
but:
vim -u NONE
:set nocp
:set ruler
:set ft=cpp
:set formatoptions+=r
Put the text below:
}Left//fooCR
You should have:
//foo
//|}
On Di, 08 Okt 2013, Urtica dioica wrote:
Open a blank Vim (I'm using 7.4.52), and type this:
3graqqY:s/a/b/g|s/b/c/gCRpq@q
(Since there are 3 as, and the 'report' default is 2, both :s commands
report the number of changes, which triggers a Press ENTER prompt. But the
bug applies to
On Di, 08 Okt 2013, Urtica dioica wrote:
I tried your patch. It seems to stop duplication when recording a
macro with q, but not when recording keystrokes to a file with vim -w.
Try this updated patch.
regards,
Christian
--
Entweder das Neueste oder das Älteste (aus der Jugend) gefällt auf
On Mi, 09 Okt 2013, Wiktor Ruben wrote:
Hello,
The subject is self-explanatory. I use Vim 7.4.052. Steps to
reproduce:
vim -u NONE
Enter the text below:
(foo foo bar)
Put cursor on the first 'foo' and try '[('. It works. Put cursor on the
second foo and try '[(' once again. It
Hi Bram!
On Mi, 09 Okt 2013, Bram Moolenaar wrote:
Yasuhiro Matsumoto wrote:
Bram, why you remove this patch from todo list?
On So, 13 Okt 2013, Nikolay Pavlov wrote:
You have no way to unconditionally disable mappings,
set paste
statusline,
set ls=0 stl=
CursorHold
set ei=CursorHold
Thus such command makes exactly no sense.
We also have :syntax on, filetype plugin on and so on. So I think it
makes
On Sa, 28 Sep 2013, Bram Moolenaar wrote:
Dimitar Dimitrov wrote:
Hi,
The call to histdel below doesn't seem to be doing what I want it to do.
It doesn't delete my 3 search patterns added by the 2 :substitute and
the :global calls. Not sure what it does exactly, it seems to delete
Hi Ken!
On Sa, 12 Okt 2013, Ken Takata wrote:
2013/07/31 Wed 4:56:39 UTC+9 Christian Brabandt wrote:
Attached is a patch to try out. It seems to work for me with GTK and
Motif Gui. I am a Unix gui and can't say for sure the code for Windows
and Mac is actually correct and works, though
Bram,
when using visual block_mode and replacing the selected block with
Enter, Vim currently does not break the line, but inserts the
linebreak literally, e.g. when doing this:
10o12345ESC9k02lC-V9jrCR you are left with:
12^M45
12^M45
12^M45
12^M45
12^M45
12^M45
12^M45
12^M45
12^M45
12^M45
Hi Bram!
On So, 20 Okt 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Bram,
when using visual block_mode and replacing the selected block with=20
Enter, Vim currently does not break the line, but inserts the=20
linebreak literally, e.g. when doing this:
10o12345ESC9k02lC
On Tue, October 22, 2013 14:07, Anatoli Sakhnik wrote:
Hello, vim developers!
I've noticed that the operator-pending mode cursor in GUI may be delayed
according to 'timeoutlen' when a custom map is defined. Judge by yourself:
$ gvim -u NONE -N
:map cs nop
:set timeoutlen=1000
iHelloesc
Hi James!
On Mo, 21 Okt 2013, James McCoy wrote:
On Sat, Oct 19, 2013 at 03:04:45PM +0200, Christian Brabandt wrote:
Bram,
when using visual block_mode and replacing the selected block with
Enter, Vim currently does not break the line, but inserts the
linebreak literally, e.g. when
Hi Bram!
On Mo, 21 Okt 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
Bram,
when using visual block_mode and replacing the selected block with=20
Enter, Vim currently does not break the line, but inserts the=20
linebreak literally, e.g. when doing
On Di, 22 Okt 2013, Anatolii Sakhnik wrote:
Вівторок, 22 жовтня 2013 р. 15:32:13 UTC+3 користувач Christian Brabandt
написав:
I see that only, when d is mapped and one is using the normal mode 'd'
command, which is clear, since Vim needs to wait if you are using the map
On So, 27 Okt 2013, Alexander Shukaev wrote:
I've stumbled across the issue with syntax highlighting. Rather than
rewriting, I'll post a link to the question on Stack Overflow: Vim: Syntax
Highlighting Doesn't Work with Recursive `nextgroup` Across Newlines When
On So, 27 Okt 2013, Ingo Karkat wrote:
In the first line, group 'A' prefers a following 'B' via the
nextgroup=B, and this does work for the next 3 'b' in the same line.
It apparently fails in the second line, even though skipnl has been given.
Ah, now I see. The MyComments match confused me.
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 website:
On Di, 05 Nov 2013, zhaocai wrote:
I am against this patch though as I do want to receive these messages. This
should be fixed by adding appropriate flag (such as s//e) to whatever
method that is giving these messages if you are sure there are no ways to
use other methods (e.g.
On Wed, November 6, 2013 05:26, Bram Moolenaar wrote:
Patch 7.4.073
Problem:Setting undolevels for one buffer changes undo in another.
Solution: Make 'undolevels' a global-local option. (Christian Brabandt)
Files: runtime/doc/options.txt, src/buffer.c, src/option.c,
src/option.h
Bram,
while investigating tests for makeing 'ul' settings global-local, I see
some problems with the undo state.
./vim -u NONE -N -c ':set ul=5'
1):for i in range(1,10)| call feedkeys(o.i.\e, 't')|endfor
(i.e. make sure echo line is a single undoable change).
2)(undo as long as it is possible,
Hi Bram!
On Mi, 06 Nov 2013, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Wed, November 6, 2013 05:26, Bram Moolenaar wrote:
Patch 7.4.073
Problem:Setting undolevels for one buffer changes undo in another.
Solution: Make 'undolevels' a global-local option
On Thu, November 7, 2013 03:04, Bram Moolenaar wrote:
Christian Brabandt wrote:
./vim -u NONE -N -c ':set ul=5'
1):for i in range(1,10)| call feedkeys(o.i.\e, 't')|endfor
(i.e. make sure echo line is a single undoable change).
2)(undo as long as it is possible, e.g. press u 6 times)
3
On Wed, November 6, 2013 22:54, Leonard Ehrenfried wrote:
I really hope I don't hurt anyones's feeling by saying that the current
vim.org website looks a little bit dated. I also happen to think that it
doesn't do a very good job of explaining what vim is and how to install
it. Lastly, it
On Thu, November 7, 2013 03:26, Bram Moolenaar wrote:
Thanks. Are you scared of the number 100? :-)
kind of. The more tests we add, the harder it is to find one, that can
be used for adding more tests. So I figured, it would make sense, to
give them more meaningful names, so one can make an
Hi Bram!
On Do, 07 Nov 2013, Christian Brabandt wrote:
On Thu, November 7, 2013 03:26, Bram Moolenaar wrote:
Thanks. Are you scared of the number 100? :-)
kind of. The more tests we add, the harder it is to find one, that can
be used for adding more tests. So I figured, it would make
1 - 100 din 4285 matches
Mail list logo