Hi Daniel,
On Fri, Nov 4, 2016 at 1:50 PM, Daniel Hahler wrote:
> Here is a test case:
>
> set errorformat=%m
> lgetexpr '?'
>
> try
> call DoesNotExit()
> catch
> lgetexpr '1'
> finally
> lgetexpr '1'
> endtry
>
> if getloclist(0)[0].text != 1
> echoerr
After pulling 8.0.0055 to 8.0.0062, I get the following warning in the
Tiny build but not in the Huge build:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/option.o
option.c
option.c:5830:1: warning:
Patch 8.0.0062
Problem:No digraph for HORIZONTAL ELLIPSIS.
Solution: Use ",.". (Hans Ginzel, closes #1226)
Files: src/digraph.c, runtime/doc/digraph.txt
*** ../vim-8.0.0061/src/digraph.c 2016-08-29 22:42:20.0 +0200
--- src/digraph.c 2016-11-04 22:15:15.382964392
John Marriott wrote:
> On 05-Nov-2016 06:09, Bram Moolenaar wrote:
> > Patch 8.0.0058
> > Problem:Positioning of the popup menu is not good.
> > Solution: Position it better. (Hirohito Higashi)
> > Files: src/popupmnu.c
> >
> >
> >
> Hi All,
>
> This patch throws this warning without
Patch 8.0.0061 (after 8.0.0058)
Problem:Compiler warning for unused variable.
Solution: Add #ifdef. (John Marriott)
Files: src/popupmnu.c
*** ../vim-8.0.0060/src/popupmnu.c 2016-11-04 20:08:48.277161346 +0100
--- src/popupmnu.c 2016-11-04 22:06:22.479024095 +0100
Patch 8.0.0060
Problem:When using an Ex command for 'keywordprg' it is escaped as with a
shell command. (Romain Lafourcade)
Solution: Escape for an Ex command. (closes #1175)
Files: src/normal.c, src/testdir/test_normal.vim
*** ../vim-8.0.0059/src/normal.c
Nelo-Thara Wallus wrote:
> Of course I forgot the patch. Sorry for the noise.
>
> On 2016-11-03 22:57, Nelo-Thara Wallus wrote:
> > The attached patch fixes the quoting of arguments for ex commands in
> > keyworgprg, issue #1175 in github.
> >
> > See github for a summary of the issue[1].
On Friday, 4 November 2016 22:33:42 UTC+3, DrChip wrote:
> Coacher wrote:
> > On Friday, 4 November 2016 14:36:12 UTC+3, Antony Scriven wrote:
> >> That's because 'o' in 'indentkeys' is causing new lines to be
> >> indented according to 'indentexpr'.
> > Indeed, after 'set indentkeys-=o' gqgq
On Friday, 4 November 2016 22:30:29 UTC+3, DrChip wrote:
> Your example has "filetype plugin indent on" -- that means that you
> have plugins enabled, and anything in ~/.vim/plugin has been loaded (ie.
> sourced). Ditto for indent plugins.
Neither ~/.vim/plugin, nor ~/.vim/indent exists.
--
On 05-Nov-2016 06:09, Bram Moolenaar wrote:
Patch 8.0.0058
Problem:Positioning of the popup menu is not good.
Solution: Position it better. (Hirohito Higashi)
Files: src/popupmnu.c
Hi All,
This patch throws this warning without FEAT_QUICKFIX (on mingw 64):
gcc -c -Iproto -DWIN32
Patch 8.0.0059
Problem:Vim does not build on VMS systems.
Solution: Various changes for VMS. (Zoltan Arpadffy)
Files: src/json.c, src/macros.h, src/Make_vms.mms, src/os_unix.c,
src/os_unix.h, src/os_vms.c, src/os_vms_conf.h,
src/proto/os_vms.pro,
Coacher wrote:
> On Friday, 4 November 2016 14:36:12 UTC+3, Antony Scriven wrote:
>> That's because 'o' in 'indentkeys' is causing new lines to be
>> indented according to 'indentexpr'.
> Indeed, after 'set indentkeys-=o' gqgq works as expected in the case
> described above.
> gqgq works as
Coacher wrote:
> On Wednesday, 2 November 2016 23:50:57 UTC+3, DrChip wrote:
>> Using 8.0.055, I get your expected results. So, I suggest that you
>> check your plugins.
> AFAIU since I have '-u NONE' in cmdline, only system-wide plugins are
> possibly in effect and I don't have any, except for
Hirohito Higashi wrote:
> I found a few issues to the display position of the pop-up menu with preview
> window.
>
> 1) Popup menu often drawing over the preview window.
> 2) Sometimes, popup menu is displayed in the narrow room side.
>
> Preparation before reproduction on Linux:
> - start
Patch 8.0.0058
Problem:Positioning of the popup menu is not good.
Solution: Position it better. (Hirohito Higashi)
Files: src/popupmnu.c
*** ../vim-8.0.0057/src/popupmnu.c 2016-10-27 14:49:11.022995393 +0200
--- src/popupmnu.c 2016-11-04 20:03:00.299805506 +0100
On 2016-11-04, Martin Vuille wrote:
> Is there a way to find out the netrw version at runtime?
:echo g:loaded_netrwPlugin
Regards,
Gary
--
--
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,
Hi Bram and list,
I found a few issues to the display position of the pop-up menu with preview
window.
1) Popup menu often drawing over the preview window.
2) Sometimes, popup menu is displayed in the narrow room side.
Preparation before reproduction on Linux:
- start terminal emulator (e.g.
Patch 8.0.0057 (after 8.0.0056)
Problem:Tests fail without the 'keymap' features.
Solution: Check for feature in test.
Files: src/testdir/test_options.vim
*** ../vim-8.0.0056/src/testdir/test_options.vim2016-11-04
15:23:41.609967769 +0100
--- src/testdir/test_options.vim
Patch 8.0.0056
Problem:When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
Files: src/option.c, src/testdir/test_options.vim
*** ../vim-8.0.0055/src/option.c2016-10-12 17:45:13.638857445 +0200
On Friday, 4 November 2016 14:36:12 UTC+3, Antony Scriven wrote:
> That's because 'o' in 'indentkeys' is causing new lines to be
> indented according to 'indentexpr'.
Indeed, after 'set indentkeys-=o' gqgq works as expected in the case described
above.
gqgq works as expected in non-tex files
On 2 November 2016 at 16:51, Coacher wrote:
> [...] Consider the following file:
>
> \begin{env}
>
x
x
> \end{env}
>
> Open it like this: vim -N
On Wednesday, 2 November 2016 23:50:57 UTC+3, DrChip wrote:
> Using 8.0.055, I get your expected results. So, I suggest that you
> check your plugins.
AFAIU since I have '-u NONE' in cmdline, only system-wide plugins are possibly
in effect and I don't have any, except for plugin manager
22 matches
Mail list logo