_sc_, 11.02.2009:
On Tuesday 10 February 2009 5:54 pm, Markus Heidelberg wrote:
_sc_, 07.02.2009:
On Friday 06 February 2009 4:09 pm, Matt Wozniski wrote:
and my .git/config contains:
Somehow, you're missing this:
[branch custom]
remote = origin
Patch 7.2.103
Problem:When 'bomb' is changed the window title is updated to show/hide a
+, but the tab page label isn't. (Patrick Texier)
Solution: Set redraw_tabline in most places where need_maketitle is set.
(partly by Lech Lorens)
Files: src/option.c
***
Markus Heidelberg, 11.02.2009:
Christian MICHON, 06.02.2009:
you're facing the same problem I faced in July. I noticed (example
7.2.102) the commit message is truncated. so we're even here: I've the
same issue and this requires somehow manual intervention. :(
James does manual
On Tue, Feb 10, 2009 at 9:48 PM, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
But let's not forget that they have significant disadvantages, too...
Vimballs made with new versions of the plugin don't work on older
vims.
There's been one problem with that -- 7.0 vimball doesn't
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
installing zip-based plugins basically is a matter of
exec '!unzip '. shellescape(expand('%')) .' -d ~/vimfiles'
On Wed, Feb 11, 2009 at 11:06 AM, Tom Link micat...@gmail.com wrote:
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
IMHO reliance on compiled-in +python support
On Wednesday 11 February 2009 4:00 am, Markus Heidelberg wrote:
[...]
Maybe you have an old git version installed, where the automatic setup
of .git/config for the remote tracking branches (during the command git
checkout -b custom origin/vim-with-runtime) was not yet the
Patch 7.2.108 (after 7.2.105)
Problem:Can't build without the diff feature.
Solution: Add #ifdef.
Files: src/option.c
*** ../vim-7.2.107/src/option.c Wed Feb 11 16:45:56 2009
--- src/option.cWed Feb 11 22:21:16 2009
***
*** 4127,4132
--- 4127,4133
Testing autocommands, I see that Vim-7.2.107 (and older)
is using memory already freed when doing silly autocommands
such as:
$ touch foobar
$ valgrind ./vim -u NONE -c 'au! BufReadPre * cd /tmp' \
-c 'e foobar' 2 vg.log
In vg.log, I then see the following error:
On 11/02/09 22:54, Tony Mechelynck wrote:
On 11/02/09 16:46, Bram Moolenaar wrote:
Patch 7.2.105
Problem:Modeline setting for 'foldmethod' overrules diff options. (Ingo
Karkat)
Solution: Don't set 'foldmethod' and 'wrap' from a modeline when 'diff' is
on.
Files:
The attached patch fixes the misbehaviour of vim when 'switchbuf' is set
to usetab. Also the location list window is not incorrectly described
as quickfix window any more.
To reproduce the problems perform the following steps:
Create a file file.txt containing the string foo.
Open Vim: vim -p
On 11/02/09 03:48, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
But let's not forget that they have significant disadvantages, too...
Vimballs made with new versions of the plugin don't work on older
vims.
There's been one problem with that -- 7.0 vimball doesn't handle the later
On 11/02/09 16:23, Matt Wozniski wrote:
[...]
Well, of course I didn't mean that we should add the features to the
zip format. Rather, I meant we should do something more like XPI -
create a zip file, rename it to .vba, and let vim handle it specially.
The change would be transparent to
On 11/02/09 06:42, Tom Link wrote:
You can specify the base path with the final arg to MkVimball.
If you wanted to create vimballs from cygwin bash by calling Windows
gvim (you could of course use cygwin's vim but ...), you'd have to
convert the path which works most of the time but can be
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough standard). And note that if
the
On Wed, Feb 11, 2009 at 7:29 PM, Tony Mechelynck wrote:
On 11/02/09 16:23, Matt Wozniski wrote:
[...]
Well, of course I didn't mean that we should add the features to the
zip format. Rather, I meant we should do something more like XPI -
create a zip file, rename it to .vba, and let vim
Gary Johnson wrote:
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough standard).
On 12/02/09 02:07, Gary Johnson wrote:
On 2009-02-12, Tony Mechelynckantoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough
On 11/02/09 03:35, Markus Heidelberg wrote:
James Vega, 06.02.2009:
On Thu, Feb 05, 2009 at 10:23:33PM +0100, Markus Heidelberg wrote:
What do you think about the commit message format, is it ok? I searched
for a git-like message, without losing information. The duplicated first
line of the
19 matches
Mail list logo
