Yukihiro Nakadaira wrote:
> Attached patch fixes section number.
Hi
I also see incorrect section numbers in runtime/doc/ft_ada.txt
(fixed in attached patch).
-- Dominique
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyin
Yukihiro Nakadaira wrote:
> Attached patch fixes section number.
Hi Yukihiro
In this chunk...
diff --git a/runtime/doc/debug.txt b/runtime/doc/debug.txt
--- a/runtime/doc/debug.txt
+++ b/runtime/doc/debug.txt
@@ -89,7 +89,7 @@
On 18/08/10 23:18, Bram Moolenaar wrote:
Tony Mechelynck wrote:
Problem: "default" branch has two heads, i.e. two changesets with have
no direct children _inside_ the same "default" branch (one of them is
the current 7.3 head, the other is the 7.2.446 changeset before the
creation of the "vim7
Attached patch fixes section number.
--
Yukihiro Nakadaira - yukihiro.nakada...@gmail.com
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
diff --git a/runtim
> F1rst! :-)
>
> Pros: All Windows specific code.
> Cons: Can't do anything clever with an invalid format string.
>
> Should be ok with mingw32.
Wow, so quick :)
I think you've done it right by installing the handler once and for
all. For users of ancient compilers I suggest to add something like
Hi
In vim/src/gui_mac.c, I see this switch:
5724 switch (type)
5725 {
5726 case VIM_GENERIC: useIcon = kNoteIcon;
5727 case VIM_ERROR:useIcon = kStopIcon;
5728 case VIM_WARNING: useIcon = kCautionIcon;
5729 case VIM_INFO: useIcon = kNoteIcon;
5730
On 19-Aug-2010 Xavier de Gaye wrote:
> I will propose a patch to support netbeans on vim-athena, unless
> someone else wants to do it.
Hi,
Thank you so much! I for one will be extremely grateful for this
feature!
--
Cheers,
Lech
--
You received this message from the "vim_dev" maillist.
Do no
Xavier de Gaye wrote:
On Thu, Aug 19, 2010 at 3:45 PM, Ben Fritz wrote:
I know about all of these except vimGdb. Wasn't that some sort of
debugger integration? Is that really included in Vim 7.3? Or is it
just no longer supported?
The patch is not included in Vim 7.3.
The patch is s
On Thu, Aug 19, 2010 at 3:43 PM, David Harrison wrote:
>>
>> Is it possible to build simply gvim-athena without having to
>> install too much athena stuff ?
>
> Athena used to come with a standard X distribution. I don't know if
> it still does, but I'm willing to bet that it's still there. Just
On Thu, Aug 19, 2010 at 3:45 PM, Ben Fritz wrote:
>
> I know about all of these except vimGdb. Wasn't that some sort of
> debugger integration? Is that really included in Vim 7.3? Or is it
> just no longer supported?
>
The patch is not included in Vim 7.3.
The patch is supported (see http://clewn
On 18/08/2010 19:16, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?)
Any unsupported format specifier will result in a crash. On
Windows, or at least builds that use recent VC CRT libraries, VIM
needs to valid
On Aug 18, 12:11 am, "John Beckett" wrote:
>
> I added a brief intro to say that some patches are no longer
> listed because they are in Vim 7.3.
>
> These patches were removed (source code is now in Vim 7.3):
> Persistent undo
> Lua Interface
> vimGdb
> Additional floating-point
> Hi Lech,
>
> I dont know why the Athena GUI is not supported by netbeans. I guess
> the main problem is having to install Athena in order to test the
> implementation. Since both GUI_MOTIF and GUI_ATHENA use Xlib, most of
> the netbeans code should be the same for both configurations.
>
> Is it p
On 19/08/2010 11:57, Bram Moolenaar wrote:
Mike Williams wrote:
On 18/08/2010 18:54, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
unsupported format specifier will result in a crash. On Windows, or at
least builds that use recent VC CRT libraries,
Mike Williams wrote:
> On 18/08/2010 18:54, Sergey Khorev wrote:
> >>> It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
> >>> unsupported format specifier will result in a crash. On Windows, or at
> >>> least builds that use recent VC CRT libraries, VIM needs to validate the
>
Hi list,
I'm source diving to find out why :noautocmd arguments don't support
completion (no luck so far ;-) and noticed that the documented values
for :command -complete=... don't include 'cscope' and 'sign'. That's
probably because these values both complete suboptions to internal Vim
comma
On 18/08/2010 18:54, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
unsupported format specifier will result in a crash. On Windows, or at
least builds that use recent VC CRT libraries, VIM needs to validate the
format string that it only contains suppor
On 18/08/2010 22:18, Bram Moolenaar wrote:
Mike Williams wrote:
On 18/08/2010 10:09, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
A
18 matches
Mail list logo
