Bram Moolenaar wrote:
> Patch 7.1.002
> Problem:Oracle Pro*C/C++ files are not detected.
> Solution: Add the missing star. (Micah J. Cowan)
Just to be clear: while I reformatted the solution in patch-form, it was
Arturo Olguín Cruz who first found the bug and determined its fix:
https://bugs
Fixes an apparent typo in filetype.vim.
Per https://bugs.launchpad.net/ubuntu/+source/vim/+bug/86916.
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
Index: runtime/filetype.vim
===
A.J.Mechelynck wrote:
> Micah Cowan wrote:
>> Bram Moolenaar wrote:
> [...]
>>> The solution is simple: Don't create a link in place of the .viminfo
>>> file. And certainly not to /dev/null.
>>>
>>> Background info: When Vim finds an existing
Bram Moolenaar wrote:
> Micah Cowan wrote:
>
>> Following description lifted from bug filed at
>> https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
>>
>> <<
>> [EMAIL PROTECTED]:~$ rm .viminfo
>> [EMAIL PROTECTED]:~$ ln -s /dev/null
Taylor Venable wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>> Is there a good reason not to simply follow symlinks when they are
>> encountered, as this user obviously expected?
>
> If it did follow the symlink to /dev/null, and tried to read from that
>
A.J.Mechelynck wrote:
> Micah Cowan wrote:
>> Following description lifted from bug filed at
>> https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
>>
>> <<
>> [EMAIL PROTECTED]:~$ rm .viminfo
>> [EMAIL PROTECTED]:~$ ln -s /dev/null .v
Following description lifted from bug filed at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
<<
[EMAIL PROTECTED]:~$ rm .viminfo
[EMAIL PROTECTED]:~$ ln -s /dev/null .viminfo
[EMAIL PROTECTED]:~$ ls -l .viminfo
lrwxrwxrwx 1 sa sa 9 2007-01-12 17:16 .viminfo -> /dev/null
[EMAIL PROTECTED
Bram Moolenaar wrote:
> Micah Cowan wrote:
>> Vincent BEFFARA wrote:
>>> However, it would be nice of vim to always test that it owns the $HOME
>>> directory before creating files there. Would it break anything ?
>> I think this would be a good idea as well. One
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
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;
Gary Johnson wrote:
> On 2007-05-09, Micah Cowan <[EMAIL PROTECTED]> 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
Edward L. Fox wrote:
> On 5/10/07, Gautam Iyer <[EMAIL PROTECTED]> wrote:
>> I got the same error. My response was
>>
>> rm -rf vim7
>> svn co https://svn.sourceforge.net/svnroot/vim/trunk vim7
>
> "svn switch" can only switch from a directory into another directory
> inside the same repos
Bram Moolenaar wrote:
> 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 thread
>> now includes a proposed patch, and so that we know what message t
Yakov Lerner wrote:
> On 5/9/07, Edward L. Fox <[EMAIL PROTECTED]> wrote:
>> If you had checked out a copy of the sources before, please run this
>> command in your source root directory to switch into the current
>> branch:
>>
>> svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7
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 thread
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 discussing.
I have made a slight adju
Micah Cowan wrote:
> A.J.Mechelynck wrote:
>
>> This is done as a result
>> of sending the t_RV code and receiving an answer for it, which happens
>> after the first file has been loaded and all -c commands have been
>> processed: probably just before or just after t
A.J.Mechelynck wrote:
> This is done as a result
> of sending the t_RV code and receiving an answer for it, which happens
> after the first file has been loaded and all -c commands have been
> processed: probably just before or just after the VimEnter event. IOW,
> you cannot test them in your vim
A.J.Mechelynck wrote:
> Micah Cowan wrote:
>> Attached is a proposed patch that effects the change I'm requesting. I
>> would love to get some feedback/further discussion based on it. They say
>> "code talks", and so here is my concrete expression. :)
>
I wrote:
> Therefore, there would seem to be no harm whatsoever in detecting screen
> as an xterm-mouse-code-capable terminal, and sending the mouse-mode
> sequence ("xterm" protocol, since AFAIK screen provides no way to detect
> the underlying xterm version). If the underlying terminal claims to
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
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
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 thi
-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 fo
23 matches
Mail list logo
