Daniel Drake wrote:
gvim with FEAT_GUI_GNOME fails to compile against GNOME 2.18. See
https://bugs.gentoo.org/show_bug.cgi?id=176566 for more info.
This patch solves the problem.
Thanks. Looks safe to include now.
--
There's no place like $(HOME)!
/// Bram Moolenaar -- [EMAIL
Michael Wookey wrote:
Has anyone else noticed this?
You apparently are missing the runtime/rgb.txt file. It's part of the
extra archive. Perhaps you didn't unpack it correctly? You must have
unpacked it, since it contains src/gui_mac.c. And you must not change
the directory
Micah Cowan wrote:
Sorry for the repost; but I realized I should've drawn more attention to
the message with the patch in it, both so other lurkers know the threa d
now includes a proposed patch, and so that we know what message to go
back to if we want to refer to the code we're
Bram Moolenaar wrote:
[...]
I'll add a specific line to copy rgb.txt.
Just for the record, after reformatting the entries to a common format and
sorting, a diff between my ~/.build/vim/vim71a/runtime/rgb.txt and my
/usr/share/X11/rgb.txt shows no other difference than the header comment --
I don't remember if I have already submitted these before... These two patches
add some NetBSD specific keywords. Please include these in the official source
code.
Martti
$NetBSD: patch-ab,v 1.5 2006/05/09 06:36:48 martti Exp $
--- runtime/syntax/fstab.vim.orig 2006-04-16
Martti Kuparinen wrote:
I don't remember if I have already submitted these before... These two
patches add some NetBSD specific keywords. Please include these in the
official source code.
Please send patches for Vim scripts directly to their maintainers. For
syntax/fstab.vim that is Radu
Bram Moolenaar wrote:
Micah Cowan wrote:
Towards a better solution: how straightforward do you think it'll be to
talk the ncurses guys into adding support for some of screen's
extensions? AFAIK, the only one I care about is the xterm mouse support;
another interesting one is a boolean
Copying the dev list. The missing context is that running vim via sudo
before having run it as regular user, causes permission problems with
the created .viminfo file (and others?).
Vincent BEFFARA wrote:
Wonderful, the problem really is about permission of .viminfo!
I noticed that you
Micah Cowan wrote:
Copying the dev list. The missing context is that running vim via sudo
before having run it as regular user, causes permission problems with
the created .viminfo file (and others?).
Vincent BEFFARA wrote:
Wonderful, the problem really is about permission of .viminfo!
Am Donnerstag 10 Mai 2007 schrieb Gautam Iyer:
I got the same error. My response was
rm -rf vim7
svn co https://svn.sourceforge.net/svnroot/vim/trunk vim7
You are using the old URL which may or may not work! The new url has the
project name at both ends:
Announcing: Vim (Vi IMproved) version 7.1b BETA
This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all
patches, updated runtime files and a few fixes.
If you were using 7.1a please upgrade to 7.1b and verify it works well.
Please report every problem you find! It will only be a
Patch 7.1b.001 (extra)
Problem:Random text in a source file. No idea how it got there.
Solution: Delete the text.
Files: src/gui_w32.c
*** ../vim-7.1b.000/src/gui_w32.c Thu May 10 20:18:47 2007
--- src/gui_w32.c Thu May 10 22:03:22 2007
***
*** 1,4
! s,
Edward L. Fox wrote:
On 5/10/07, Gautam Iyer [EMAIL PROTECTED] wrote:
[...]
I've a question, though: isn't bleeding-edge development done in
https://svn.sourceforge.net/svnroot/vim/trunk ? That /would/ be the
appropriate line for the latest sources, right?
I don't know. I'm still asking
Patch 7.1b.001 (extra)
Builds cleanly with MinGW, thanx!
Chris
--
Chris Sutcliffe
http://ir0nh34d.googlepages.com
http://ir0nh34d.blogspot.com
http://emergedesktop.org
14 matches
Mail list logo
