Bram,
On Mon, Apr 04, 2016 at 10:03:22PM +0200, Bram Moolenaar wrote:
>
> Anton Lindqvist wrote:
>
> > If a file passed to the 'qf_init_ext' function contains lines longer
> > than 1021 bytes (might be platform specific) the rest of the line is
> > recognized as a separate error without a valid
Am 2016-04-04 22:13, schrieb Bram Moolenaar:
I have been wondering if the next release should be called 7.5 or 8.
We have quite a few new features, but not that many as with the Vim 7
release. Well, that was a big release. I think the most important
addition since then is persistent undo in 7.3
On Mon, Apr 04, 2016 at 10:03:22PM +0200, Bram Moolenaar wrote:
>
> Anton Lindqvist wrote:
>
> > If a file passed to the 'qf_init_ext' function contains lines longer
> > than 1021 bytes (might be platform specific) the rest of the line is
> > recognized as a separate error without a valid filenam
Then, I think your patch is enough and suitable for now.
Thanks.
2016-04-05 11:33 GMT+09:00 James McCoy :
> On Tue, Apr 05, 2016 at 11:03:02AM +0900, Kazunobu Kuriyama wrote:
> > Good catch, really.
> >
> > One thing I want to make sure since I know little about Wayland
> environments.
> >
> > W
On Tue, Apr 05, 2016 at 11:03:02AM +0900, Kazunobu Kuriyama wrote:
> Good catch, really.
>
> One thing I want to make sure since I know little about Wayland environments.
>
> Which is correctt?
>
> With this patch,
> (1) gtk3vim can be built and works only for genuine X11 environments.
> (2) gtk
Good catch, really.
One thing I want to make sure since I know little about Wayland
environments.
Which is correctt?
With this patch,
(1) gtk3vim can be built and works only for genuine X11 environments.
(2) gtk3vim can be built and works even for Wayland environments, but
through some bridge AP
When built with GTK3, gvim crashes in a Wayland environment. This is
due to lots of X-specific code in the GTK UI.
I'm forwarding the attached patch, from Simon McVittie, which tells GDK
that only the X11 backend is applicable.
>From a quick glance at the GTK/GDK APIs, I didn't find either
backe
Hi,
On Mon, Apr 4, 2016 at 1:13 PM, Bram Moolenaar wrote:
>
> I have been wondering if the next release should be called 7.5 or 8.
> We have quite a few new features, but not that many as with the Vim 7
> release. Well, that was a big release. I think the most important
> addition since then is
On Mon, Apr 4, 2016 at 10:13 PM, Bram Moolenaar wrote:
>
> I have been wondering if the next release should be called 7.5 or 8.
> We have quite a few new features, but not that many as with the Vim 7
> release. Well, that was a big release. I think the most important
> addition since then is per
Hi Bram,
2016/04/05 5:13 "Bram Moolenaar" :
>
> I have made a list of the most important improvements compared to Vim
> 7.4. I might still be missing some (let me know!).
maybe the following features are missing.
* Packages
* Emoji support
* GTK 3 support
--
--
You received this message from
On Mon, Apr 04, 2016 at 10:13:17PM +0200, Bram Moolenaar wrote:
> I have been wondering if the next release should be called 7.5 or 8.
my vote would be for 7.5 -- I run vim with option noloadplugins and I
don't [yet] see any significant improvements to how I use it
that said, I noticed you said
> -Original Message-
> From: Bram Moolenaar [mailto:b...@moolenaar.net]
> Sent: Monday, April 04, 2016 2:20 PM
> To: Owen Leibman
> Cc: vim_dev@googlegroups.com
> Subject: RE: Question About test.ok in Old Style Tests
>
>
> Owen Leibman wrote:
>
> > > > > > There are a number of tests
Owne Leibman wrote:
> > > > > There are a number of tests which fail on z/OS due to ASCII-EBCDIC
> > > > > differences, e.g. sorts.
> > > > > It is not much of a problem to document and ignore these failures,
> > but
> > > > > it would be better to actually run a successful test on z/OS if
> > >
> -Original Message-
> From: vim_dev@googlegroups.com [mailto:vim_dev@googlegroups.com] On
> Behalf Of Bram Moolenaar
> Sent: Monday, April 04, 2016 1:34 PM
> To: Owen Leibman
> Cc: vim_dev@googlegroups.com
> Subject: RE: Question About test.ok in Old Style Tests
>
>
> Owne Leibman wrot
On 2016-04-04, George V. Reilly wrote:
> On Mon, Apr 4, 2016 at 1:16 PM, Christian J. Robinson wrote:
>
> On Mon, 4 Apr 2016, Bram Moolenaar wrote:
>
>
> I have been wondering if the next release should be called 7.5 or 8.
>
>
> I'm inclined to think it should be version 8.
>
ASIO and Jobs alone should perfectly rectify going to 8.0.
--
--
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
---
You received this message because you are
Il giorno lunedì 4 aprile 2016 22:13:23 UTC+2, Bram Moolenaar ha scritto:
> Asynchronous I/O support, channels ~
> Jobs ~
> Timers ~
I suppose these are going to be quite a big change for plugin developers, so
8.0 might be better
--
--
You received this message from the "vim_dev" maillist.
Do
Owne Leibman wrote:
> > > There are a number of tests which fail on z/OS due to ASCII-EBCDIC
> > > differences, e.g. sorts.
> > > It is not much of a problem to document and ignore these failures, but
> > > it would be better to actually run a successful test on z/OS if
> > > possible.
> > > To d
On Mon, Apr 4, 2016 at 1:16 PM, Christian J. Robinson
wrote:
> On Mon, 4 Apr 2016, Bram Moolenaar wrote:
>
> I have been wondering if the next release should be called 7.5 or 8.
>>
>
> I'm inclined to think it should be version 8.
+0.6
--
/George V. Reilly geo...@reilly.org Twitter: @geo
On Mon, 4 Apr 2016, Bram Moolenaar wrote:
I have been wondering if the next release should be called 7.5 or 8.
I'm inclined to think it should be version 8.
- Christian
--
Nurphy's law: Anything that can't be misspelled will be.
Christian J. Robinson http://christianrobinson
I have been wondering if the next release should be called 7.5 or 8.
We have quite a few new features, but not that many as with the Vim 7
release. Well, that was a big release. I think the most important
addition since then is persistent undo in 7.3. Now we have more new
features than in 7.3 o
> -Original Message-
> From: Bram Moolenaar [mailto:b...@moolenaar.net]
> Sent: Monday, April 04, 2016 1:03 PM
> To: Owen Leibman
> Cc: vim_dev@googlegroups.com
> Subject: Re: Question About test.ok in Old Style Tests
>
>
> Owne Leibman wrote:
>
> > There are a number of tests which fa
Anton Lindqvist wrote:
> If a file passed to the 'qf_init_ext' function contains lines longer
> than 1021 bytes (might be platform specific) the rest of the line is
> recognized as a separate error without a valid filename and lnum. If a
> string or list is passed to 'qf_init_ext' the rest of a l
Patch 7.4.1710
Problem:Not all output of an external command is read.
Solution: Avoid timing out when the process has exited. (closes #681)
Files: src/os_unix.c
*** ../vim-7.4.1709/src/os_unix.c 2016-03-28 19:16:15.669846492 +0200
--- src/os_unix.c 2016-04-03 15:46:27.4070
Owne Leibman wrote:
> There are a number of tests which fail on z/OS due to ASCII-EBCDIC
> differences, e.g. sorts.
> It is not much of a problem to document and ignore these failures, but
> it would be better to actually run a successful test on z/OS if
> possible.
> To do so, I hit on the idea
Patch 7.4.1709
Problem:Mistake in #ifdef.
Solution: Change PROOF_QUALITY to DRAFT_QUALITY. (Ken Takata)
Files: src/os_mswin.c
*** ../vim-7.4.1708/src/os_mswin.c 2016-04-03 22:07:35.266508711 +0200
--- src/os_mswin.c 2016-04-04 21:03:28.619435622 +0200
***
*** 270
Ken Takata wrote:
> 2016/4/4 Mon 5:08:29 UTC+9 Bram Moolenaar wrote:
> > Patch 7.4.1705
> > Problem:The 'guifont' option does not allow for a quality setting.
> > Solution: Add the "q" item, supported on MS-Windows. (Yasuhiro Matsumoto)
> > Files: runtime/doc/options.txt, src/gui_w32.c
Ken Takata wrote:
> Hi Bram,
>
> 2016/4/4 Mon 5:08:29 UTC+9 Bram Moolenaar wrote:
> > Patch 7.4.1705
> > Problem:The 'guifont' option does not allow for a quality setting.
> > Solution: Add the "q" item, supported on MS-Windows. (Yasuhiro Matsumoto)
> > Files: runtime/doc/options.txt,
Owen Leibman wrote:
> The patch for regexp_nfa.c with which this thread commenced should
> have been part of this change, and isn't.
> I have confirmed by downloading the most recent version from github -
> regexp.c is patched, regexp_nfa.c is not (so compiles on z/OS will
> still fail).
> Re-att
tldr: Proposal: Change loading packages from pack/start (and
:packloadall) to first add all directories to 'runtimepath' before
sourcing the plugins.
Lcd wrote:
> > > > > On 2 April 2016, Bram Moolenaar wrote:
> > > > > >
> > > > > > Patch 7.4.1699
> > > > > > Problem::packadd does not w
Patch 7.4.1708
Problem:New regexp engine does not work properly with EBCDIC.
Solution: Define equivalence class characters. (Owen Leibman)
Files: src/regexp_nfa.c
*** ../vim-7.4.1707/src/regexp_nfa.c2016-02-12 19:08:10.479766970 +0100
--- src/regexp_nfa.c2016-04-04 20:51:11.12
There are a number of tests which fail on z/OS due to ASCII-EBCDIC differences,
e.g. sorts.
It is not much of a problem to document and ignore these failures, but it would
be better to actually run a successful test on z/OS if possible.
To do so, I hit on the idea of adding the following code to
The patch for regexp_nfa.c with which this thread commenced should have been
part of this change, and isn't.
I have confirmed by downloading the most recent version from github - regexp.c
is patched, regexp_nfa.c is not (so compiles on z/OS will still fail).
Re-attaching patch for regexp_nfa.c to
Hi Bram and Charles,
2016-3-13(Sun) 21:05:56 UTC+9 h_east:
> Hi Charles,
>
> 2016-3-6(Sun) 1:26:30 UTC+9 Bram Moolenaar:
> > Hirohito Higashi wrote:
> >
> > >
> > > 2016-2-1(Sun) 23:47:18 UTC+9 Charles Campbell:
> > > > mattn wrote:
> > > > >> The problem is that the cases of the variables are
Hi,
2016/3/29 Tue 2:27:40 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > 2016/2/24 Wed 22:10:33 UTC+9 Ken Takata wrote:
> > > I have updated the num64 patch. I have merged the three patches into one
> > > again.
> > > This includes the fix of the g problem:
> > > https://groups.google.com
On Friday, 1 April 2016 15:33:03 UTC+2, Ken Takata wrote:
> Hi Andreas,
>
> 2016/4/1 Fri 21:51:38 UTC+9 Andreas wrote:
> > On Friday, 1 April 2016 10:36:17 UTC+2, Ken Takata wrote:
> > > Hi Andreas,
> > >
> > > 2016/4/1 Fri 17:11:12 UTC+9 Andreas wrote:
> > > > I remember now why. When I try to
Hi Bram,
2016/4/4 Mon 5:08:29 UTC+9 Bram Moolenaar wrote:
> Patch 7.4.1705
> Problem:The 'guifont' option does not allow for a quality setting.
> Solution: Add the "q" item, supported on MS-Windows. (Yasuhiro Matsumoto)
> Files: runtime/doc/options.txt, src/gui_w32.c, src/os_mswin.c,
>
On 3 April 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > Error detected while processing
> > > > /home/lcd047/Git/Vim/textobj-comment/plugin/textobj/comment.vim:
> > > > line 27:
> > > > E117: Unknown function: textobj#user#plugin
> > > > Press ENTER or type command to continue
[...]
>
Hi,
If a file passed to the 'qf_init_ext' function contains lines longer
than 1021 bytes (might be platform specific) the rest of the line is
recognized as a separate error without a valid filename and lnum. If a
string or list is passed to 'qf_init_ext' the rest of a long line is
discarded. This p
39 matches
Mail list logo
