Loading ...
Sorry, an error occurred while loading the content.

Topics List

Preparations for moving to github

(60)
I'd just like to point out that all you githeads arguing over the various different options on pull and fetch and whether they break or keep your repository
Ben Fritz
60
posts
8:04 AM

[Patch] Build Vim on Mac OS X with Privately Installed Python (src/c

(9)
... I'll try it soon, but I assure you, to check that the usage of the return of the boolean test was broken I've tried it in a minimal case just to make sure.
Francisco Lopes
9
posts
7:16 AM

Bug with renderoptions (was: Re: [ANN] Vim for Windows build, conta

(7)
... Yes, that seems to be the case. Using a debugger, I can see, that after the CreateFontIndirect() call, I get a handle like this: 0xc011751 {unused=???}
Christian Brabandt
7
posts
3:32 PM

Issue 91 in vim: File->Open does not update window content correctly

(11)
Comment #9 on issue 91 by brammool...@gmail.com: File->Open does not update window content correctly - Appeared first in v7-3-638
vim@googlecode.com
11
posts
Mar 24

Another bug with rnu and showbreak

(7)
... I thought I fixed that one, but the test case I created still does not work and I am running out of ideas currently. So I have to leave that aside for now.
Christian Brabandt
7
posts
Mar 23

Wrong dollar sign red color highlighting in shell scripts

(13)
... Actually no, this patch breaks $(cmd ...) syntax. Somebody needs to look into why b:is_kornshell should come into play for bourne shell syntax. Or just
Yuri
13
posts
Mar 22

Issue 344 in vim: Inconsistency with virtualedit=onemore $ and g$ in

(6)
Comment #5 on issue 344 by TruSktr: Inconsistency with virtualedit=onemore $ and g$ in NORMAL vs VISUAL. https://code.google.com/p/vim/issues/detail?id=344 I'm
vim@googlecode.com
6
posts
Mar 20

Weird behaviour of :tabmove and inconsistency between the actual beh

(19)
... Thanks! I would appreciate if a couple of people review this. -- Q: How does a UNIX Guru pick up a girl? A: look; grep; which; eval; nice; uname; talk;
Bram Moolenaar
19
posts
Mar 20

Issue 341 in vim: Google Code will close

(6)
Updates: Status: Duplicate Mergedinto: 340 Comment #3 on issue 341 by chrisbr...@googlemail.com: Google Code will close
vim@googlecode.com
6
posts
Mar 19

Google Code shuts down

(66)
... ++. Seems to me that moving vim to another source repo host should be done in phases. First, move the vim repo to a host that supports Mercurial which
Will Fiveash
66
posts
Mar 17

BUG: Unclosed regexp collection breaks :substitute

(8)
... Hash: SHA1 ... Yeah, realistically, the bug would only be included as a low-prio item on the todo list, and probably not addressed within this decade :-(
Ingo Karkat
8
posts
Mar 15

Possible bug in CursorHoldI behavior

(8)
... Thanks! I'm glad it's this simple. -- GUARD #1: Where'd you get the coconut? ARTHUR: We found them. GUARD #1: Found them? In Mercea? The coconut's
Bram Moolenaar
8
posts
Mar 12

Font size?

(12)
Hi Donald! ... Thanks but wading through another unknown code repository doesn't make it easier... ... Not everybody knows every part of this editor. ... Well
Christian Brabandt
12
posts
Mar 11

Re: colorcolumn and foldtext

(9)
... Do you mean, that the number setting isn't updated? How did you do this? Does a manual redraw using :redraw or :redraw! help? I can't seem to replicate
Christian Brabandt
9
posts
Mar 10

Maintainer of runtime/syntax/make.vim

(7)
... I sent my first email on July 23rd 2014, and a second one on October 23rd 2014. Matthias -- -- You received this message from the "vim_dev" maillist. Do
matthias.hinkfoth2@uni-rostock.de
7
posts
Feb 27
View First Topic Go to View Last Topic
Loading 1 - 15 of total 15 topics