Hi,
2019/6/7 Fri 12:05:15 UTC+9 Ken Takata wrote:
> Hi,
>
> 2019/6/7 Fri 5:51:02 UTC+9 Bram Moolenaar wrote:
> > > I see someone else posted earlier about the same issue.
> > > But those suggestions and also latest git rev do not resolve issue for me.
> >
> > The problem appears to be a broken
On Do, 06 Jun 2019, Bram Moolenaar wrote:
>
> > I see someone else posted earlier about the same issue.
> > But those suggestions and also latest git rev do not resolve issue for me.
>
> The problem appears to be a broken version of msgfmt.
> We can't fix that in Vim. And it appears to be a
On Do, 06 Jun 2019, M Kelly wrote:
> Hi,
>
> I see someone else posted earlier about the same issue.
> But those suggestions and also latest git rev do not resolve issue for me.
Yeah, it looks like Ubuntus msgfmt is seriously broken. Open a bug
report at their issue tracker please.
For the
Since others have posted code, here's mine. In gui_gtk_x11.c:
At file scope:
#ifdef CANBERRA
# include
static ca_context *canberra = 0;
#endif
In gui_mch_beep:
#ifdef CANBERRA
int ca_error;
if (!canberra) // static, initialize on first use
ca_context_create ();
Hi,
2019/6/7 Fri 5:51:02 UTC+9 Bram Moolenaar wrote:
> > I see someone else posted earlier about the same issue.
> > But those suggestions and also latest git rev do not resolve issue for me.
>
> The problem appears to be a broken version of msgfmt.
> We can't fix that in Vim. And it appears to
> I see someone else posted earlier about the same issue.
> But those suggestions and also latest git rev do not resolve issue for me.
The problem appears to be a broken version of msgfmt.
We can't fix that in Vim. And it appears to be a real problem, thus
ignoring it also doesn't appear to be
Patch 8.1.1486
Problem:A listener change is merged even when it adds a line. (Paul Jolly)
Solution: Do not merge a change that adds or removes a line. (closes #4490)
Files: src/change.c, src/testdir/test_listener.vim
*** ../vim-8.1.1485/src/change.c2019-06-01
Dominique wrote:
> Attached are minor doc fixes for vim-8.1.1485.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
105. When someone asks you for your address, you tell them your URL.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///
Christian wrote:
> On Do, 06 Jun 2019, Bram Moolenaar wrote:
> > export VIMRUNTIME; ../vim -f -u unix.vim -U NONE --noplugin
> > --not-a-term -S summarize.vim messages essages" [New File]
> > Error detected while processing
> > /home/travis/build/vim/vim/src/testdir/summariz
> > :
> > line
Hi
Attached are minor doc fixes for vim-8.1.1485.
Regards
Dominique
--
--
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
Hi,
I see someone else posted earlier about the same issue.
But those suggestions and also latest git rev do not resolve issue for me.
-m
--
--
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,
git rev is latest master since a few minutes ago:
* 2019-06-06 773a97c25 (HEAD -> master, origin/master, origin/HEAD) Update
runtime files - Add typescript syntax and indent. (Bram Moolenaar)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below
Hi,
I typically build daily and its been fine until today -
msgfmt --desktop -d . --template gvim.desktop.in -o tmp_gvim.desktop
rm -f LINGUAS
if command -v desktop-file-validate; then desktop-file-validate
tmp_gvim.desktop; fi
/usr/bin/desktop-file-validate
tmp_gvim.desktop: warning: file
> What part of balloons? If you mean 'balloonexpr', it only returns plain
> text. Perhaps you mean the functionality to detect the mouse pointer is
> hovering over text for some time? Well, we could add 'balloonpopup',
> which would open a popup window with anything it likes and return the
>
On 06/06/2019 18:22, Christian Brabandt wrote:
>
> On Do, 06 Jun 2019, Mike Williams wrote:
>
>> The desktop file still seems valid apart from encoding errors. Is there
>> a problem if the makefile ignored the error and continued? Or have a
>
> The problem is, we might not notice failures :(
On Do, 06 Jun 2019, Mike Williams wrote:
> The desktop file still seems valid apart from encoding errors. Is there
> a problem if the makefile ignored the error and continued? Or have a
The problem is, we might not notice failures :(
> build option to allow ignoring errors generating
On Thu, Jun 6, 2019 at 12:04 PM Christian Brabandt wrote:
> On Do, 06 Jun 2019, tooth pik wrote:
>
> > this morning i get a
> >
> > Updating 32e197701..75ee544f9
> > error: Your local changes to the following files would be overwritten by
> > merge:
> > src/testdir/test_clientserver.vim
On Thu, Jun 06, 2019 at 02:07:46PM +0200, Bram Moolenaar wrote:
> I tried a little example:
>
>
> #include
> #include
> int main () {
> ca_context * hello;
> ca_context_create ();
> ca_context_play (hello, 0,
>
On Do, 06 Jun 2019, tooth pik wrote:
> this morning i get a
>
> Updating 32e197701..75ee544f9
> error: Your local changes to the following files would be overwritten by
> merge:
> src/testdir/test_clientserver.vim
> Please commit your changes or stash them before you merge.
> Aborting
Paul Jolly wrote:
> As a follow up to a thread I just started ("Using text properties to
> show rendered documents" -
> https://groups.google.com/forum/#!topic/vim_dev/Armm3XaIleo) I'd like
> to ask whether folks would be supportive of using popup windows
> instead of balloons (or at least
Patch 8.1.1485
Problem:Double free when garbage_collect() is used in autocommand.
Solution: Have garbage collection also set the copyID in funccal_stack.
Files: src/eval.c, src/userfunc.c
*** ../vim-8.1.1484/src/eval.c 2019-06-06 18:05:19.238273419 +0200
--- src/eval.c 2019-06-06
this morning i get a
Updating 32e197701..75ee544f9
error: Your local changes to the following files would be overwritten by merge:
src/testdir/test_clientserver.vim
Please commit your changes or stash them before you merge.
Aborting
when i try to git pull
--
--
You received this
On 06/06/2019 16:48, Christian Brabandt wrote:
>
> On Do, 06 Jun 2019, Mike Williams wrote:
>
>> 16.04 is a Ubuntu LTS and supported for another 18 months or so. It
>> would be nice to think they would want to updated for such an obvious
>> bug on release widely used, but who knows.
>
> Just
Patch 8.1.1484
Problem:Some tests are slow.
Solution: Add timing to the test messages. Fix double free when quitting in
VimLeavePre autocmd.
Files: src/testdir/runtest.vim, src/eval.c
*** ../vim-8.1.1483/src/testdir/runtest.vim 2019-06-06 13:37:56.967789508
+0200
On Do, 06 Jun 2019, Mike Williams wrote:
> 16.04 is a Ubuntu LTS and supported for another 18 months or so. It
> would be nice to think they would want to updated for such an obvious
> bug on release widely used, but who knows.
Just for the fun of it, I have been trying to see what commit
Hi all,
As a follow up to a thread I just started ("Using text properties to
show rendered documents" -
https://groups.google.com/forum/#!topic/vim_dev/Armm3XaIleo) I'd like
to ask whether folks would be supportive of using popup windows
instead of balloons (or at least having this as an option).
On 06/06/2019 15:47, Christian Brabandt wrote:
>
> On Do, 06 Jun 2019, Mike Williams wrote:
>
>> It looks like the last byte of the last character has been dropped in
>> processing. The .in file has the UTF-8 sequence 0xe0 0xad 0x81 0x0a for
>> the last character and the newline, but the tmp
Hi all,
I'm somewhat/extremely behind on the text properties work, which looks
very exciting.
In the context of govim (https://github.com/myitcv/govim), I'm
considering using text properties as a way of showing a simple
rendering of markdown/HTML within a Vim window (popup to be precise).
On Do, 06 Jun 2019, Mike Williams wrote:
> It looks like the last byte of the last character has been dropped in
> processing. The .in file has the UTF-8 sequence 0xe0 0xad 0x81 0x0a for
> the last character and the newline, but the tmp file has 0xe0 0xad 0x0a
> which is an invalid UTF-8
Patch 8.1.1483
Problem:Skipped tests are not properly listed.
Solution: Throw a "Skipped" exception instead of using ":finish" or ":return".
Files: src/testdir/test_breakindent.vim, src/testdir/test_cdo.vim,
src/testdir/test_channel.vim, src/testdir/test_clientserver.vim,
Patch 8.1.1482
Problem:No test for wincol() depending on the 'number' option.
Solution: Add a couple of tests. (Christian Brabandt, closes #4500)
Files: src/testdir/test_gui.vim
*** ../vim-8.1.1481/src/testdir/test_gui.vim2019-03-28 22:04:53.290665042
+0100
---
On 06/06/2019 12:16, Christian Brabandt wrote:
>
> On Do, 06 Jun 2019, Mike Williams wrote:
>
>> Hi
>>
>> On 05/06/2019 20:25, Bram Moolenaar wrote:
>>>
>>> Patch 8.1.1468
>>> Problem:The generated desktop files may be invalid.
>>> Solution: Check validity with desktop-file-validate.
Patch 8.1.1481
Problem:Length for two-digit rgb termresponse is off by one.
Solution: Adjust the length. (closes #4494)
Files: src/term.c
*** ../vim-8.1.1480/src/term.c 2019-06-05 22:57:00.932848350 +0200
--- src/term.c 2019-06-06 15:15:31.928819121 +0200
***
***
Patch 8.1.1480
Problem:Desktop file check doesn't run on CI.
Solution: Install the desktip-file-utils packages. (Christian Brabandt,
closes #4498)
Files: .travis.yml
*** ../vim-8.1.1479/.travis.yml 2019-05-11 14:34:09.326200119 +0200
--- .travis.yml 2019-06-06
Christian wrote:
> On Do, 06 Jun 2019, Bram Moolenaar wrote:
>
> > Patch 8.1.1478
> > Problem:Still an error when running tests with the tiny version.
> > Solution: Do not try reading test.log
> > Files: src/testdir/Makefile, src/testdir/summarize.vim
>
> I did not see any
Patch 8.1.1479
Problem:Change included for debugging only.
Solution: Restore the REDIR_TEST_TO_NULL line.
Files: src/testdir/Makefile
*** ../vim-8.1.1478/src/testdir/Makefile2019-06-06 14:28:50.629869185
+0200
--- src/testdir/Makefile2019-06-06 14:34:35.455882856
Christian wrote:
> On Do, 06 Jun 2019, Bram Moolenaar wrote:
>
> > Patch 8.1.1476
> > Problem:No statistics displayed after running tests.
> > Solution: Summarize the test results. (Christian Brabandt, closes #4391)
> > Also make it possible to report a skipped file.
> >
On Do, 06 Jun 2019, Bram Moolenaar wrote:
> Patch 8.1.1478
> Problem:Still an error when running tests with the tiny version.
> Solution: Do not try reading test.log
> Files:src/testdir/Makefile, src/testdir/summarize.vim
I did not see any failures with the tiny version those
Patch 8.1.1478
Problem:Still an error when running tests with the tiny version.
Solution: Do not try reading test.log
Files: src/testdir/Makefile, src/testdir/summarize.vim
*** ../vim-8.1.1477/src/testdir/Makefile2019-06-06 13:37:56.967789508
+0200
--- src/testdir/Makefile
Patch 8.1.1477
Problem:Test summary fails in the tiny version.
Solution: set 'nocompatible'.
Files: Filelist, src/testdir/summarize.vim
*** ../vim-8.1.1476/Filelist2019-05-25 19:51:03.768408497 +0200
--- Filelist2019-06-06 13:38:48.383437887 +0200
***
*** 118,123
Marius Gedminas wrote:
> On Thu, Jun 06, 2019 at 11:59:34AM +0200, Bram Moolenaar wrote:
> > It appears libcanberra is widely available. My system also has the -dev
> > package installed (I didn't do that, perhaps because of a gtk
> > dependency). I could not find something for autoconf
Hi Bram,
On Do, 06 Jun 2019, Bram Moolenaar wrote:
> Patch 8.1.1476
> Problem:No statistics displayed after running tests.
> Solution: Summarize the test results. (Christian Brabandt, closes #4391)
> Also make it possible to report a skipped file.
> Files:
Patch 8.1.1476
Problem:No statistics displayed after running tests.
Solution: Summarize the test results. (Christian Brabandt, closes #4391)
Also make it possible to report a skipped file.
Files: src/Makefile, src/testdir/Makefile, src/testdir/summarize.vim,
On Do, 06 Jun 2019, Mike Williams wrote:
> Hi
>
> On 05/06/2019 20:25, Bram Moolenaar wrote:
> >
> > Patch 8.1.1468
> > Problem:The generated desktop files may be invalid.
> > Solution: Check validity with desktop-file-validate. (Christian Brabandt,
> > Will Thompson,
On Thu, Jun 06, 2019 at 11:59:34AM +0200, Bram Moolenaar wrote:
> It appears libcanberra is widely available. My system also has the -dev
> package installed (I didn't do that, perhaps because of a gtk
> dependency). I could not find something for autoconf though. But I
> expect it to be
Patch 8.1.1475
Problem:Search string not displayed when 'rightleft' is set.
Solution: Clear the right part of the old text. (closes #4488, closes #4489)
Files: src/search.c, src/testdir/test_search.vim
*** ../vim-8.1.1474/src/search.c2019-05-28 23:08:12.076648654 +0200
---
Hi
On 05/06/2019 20:25, Bram Moolenaar wrote:
>
> Patch 8.1.1468
> Problem:The generated desktop files may be invalid.
> Solution: Check validity with desktop-file-validate. (Christian Brabandt,
> Will Thompson, closes #4480)
> Files:src/po/Makefile
>
A clean
Patch 8.1.1474
Problem:'ttybuiltin' is not tested.
Solution: At least test that it doesn't break things.
Files: src/testdir/test_termcodes.vim
*** ../vim-8.1.1473/src/testdir/test_termcodes.vim 2019-06-06
11:59:15.508182794 +0200
--- src/testdir/test_termcodes.vim
Hi Ken
On 05/06/2019 11:56, Ken Takata wrote:
> Hi,
>
> 2019/6/5 Wed 5:25:13 UTC+9 Mike Williams wrote:
>> On 04/06/2019 19:18, Bram Moolenaar wrote:
>>>
>>> Mike Williams wrote:
>>>
It looks like the change to Windows for resolve() in 8.1.1417 was a
breaking change. I use the
> On 4 Jun 2019, at 19:10, Bram Moolenaar wrote:
> >
> >
> >> I have tried to contact the author of hitest.vim a few days ago, but
> >> didn’t get any answer yet. Anyway, hopefully it’s on this list, too.
> >>
> >> I get E348 with runtime syntax/hitest.vim when whichwrap is set to a value
Patch 8.1.1473
Problem:New resolve() implementation causes problem for plugins.
Solution: Only resolve a resparse point after checking it is needed. (Ken
Takata, closes #4492)
Files: src/os_mswin.c, src/testdir/test_functions.vim
*** ../vim-8.1.1472/src/os_mswin.c
John Little wrote:
> On Wednesday, June 5, 2019 at 1:08:03 AM UTC+12, Bram Moolenaar wrote:
> > I have been wondering if it would help if Vim could play a sound.
>
> I'm a fan. More bandwidth from vim to me is always good. But people wanting
> to turn off beeps from vim are very vocal,
Patch 8.1.1472
Problem:Add_termcap_entry() is not tested.
Solution: Add a simple test.
Files: src/testdir/test_termcodes.vim
*** ../vim-8.1.1471/src/testdir/test_termcodes.vim 2019-06-05
22:57:00.932848350 +0200
--- src/testdir/test_termcodes.vim 2019-06-06
On 5 Jun 2019, at 16:56, 'Lifepillar' wrote:
>
> The enclosed patch adds the changes you mention.
>
> The attached patch uses silent! also on the added command.
>
> About the slowness: I have made some more tests and when there are many
> highlight groups (e.g. those loaded by Vim filetype),
54 matches
Mail list logo
