-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Some folks who like to use vim under GNU screen, myself included, would
like the ability for vim to automatically support xterm mouse escape
sequences. Would it be a workable solution for vim to include screen
as one of the initial strings for
Am Montag, den 07.05.2007, 16:07 -0700 schrieb Ian Tegebo:
The Wiki would ideally understand how to link to vim-scripts and vim-tips like
vimonline currently does. As a bonus, mailing-list posts would also linkable
Easy:http://en.wikipedia.org/wiki/Interwiki#Shorthand_for_non-wiki_sites
For
Suresh Govindachar wrote:
Bram Moolenaar wrote:
Markus Trenkwalder wrote:
checked out vim-7.1a.001 today from svn (#263) and tried to
compile it with mingw-gcc and got the following error:
8
$ make -f Make_ming.mak
gcc -c -Iproto -DWIN32 -DWINVER=0x0400
Tried the ftp versions (including patch 7.1a.001) now. Same again. And
as Edward Fox told earlier the SVN repository should be almost the same
as CVS.
I also tried to find a better solution but as I could not find macro
that fits better I do also not know any alternative.
Regards
Markus
On 5/8/07, Markus Trenkwalder [EMAIL PROTECTED] wrote:
Tried the ftp versions (including patch 7.1a.001) now. Same again. And
as Edward Fox told earlier the SVN repository should be almost the same
as CVS.
*Almost* the same with ftp versions.
*Definitely* the same with CVS.
I also tried
On 5/8/07, Markus Trenkwalder [EMAIL PROTECTED] wrote:
Edward L. Fox wrote:
On 5/8/07, Markus Trenkwalder [EMAIL PROTECTED] wrote:
Tried the ftp versions (including patch 7.1a.001) now. Same again. And
as Edward Fox told earlier the SVN repository should be almost the same
as CVS.
Bram Moolenaar wrote:
Chris Sutcliffe wrote:
Hey All,
Patch 7.1a.001
I managed to compile 7.1a from cvs yesterday. I went and did a cvs up
to grab this patch and I am now getting this error:
gui_w32.c:236: error: redefinition of `struct tagNMTTDISPINFOA'
gui_w32.c:246: error: redefinition
I was able to get it to compile under cygwin using Make_cyg.mak GUI=yes by
removing the two typedefs at line 236 and 247 in gui_w32.c.
It would seem that the pre-processor doesn't recognise labels from a previous
typedef, so the #ifndef LPNMTTDISPINFO test doesn't work as expected.
Or it's
Yakov Lerner wrote:
On 5/5/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Announcing: Vim (Vi IMproved) version 7.1a BETA
I compared runtime files form ftp [1] and from svn [2].
Both vims are labeled vim71a. But many runtimes are different.
In svn, many files are labeled 2007.
Hello!
On RHEL4 works well!
On Fedora Core 6 couldn't automatically determinte $VIMRUNTIME, lacked
the last part 'vim71a' in the path when I tried to open a file (say,
Foo.hs). Without initial file opening from command line works well.
On mingw (Windows XP) couldn't compile the gui version
Redirecting to the vim-dev list...
What I find interesting is that the #ifndef LPNMTTDISPINFO should have
caught that LPNMTTDISPINFO was defined in commctrl.h which is included
in gui_w48.c included prior to the #ifndef LPNMTTDISPINFO test.
As far as I know this is not true because in
It doesn't compile under Mingw32 unless gui_w32.c is patched:
--- gui_w32.c.orig Sat May 05 04:24:58 2007
+++ gui_w32.c Tue May 08 09:01:11 2007
@@ -232,6 +232,7 @@
LPARAM lParam;
} NMTTDISPINFO_NEW;
+#ifndef __MINGW32__
#ifndef LPNMTTDISPINFO
typedef struct tagNMTTDISPINFOA {
Edward L. Fox wrote:
On 5/8/07, scott [EMAIL PROTECTED] wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to
7.1a -- from previous posts i had thought there was something extra
that had
to be done to get the beta, like create a new 71a directory or something
now
Anatoli Sakhnik wrote:
Hello!
On RHEL4 works well!
On Fedora Core 6 couldn't automatically determinte $VIMRUNTIME, lacked
the last part 'vim71a' in the path when I tried to open a file (say,
Foo.hs). Without initial file opening from command line works well.
On mingw (Windows XP) couldn't
On Tuesday 08 May 2007 12:04, you wrote:
Edward L. Fox wrote:
On 5/8/07, scott [EMAIL PROTECTED] wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to
7.1a -- from previous posts i had thought there was something extra
that had
to be done to get the beta,
Markus Trenkwalder wrote:
Suresh Govindachar wrote:
Bram Moolenaar wrote:
Markus Trenkwalder wrote:
checked out vim-7.1a.001 today from svn (#263) and tried to
compile it with mingw-gcc and got the following error:
8
$ make -f Make_ming.mak
Micah Cowan wrote:
Some folks who like to use vim under GNU screen, myself included, would
like the ability for vim to automatically support xterm mouse escape
sequences. Would it be a workable solution for vim to include screen
as one of the initial strings for terms that trigger truth for
Mr Toothpik wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to 7.1a -- from previous posts i had thought there was something
extra that had to be done to get the beta, like create a new 71a
directory or something
now i've got the beta i feel committed, and
Ian Tegebo wrote:
On 5/6/07, Sebastian Menge [EMAIL PROTECTED] wrote:
Hi all
Independent of the implementation used, I suggest to develop good
guidelines. The Wiki should be really valuable and not redundant to
vim-tips or mailing-lists.
I would like to make another implementation
Hi there!
I'm sorry having troubled you. I often type `vi' instead of `vim' for
brevity. Usually, I substitute the former of the system with a link to
vim, but this time I missed that fact (by the way, not for the first
time). So, there's no problem with linux compilation and running at
all.
Bram Moolenaar wrote:
Mr Toothpik wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to 7.1a -- from previous posts i had thought there was something
extra that had to be done to get the beta, like create a new 71a
directory or something
now i've got the beta i
On Tue, May 08, 2007 at 04:50:36PM -0500, Robert Lee wrote:
The SVN Repos has conflict markers left in the file filetype.vim,
Sorry for the silly question, but the answer is not clear to me from
your text: is your working copy that has conflict markers or the last
committed version in the
Doh! I accidentally sent this directly to Bram, instead of to list :/
Bram Moolenaar wrote:
I'm guessing that a problem for this, might be the fact that if vim
detects xterm-ish terminals, it automatically tries the t_RV sequence
out, which isn't dependably valid for screen.
If this is the
On Tue, May 08, 2007 at 03:04:10PM -0700, Micah Cowan wrote:
It's about time termcap/terminfo gets updated to support the
features we need, instead of hacking solutions in all programs. I'm
afraid I don't have time for this (the original development of
termcap was closely related to the
Stefano Zacchiroli wrote:
On Tue, May 08, 2007 at 04:50:36PM -0500, Robert Lee wrote:
The SVN Repos has conflict markers left in the file filetype.vim,
Sorry for the silly question, but the answer is not clear to me from
your text: is your working copy that has conflict markers or the
Micah Cowan wrote:
[...]
But you already have hacked support into your programs for mouse
support. Now that you've done that, couldn't you just open it up a bit?
Is there anything wrong with always recognizing the appropriate xterm
sequences (provided that they don't first match a valid terminfo
A.J.Mechelynck wrote:
Micah Cowan wrote:
[...]
But you already have hacked support into your programs for mouse
support. Now that you've done that, couldn't you just open it up a bit?
Is there anything wrong with always recognizing the appropriate xterm
sequences (provided that they don't
Hi Vimmers,
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
If you had checked out a copy of the sources before, please run this
command in
Hi Bram,
I noticed that you also maintained another CVS repository besides the
sf.net's CVS repository. And many changes to that internal CVS won't
be applied to the sf.net's CVS repository unless a large release is to
be made.
In my opinion, as the SVN repository is now standardized, could you
On 5/9/07, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi Vimmers,
As many many people requested, I finally decide to obey the svn book's
advice and will build up trunk/ tags/ and branches/. But so far as you
know, sf.net's svn service is not in a good status so I'm not able to
commit all changes
One word under :help 'ttymouse' was obviously forgotten when that option got
more possible settings. See suggested patch, attached.
Best regards,
Tony.
--
You should never wear your best trousers when you go out to fight for
freedom and liberty.
-- Henrik Ibsen
***
Edward L. Fox announced:
Hi Vimmers,
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1 vim7
If you had checked out a
A.J.Mechelynck wrote:
Micah Cowan wrote:
[...]
But you already have hacked support into your programs for mouse
support. Now that you've done that, couldn't you just open it up a bit?
Is there anything wrong with always recognizing the appropriate xterm
sequences (provided that they don't
On Tuesday 08 May 2007 15:32, you wrote:
Mr Toothpik wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to 7.1a -- from previous posts i had thought there was something
extra that had to be done to get the beta, like create a new 71a
directory or something
Hello vimmers,
I am running 7.1a.001 on OSX and have just noticed the following from
console vim (running in Terminal.app and also occurs in iTerm.app).
If I change the colour scheme I receive a lot of error output. For
example:
:colorscheme desert
Results in:
Error detected while
On 5/9/07, Suresh Govindachar [EMAIL PROTECTED] wrote:
Edward L. Fox announced:
Hi Vimmers,
The directories structure of the Subversion repository has been
changed. Please use this command to checkout the latest sources:
svn co
On 5/8/07, scott [EMAIL PROTECTED] wrote:
i was surpised by the fact that simply running 'svn update' bumped me up to
7.1a -- from previous posts i had thought there was something extra that had
to be done to get the beta, like create a new 71a directory or something
now i've got the beta i
On 2007-05-08, Ian Tegebo [EMAIL PROTECTED] wrote:
On 5/8/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Ian Tegebo wrote:
I would like to make another implementation independent suggestion;
one could make a VimWiki more valuable by importing the _extremely_
valuable vim helpfiles
On 5/8/07, Gary Johnson [EMAIL PROTECTED] wrote:
On 2007-05-08, Ian Tegebo [EMAIL PROTECTED] wrote:
On 5/8/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Ian Tegebo wrote:
I would like to make another implementation independent suggestion;
one could make a VimWiki more valuable by
A.J.Mechelynck wrote:
Michael Wookey wrote:
Hello vimmers,
I am running 7.1a.001 on OSX and have just noticed the following
from
console vim (running in Terminal.app and also occurs in iTerm.app).
If I change the colour scheme I receive a lot of error output. For
example:
40 matches
Mail list logo
