>> On Mo, 23 Sep 2013, Bram Moolenaar wrote:
>>
>> > Christian Brabandt wrote:
>> >
>> > > Hi Dimitar!
>> > >
>> > > On Mo, 23 Sep 2013, Dimitar DIMITROV wrote:
>> > >
>> > > > Hi,
>> > >
>> Test done with the latest version out of mercurial
>>
>> Hi,
>>
>> Here is a bug: if you place your cursor at the end of a line and try dw,
>> all that happens is the character under cursor is deleted but the line
>> is not joined with the one below.
>
>hm, dw deletes just the last character on
w and
use them in the new results window.
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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 inf
usual settings but not with :se ve=all. In that case,
if you go beyond the end of a line the joining of lines happens but your cursor
position changes to the end of line instead of remaining in its place.
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka
>> 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.
That fixes it, thanks
Dimitar
--
--
You re
Hi,
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
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov
>> On Mon, Aug 19, 2013 at 3:53 PM, Manuel Ortega 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:
>>
>> -n[args]
>> -com[plete]
>> -
>> If you use k or j you will not move just above/below the char
>> but in some weird location
>
>My vim 7.4 doesn't do this, but 7.3.547 does, so it looks like a bug that's
>been fixed.
I used version 7.4 with Included patches: 1-5 so not sure how come you're not
seing it.
Also used: vim -n
Move away and :call setpos('.',[0,4,17,0])
If you use k or j you will not move just above/below the char but
in some weird location
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vim_dev"
>> 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
>> fails, no visual selection is created and th
on my motion in the buffer
instead of being cancelled. Is there a way to tell in the test, if it fails to
cancel the omap?
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
>> Hi,
>>
>>
>> First vim -nNX -u NONE ad :se ve=all
>> Then enter the following test with X representing the cursor:
>>
>>
>> if {
>>
>>
>>
>>
>> X
>>
>>
>>
>>
>> }
>>
>>
>> Now vaB is wrong
>>
>
>I don't see anything wrong. For me it selects all text from the opening { to
>the closi
Hi,
First vim -nNX -u NONE ad :se ve=all
Then enter the following test with X representing the cursor:
if {
X
}
Now vaB is wrong
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vi
Hi,
Not sure this is an actual issue.
In a buffer enter this text: loRem lorem
then set hls ic
Now search for /loRem and you have 2 matches
Finally, after set smartcase the highlighting is not refreshed
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka
>> As per the subject :)
>>
>
>Verified that . has no
effect after a gUgn that capitalized a match for the last search, on
7.3.822 Windows, and also 7.4b.14 on Solaris.
Doesn't work for g~ either (or ~ with 'top set). Haven't checked the others
Dimitar
--
--
You received this message fr
As per the subject :)
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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/ma
ot an issue. Just a weird historical default.
Indeed, I was editing my ~/.dir_colors and it surprised me.
I should only use these defaults for nroff files, otherwise :se para=
Cheers
>For more info, see:
>:help paragraph
Dimitar Dimitrov
--
--
You received this message from the "vim_d
.cgm 01;35
.emf 01;35
then go to the top (gg) and try vap...
There is an issue
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
Hi,
I was reading :h40.3 and tried the example from line 446. That never worked
because
FileWritePre is irrelevant and
BufWritePre should be used
Cheers
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vi
le:
>
> aann
> nnbb
>
> and search for
> /n\_[n]*
All I am trying to say is that this is a *single* match (/n\_[n]* matches *all*
n in your example) so a single n move would make more sense,
same as in this non-multiline pattern: aa, /a* is a single match
and n won't mov
t; I think, Vim has always done this and restarted trying to match
> after linebreaks.
>
> If you want to keep matching at the start of the file, use the \%^ atom.
>
> regards,
> Christian
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
ey: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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 b
2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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 subscri
and how it is to compile the
> program.
Ok, I realize it now. I should have used a Makefile. Also the message states it.
But in fact there is still an issue. If you fist open a perl file (as an
example)
and right after you open a c file, makeprg is not updated. Is this intentional
and the u
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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
se.
>
> Marc Weber
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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/ma
> > Hi list,
> >
> > >From :h:g (line 57) I get it :g9pattern9ACTION shouldn't work, but it does.
> > These work as well:
> >
> > :g"pattern"ACTION
> > :g|pattern|ACTION
> >
> > Regards
> >
> >
> > D
other
parts.
> Vim sucks in many ways - but on average it is very helpful for me.
>
> You could try =repeat('Hello', insanely-large-int) as
> alternative - maybe its faster, maybe its not, I don't want to wait
> 50 min for this case unless there is a use case.
&g
Hi list,
>From :h:g (line 57) I get it :g9pattern9ACTION shouldn't work, but it does.
These work as well:
:g"pattern"ACTION
:g|pattern|ACTION
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message
Hi,
After reading the docs about -u, I can't see it mentioned that in that case
$MYVIMRC wouldn't be setup.
But it isn't.
Try with vim -u ~/.vimrc
Regards
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message fr
2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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 su
> 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:
> >
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
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the &qu
heers
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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 receiv
Jul 8 2013 13:51:44)
Included patches: 1-2
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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,
luded patches: 1-2
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
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/maillis
No, I didn't right ZZ but zz. It's different :)
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
De : tooth pik
À : vim_dev@googlegroups.com
Envoyé le : Lundi 8 juillet 2013 14h36
Objet : Re: vim stops
On M
Version:
VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44)
Included patches: 1-2
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
-lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm
-lelf -lcurses -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config
-lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynami
c
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You receive
>>
>>>
>>> On Wed, Apr 17, 2013 at 11:06 AM, Ben Fritz
>>> wrote:
>>> >
>>> > See image attached to my next message for what I see.
>>> >
>>> > And please bottom-post.
>>> >
>>> Thanks Ben, can't see clearly your image but maybe indeed the bug was
>>> fixed in your version. Here is what I see (att
Dimitar wrote:
>
> On Wed, Apr 17, 2013 at 11:06 AM, Ben Fritz wrote:
> >
> > See image attached to my next message for what I see.
> >
> > And please bottom-post.
> >
> Thanks Ben, can't see clearly your image but maybe indeed the bug was fixed
> in your version. Here is what I see (attached
Hi Ben,
what I meant is modeless selection (:h modeless) so try to select the text
after using :e for instance (and before hitting or ^c of course)
Cheers
Note: my gVim version is: 7.3.409
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka
Hi,
Anyone knows why in gVim modeless-selection distorts all characters which makes
the selection quite unreadable?
Dimitar
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
> On Tuesday, February 12, 2013 8:38:02 AM UTC-6, Dimitar DIMITROV wrote:
> > Hi Ingo,
> >
> > You did explain the help for 'unnamedplus but there is still the problem I
> > described:
> >
> >
> >
> > 1. gvim -NX -u NONE -c 'se cb^
rt
-lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM
-lICE -lm -lelf -lcurses -lacl -lattr -lgpm -ldl
-L/usr/lib/python2.7/config -lpython2.7 -
lpthread -ldl -lutil -lm -Xlinker -export-dynamic
---
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
--
> On 11-Feb-13 14:55:48 +0100, Dimitar DIMITROV wrote:
>
> > [7 lines deleted]
> >
> > Also, I can't make sense of the help for 'unnamedplus.
> > It reads that all operations except yank go to "+, then first thing it says
> > after is yank cop
reetype
-lfontconfig -lgconf-2 -lgthrea
d-2.0 -lgmodule-2.0 -lrt -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11
-lXdmcp -lSM -lICE -lm -lelf -lcurses -lacl -lattr -lgpm -ldl
-L/usr/lib/python2.7/config -lpython2.7 -
lpthread -ldl -lutil -lm -Xlinker -export-dynamic
---
GPG Key
> > Hi all,
> >
> > I think the following might (I am testing with Vim 7.3.409) be a bug:
> >
> > command vim -nNX -u NONE
> > then insert: bla:///path/to/file
> > then, with cursor being on p, use gf
> > It tries to open bla:///path/to/file although : is not in 'isf and bla:/// =
> > isn't a prot
--
GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka)
--
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
Hi,
Sorry, forgot to mention that you need :set report=0
Cheers
--
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
Hi, I don't have the latest version of Vim installed, so this might not be a
real bug.
Please check!
1. 60obutterchocolate (120 lines)
2. qwq
3. :g/butter/y W
4. at the -- More -- prompt hit q
5. in a new window: "wP
Result: you have copied only half the words (or a screenfull in fact)
:silen
Hi all,
I have maybe found a little issue:
1. vim -N -u NONE -U NONE
2. :imap D
3. :set spell
4. ino
Instead of trying to complete using the 'dict option, it is trying to use the
mapping...
Also, in insert.txt line 64: 'The key that
ends CTRL-X mode (any key that is not a valid CTRL-X mode co
Hi all,
I have maybe found a little issue:
1. vim -N -u NONE -U NONE
2. :imap D
3. :set spell
4. ino
Instead of trying to complete using the 'dict option, it is trying to use the
mapping...
Also, in insert.txt line 64: 'The key that
ends CTRL-X mode (any key that is not a valid CTRL-X mode co
Hi all,
Here is what to do (tried on windows only):
1. gvim.exe -u NONE -U NONE -N
2. i(oge)
3. :se is
4. /(oge)^f
5. Now just go up/down, left/right and there will be weird highlightings
everywhere
Version: 7.3, 1-138
PS: Sorry if this has already been reported
Dimitar Dimitrov
Hi,
On windows XP:
1. I did: gvim.exe -u NONE -U NONE -N
then :ls which displays
:ls
1 %a "[No Name]"line 1
Press ENTER or type command to continue
2. Then I did: :set lazyredraw, and this time :ls wouldn't display anything
Tested with Vim 7.3, 1-138
D
2011, 21h 04min 42s
Objet : Re: tr() problem ?
On Wed, Feb 9, 2011 at 2:10 PM, James Vega wrote:
> On Wed, Feb 9, 2011 at 12:04 PM, Dimitar DIMITROV wrote:
>> But this doesn't:
>>
>> command! Translate call setline(line('.'), tr(getline('.')
Thanks James,
I'll use "\u0440" as you suggested
D
De : James Vega
À : vim_dev@googlegroups.com
Envoyé le : Mer 9 février 2011, 19h 10min 55s
Objet : Re: tr() problem ?
On Wed, Feb 9, 2011 at 12:04 PM, Dimitar DIMITROV wrote:
> But this do
Hi,
I wonder why the below works:
command! Translate call setline(line('.'), tr(getline('.'),
\'ABVGDEWZIJK',
\'АБВГДЕЖЗИЙК'))
then :Translate on any line
But this doesn't:
command! Translate call setline(line('.'), tr(getline('.'),
\'ABVGDEWZIJKLMNOPRSTUYFHXC$^&}{!|Qabvgdewzijklmnopr
Hi,
I use the excellent Bgrep plugin:
http://www.vim.org/scripts/script.php?script_id=2545
When I open a bunch of files (:n ~/*.bla) and look for a pattern in all buffers
with :Bgrep/pattern/
All goes really well if 'hidden' is NOT enabled.
If it is, syntax highlighting disappears from most of
> Dimitar DIMITROV wrote:
> > Hi,
> >
> > 1. :help
> > 2. 10GVj
> > 3. :ene
> > 4. Use to paste the text but don't do it above line 1
> > 5. u
> > 6. Use to paste the text and do it above line 1
> > 7. ddu^R
> >
> > Erro
2010 10:56, Dimitar DIMITROV wrote:
> I hadn't. Now I did and there is a different error. At the end we still
> should
> have one line but all disappears. Here is how you can reproduce it:
>
> gvim.exe -u NONE -U NONE
> :help
> yy
> ^w^w
> p
> u
> P
> j
>
> Dimitar Dimitrov wrote:
>
> > 1. :help
> > 2. 10GVj
> > 3. :ene
> > 4. Use to paste the text but don't do it above line 1
> > 5. u
> > 6. Use to paste the text and do it above line 1
> > 7. ddu^R
> >
> > Error message:
> &
> Hi,
>
> When using
>
> :vglobal/\S/,/\S/-j|noh (this reduces several empty lines following one
> another
>to just one line)
>
> on a php file:
>
>
> class Test {
>
> public function init()
> {
> echo '1';
>
> echo '2';
> echo '3';
> echo '4';
> e
Hi,
1. :help
2. 10GVj
3. :ene
4. Use to paste the text but don't do it above line 1
5. u
6. Use to paste the text and do it above line 1
7. ddu^R
Error message:
E315: ml_get: invalid lnum: 3
E315: ml_get: invalid lnum: 3
:version
VIM - Vi IMproved 7.3d BETA (2010 Aug 4, compiled Aug 4 2010
Hi,
When using
:vglobal/\S/,/\S/-j|noh (this reduces several empty lines following one another
to just one line)
on a php file:
http://www.vim.org/maillist.php
Dimitar Dimitrov wrote:
> On 29/07/10 10:49, Dimitar DIMITROV wrote:
> > Hi,
> >
> > I've noticed that there is no mention in the help files that one can use
> > things like:
> >
> > 1. :h i^x^k or even
> > :h^x^k instead of
> > :h i_CTRL
Hi,
On linux systems I can open Vim and type:
:e~/d which expands (for me) to :e~/dev/ and I can go on...
but on Windows:
:e~/d expands to :eD:\dev\ and therefore I can't go on with my completion
unless I start over again using :e ~/d (note the space)
The whole point is:
I need a space before
Hi,
I've noticed that there is no mention in the help files that one can use things
like:
1. :h i^x^k or even
:h^x^k instead of
:h i_CTRL-X_CTRL-K
2. [count] gqq will format count lines
Cheers
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
- Message transféré
De : Dimitar DIMITROV
À : Bram Moolenaar
Envoyé le : Mar 27 juillet 2010, 13h 32min 56s
Objet : Re : Minor problems...
Dimitar Dimitrov wrote:
> I wrote:
>
> > Dimitar Dimitrov wrote:
> >
> > > I always have 'cursorline
Dimitar Dimitrov wrote:
> I wrote:
>
> > Dimitar Dimitrov wrote:
> >
> > > I always have 'cursorline' set.
> > >
> > > Try this: :h'exrc
> > >
> > > Setting the cursor on this line...:
> > >
> > >
gVim on Windows XP
1. 77ia,
2. /\(\(\s*\w\+\s*\)\+,\)\{1,20}
3. :h\{
Then gVim stops responding
VIM - Vi IMproved 7.3a BETA (2010 Jul 18, compiled Jul 18 2010 21:51:55)
MS-Windows 32-bit GUI version with OLE support
Compiled by b...@kibaale
Big version with GUI. Features included (+) or not
:find crashed my gVim on Windows XP
VIM - Vi IMproved 7.3a BETA (2010 Jul 18, compiled Jul 18 2010 21:51:55)
MS-Windows 32-bit GUI version with OLE support
Compiled by b...@kibaale
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byt
Hi,
I always have 'cursorline' set.
Try this: :h'exrc
Setting the cursor on this line...:
setting the 'secure' option (see initialization). Using a local
...makes it move right. Same thing if you turn off cursorline but position your
cursor on the left parens...
I think this is rela
1. valgrind --leak-check=full --show-reachable=yes ./vim -u NONE -U NONE
2. ZQ
==14191== LEAK SUMMARY:
==14191==definitely lost: 36 bytes in 1 blocks.
==14191==indirectly lost: 120 bytes in 10 blocks.
==14191== possibly lost: 0 bytes in 0 blocks.
==14191==still reachable: 40,689
1.
2. 3yy`]
3. 5yy`]
==4008== LEAK SUMMARY:
==4008==definitely lost: 37,350 bytes in 116 blocks.
==4008==indirectly lost: 28,332 bytes in 1,403 blocks.
==4008== possibly lost: 319,554 bytes in 469 blocks.
==4008==still reachable: 2,425,077 bytes in 30,351 blocks.
==4008==
valgrind --leak-check=full --show-reachable=yes gvim
1. cc, then a,a,a,a,a,a,a,a,a,a,a,
2. /\(\(\s*\w\+\s*\)\+,\)\{1,20}
3. :h\{
4. Close gvim
==3987== LEAK SUMMARY:
==3987==definitely lost: 12,986 bytes in 47 blocks.
==3987==indirectly lost: 28,332 bytes in 1,403 blocks.
==3987== po
> That said, I think persistent undo is more or less useless and, well,
> just a big pile of potential problems. Persistent undo is in the
> version control system, not in the editor.
I agree with that. This would probably be best left to versionning systems.
Shouldn't Vim be used for purely te
I would like to report some unexpected behaviour:
1. :set path+=~/dev/**
2. :find test.c works
1. :set path+=~/dev
2. :find **/test.c doesn't work
And yet, :h wildcard suggests that it should...
Note: File in ~/dev/project/example/test.c
--~-
I still think there is a little problem here.
Fist, setting cpo+=% is not a solution because it breaks /* */ and # jumping...
What I am saying is:
("( )use %" ) - here we will jump to the
very first (
so using ]) should work as well... (for jumping to the l
lugin = 1
let g:loaded_getscriptPlugin = 1
let loaded_gzip = 1
let loaded_spellfile_plugin = 1
Regards
Dimitar Dimitrov
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit htt
#x27;t happen.
Just after: touch .vimrc, the bug appears!
Dimitar Dimitrov
My version:
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Feb 25 2009 17:43:03)
Included patches: 1-108
Compiled by 'http://www.opensuse.org/'
81 matches
Mail list logo
