OSDN hosting has already become unacceptable.
The console screen appears only once every few times. Also, shell.osdn.net
rarely connects.
2023年8月24日木曜日 15:34:45 UTC+9 Ken Takata:
> Hi Christian,
>
> > For a similar reason and because of the mess I created with the
> > mercurial mirror, I am thi
I suggest moving to another hosting server, the OSDN console has lots of
errors. Perhaps Christian should be able to export the DB.
2023年8月11日金曜日 0:34:20 UTC+9 Christian Brabandt:
>
> On Do, 10 Aug 2023, ciu...@gmail.com wrote:
>
> > Hi Cristian --
> >
> > I've helped with the Vim project in th
Christian, you should have the rights for vim project on OSDN.
If you want to continue to use OSDN, and want to add members, please refer
following URL.
https://osdn.net/projects/vim/memberlist
And click "add member".
Thanks.
2023年8月10日木曜日 15:07:42 UTC+9 John Beckett:
> Thanks for taking this
Chris, Ken. Thanks for working about this.
I would like to help you guys and Vim in the future.
- mattn
2023年8月6日日曜日 17:21:42 UTC+9 Christian Brabandt:
> Ken,
> Please go ahead with enabling discussions and requesting admin rights.
> They may or may not be redirected, don't kno
Currently, vim.org is missing. What is going on?
--
--
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 subscribe
Hi, Bram and all
We vim-jp updated syntax/cpp.vim. Please check and merge this.
Thanks.
https://gist.github.com/mattn/e26d64c8948ddb22a37e28f9bfc68267
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to
Hi, Bram and all.
We vim-jp updated syntax/c.vim and syntax/cpp.vim.
https://github.com/vim-jp/vim-cpp/pull/55
https://gist.githubusercontent.com/mattn/e3e08668896633a088c944d40087f0c3/raw/c491d283ec46706c18c001ec2343a98f7b10df3b/patch.diff
Thanks.
--
--
You received this message from the
Simply poor readability for me.
And it will be difficult to support Vim script syntax highlighting in other
text editors or viewer (like GitHub).
On Saturday, January 4, 2020 at 10:05:53 PM UTC+9, Andy Massimino wrote:
>
> On 1/3/20 8:17 AM, Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> >
If you are thinking vim9 accept to use lambda in the expression in while/for,
it will be confusable.
while {ｰ>1}()
...
}
--
--
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
Why you don't use { ?
--
--
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 subscribed to the Google Groups
"vi
This too, pls
https://patch-diff.githubusercontent.com/raw/vim-jp/vim-cpp/pull/51.patch
On Wednesday, December 18, 2019 at 6:41:25 AM UTC+9, Bram Moolenaar wrote:
>
>
> Yasuhiro Matsumoto wrote:
>
> > Updated syntax/cpp.vim. Please merge in next update of runtime files.
> >
> >
> https://gith
Updated syntax/cpp.vim. Please merge in next update of runtime files.
https://github.com/vim-jp/vim-cpp/commit/0357d5d7ce9225566a8775cdbfd50131b0092e13
mattn
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyi
> vim --clean /path/to/vim/src/if_*.c
> :bufdo tab split
> n
This is all.
vim --clean /path/to/vim/src/if_*.c
:bufdo tab split
:ball
https://go-gyazo.appspot.com/ad695f8d81690638.png
First and last buffer has syntax. But middles are not.
--
--
You received this message from the "vim_dev" mai
> This change is intended to be backwards compatible.
>
> After 8.1.1686 it should be. Let me know if you spot a problem.
As I mentioned in above, this break backward compatibility.
let blue = "blue"
echo 2 *{blue: 3}.blue
Older vim output 6. But new vim output "2 3".
--
--
You receive
> > The name str is unclear. What is better?
>
> There are several existing functions using "str" for string.
> But are these functions really using a string?
writefile is given list of strings. Also join. Both does not have "str" in
function name. So I think that encode_blob/decode_blob is bett
hould be fixed be and clean-up. But sending/receiving patch files via
e-mail make developments slowly. For that I also feed you've better to switch
to development using git.
mattn
On Tuesday, January 22, 2019 at 7:13:37 PM UTC+9, Ingo Karkat wrote:
> -BEGIN PGP SIGNED MESSAGE-
&g
vim will occur errors if some plugins remove ! from their
codes.
mattn
--
--
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 messa
On Monday, August 20, 2018 at 1:37:53 AM UTC+9, Bram Moolenaar wrote:
> Currently, when making a list with continuation lines, it is not
> possible to add a comment somewhere:
>
> let array = [
> \ item,
> \ item,
> \ item,
> \]
>
> Ad
I don't mind. Thanks for reviews and merging.
- mattn
--
--
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, all & administrator of www.vim.org
www.vim.org have login feature. So it must use HTTPS. Currently,
http://www.vim.org/ have cookies which accept HTTP too. If malicious
advertisements are displayed, they might steal the cookie.
- mattn
--
--
You received this message from the &quo
s/SLL/SSL/
--
--
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 subscribed to the Google Groups
"vim_dev" grou
On Wednesday, August 2, 2017 at 7:43:41 PM UTC+9, Ken Takata wrote:
> Hi Bram,
>
> 2016/10/18 Tue 17:16:14 UTC+9 mattn wrote:
> > Hi, Bram.
> >
> > I hope to merge this. When using Visual Studio Code with terminal feature,
> > vim always breaks the termina
previous tests. So we can get faster results.
Regards.
mattn
--
--
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 becau
On Friday, August 4, 2017 at 4:33:48 PM UTC+9, mattn wrote:
> Bram, As far as I can see, it seems JO_XXX flags are filled in bit mask
> 0x already. Do you have plan to be possible to add new flag? For
> example, I want to add new flag for job options "title".
Bram, As far as I can see, it seems JO_XXX flags are filled in bit mask
0x already. Do you have plan to be possible to add new flag? For
example, I want to add new flag for job options "title". This is fixed title
string for the terminal.
--
--
You received this message from the "vim_
Ooops. Sorry. Mistake.
--
--
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 subscribed to the Google Groups
"v
On Friday, August 4, 2017 at 2:23:04 AM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
> > term_start options on Windows seems not work. exit_cb is not called.
>
> Hmm, the options are passed to channel_set_job().
> You'll have to do some debugging to find out why it doesn't work.
jo
term_start options on Windows seems not work. exit_cb is not called.
--
--
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 becau
On Monday, July 31, 2017 at 9:43:23 AM UTC+9, mattn wrote:
> Hi Bram, something wrong when re-activating buffer of terminal.
>
> 1. :terminal
> 2. exit on terminal
> 3. ^W ^W to active another buffer
> 4. :only
> 5. ball
>
> http://go-gyazo.appspot.com/986c1464cb1
Hi Bram, something wrong when re-activating buffer of terminal.
1. :terminal
2. exit on terminal
3. ^W ^W to active another buffer
4. :only
5. ball
http://go-gyazo.appspot.com/986c1464cb1dd8e0.png
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply bel
Sorry, this instead.
https://gist.github.com/b6cc675eac4c67c923b1d952307947f7
--
--
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 mes
On Thursday, July 27, 2017 at 4:41:01 PM UTC+9, Ivan Smirnov wrote:
> On Wednesday, 26 March 2014 21:51:43 UTC, Christian Brabandt wrote:
> > On Mi, 26 Mär 2014, Klaus Rudolph wrote:
> >
> > > C++ Lambda Expressions are now not longer an error in syntax highlighting
> > > and indentation since v
return 1;
> }
> }
> write(1, s, strlen(s));
> return 0;
> }
> ```
>
> gcc -o cursor cursor.c
> vim --clean -c terminal
>
> and execute './cursor off' on terminal buffer, then it occurs descrepancy
> between cursor and in
buggy and flacky, But I'll send pull-request in few days or
> > cupple of weeks.
> >
> > https://github.com/mattn/vim/tree/windows-terminal
>
> Looks interesting.
>
> Looking at the requirements of winpty, this is really difficult to
> build, requires
Hi, all.
Good news. I'm working implement of :terminal using winpty/libvterm on Windows.
http://i.imgur.com/lrm9hr0.gif
Currently, buggy and flacky, But I'll send pull-request in few days or cupple
of weeks.
https://github.com/mattn/vim/tree/windows-terminal
--
--
You rec
;
> > This is in vim/terminal branch in my repository.
> >
> > https://github.com/mattn/vim/tree/terminal
>
> Interesting. What kind of terminal does it pretend to be? With
> libvterm it's like an xterm. On MS-Windows commands expect to be
> running in a conso
Hi, Bram.
I have implementation (but PoC/WIP) that works on Windows.
https://qiita-image-store.s3.amazonaws.com/0/665/67e1a2e1-c2dc-847e-20b6-5b26a0f62b89.gif
This is in vim/terminal branch in my repository.
https://github.com/mattn/vim/tree/terminal
--
--
You received this message from the
On Tuesday, June 13, 2017 at 9:34:27 PM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
> > Just typed
> >
> > :call execute("throw 1")
> > [error appear]
> >
> > :call execute("throw 1")
> > [not appear]
> >
> > I'm thinking, if it's executed from command-line not script or
> > mapp
Ah, I miss it.
On Tuesday, June 13, 2017 at 12:09:55 PM UTC+9, h_east wrote:
> Hi mattn,
>
> 2017-6-13(Tue) 11:27:26 UTC+9 mattn:
> > In cpp, cFloat is wrong highlighted.
> >
> > https://cloud.githubusercontent.com/assets/5300799/25893627/cf4f0266-3578
In cpp, cFloat is wrong highlighted.
https://cloud.githubusercontent.com/assets/5300799/25893627/cf4f0266-3578-11e7-8f87-f587a7a1d3bf.png
Below's change fixes this.
diff --git a/syntax/cpp.vim b/syntax/cpp.vim
index 5a478fb..495a335 100644
--- a/syntax/cpp.vim
+++ b/syntax/cpp.vim
@@ -48,7 +48,7
Just typed
:call execute("throw 1")
[error appear]
:call execute("throw 1")
[not appear]
I'm thinking, if it's executed from command-line not script or mappings, the
errors should be displayed, I think.
On Tuesday, June 13, 2017 at 3:07:49 AM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto w
* line. Put it back in the first column. */
msg_col = 0;
Thanks.
- mattn
--
--
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
Hi, list.
include directive allow to use MACRO.
#include
#include FT_FREETYPE_H
This is patch to fix this problem.
https://patch-diff.githubusercontent.com/raw/vim-jp/vim-cpp/pull/44.diff
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
Hi, list.
A float number 1.0 in cpp is separated as cppNumber(1) and cFloat(.0). Below is
a patch.
https://patch-diff.githubusercontent.com/raw/vim-jp/vim-cpp/pull/48.diff
diff --git a/syntax/cpp.vim b/syntax/cpp.vim
index 5a478fb..495a335 100644
--- a/syntax/cpp.vim
+++ b/syntax/cpp.vim
@@ -48
On Wednesday, March 8, 2017 at 7:07:58 PM UTC+9, mattn wrote:
> hi list.
>
> ~/.tmux.conf is not detected as filetype=tmux because filetype command
> doesn't match it.
>
> diff --git a/runtime/filetype.vim b/runtime/filetype.vim
> index 20e9af4a8..df0397be2 100644
&g
hi list.
~/.tmux.conf is not detected as filetype=tmux because filetype command doesn't
match it.
diff --git a/runtime/filetype.vim b/runtime/filetype.vim
index 20e9af4a8..df0397be2 100644
--- a/runtime/filetype.vim
+++ b/runtime/filetype.vim
@@ -2281,7 +2281,7 @@ au BufNewFile,BufRead .tidyrc,t
On Thursday, November 10, 2016 at 2:36:22 AM UTC+9, DrChip wrote:
> mattn wrote:
> > On Wednesday, November 9, 2016 at 10:53:08 PM UTC+9, Tony Mechelynck wrote:
> >> On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote:
> >>> On Wednesday, November 9, 2016 at 3:58:03 AM UTC
Hi.
Seems to be duplicate ().
diff --git a/src/channel.c b/src/channel.c
index 16156ce..ff97721 100644
--- a/src/channel.c
+++ b/src/channel.c
@@ -1341,7 +1341,7 @@ write_buf_line(buf_T *buf, linenr_T lnum, channel_T
*channel)
p[len] = NL;
p[len + 1] = NUL;
-channel_send(channel,
On Thursday, November 10, 2016 at 2:49:16 AM UTC+9, DrChip wrote:
> mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windows for a long time. Most of
> > operations which use Windows commands of cmd.exe doesn't work because netrw
On Wednesday, November 9, 2016 at 10:53:08 PM UTC+9, Tony Mechelynck wrote:
> On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote:
> > On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
> >> Cesar Romani wrote:
> >
> >> Netrw actually doesn't chec
sion. My opinion may not be a correct
answer for this problem. So if you have opinion about this, please let me known.
I'm very sorry to trouble you about my rude, but waiting your answer.
Thanks.
- mattn
--
--
You received this message from the "vim_dev" maillist.
Do not top
somewhere. And please permit us to
modify the code of netrw for vim-dev or vim-jp.
Best Regards.
Thanks.
- mattn
--
--
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
On Friday, October 28, 2016 at 12:11:37 AM UTC+9, Bram Moolenaar wrote:
> With this patch the channel test failed on AppVeyor. However, when I
> run it on my Windows 7 system it passes...
Yes, I also tested Windows7. I'll update patch to work the part only Windows7
or older.
--
--
You receive
Hi, Bram.
I hope to merge this. When using Visual Studio Code with terminal feature, vim
always breaks the terminal like below.
https://camo.githubusercontent.com/b4af7147f7689b5540ca0efec9d50cdef38c3867/687474703a2f2f676f2d6779617a6f2e61707073706f742e636f6d2f353965643863623539626138313865392e7
Sorry, It was wrong. I updated patch
https://gist.github.com/mattn/d47e7d3bfe5ade4be86062b565a4bfca
On Wednesday, October 12, 2016 at 11:19:06 PM UTC+9, Bram Moolenaar wrote:
> +strsave_for_argv(char_u *string)
>
> I would call the argument "argv" and the escaped result "
On Wednesday, October 5, 2016 at 9:05:11 PM UTC+9, mattn wrote:
> On Wednesday, October 5, 2016 at 5:49:32 AM UTC+9, Bram Moolenaar wrote:
> > Thanks for diving into this. But I think this needs more testing, since
> > it's quite different from what we have before.
> >
On Wednesday, October 5, 2016 at 5:49:32 AM UTC+9, Bram Moolenaar wrote:
> Thanks for diving into this. But I think this needs more testing, since
> it's quite different from what we have before.
>
> I think the "escaping" value needs to be reset after
> for (i = 0; i < escaping; i++)
> Loo
dc74e8c3.png
See this article.
https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/
We should escape double-quote as \" instead of "" if we run without cmd.exe, so
we MUST NOT use shellescape for this. Below
On Monday, October 3, 2016 at 7:49:20 AM UTC+9, Ozaki Kiichi wrote:
>
> https://gist.github.com/ichizok/6e0c00daf387b32bebcc2972f0cca137
Bram, in this patch, you can see workaround to avoid a bug with escaping
double-quote on Windows.
https://gist.github.com/ichizok/6e0c00daf387b32bebcc2972f0cc
On Saturday, July 9, 2016 at 5:20:16 AM UTC+9, Bram Moolenaar wrote:
> I wrote:
>
> > Patch 7.4.2003
> > Problem:Still cursor flickering when a callback updates the screen.
> > (David
> > Samvelyan)
> > Solution: Put the cursor in the right position after updating the screen.
>
Hi list.
When do :grep, we need to type ENTER always. But in most of cases, it doesn't
display anything. How about this patch?
diff --git a/src/ex_cmds.c b/src/ex_cmds.c
index 6535de1..812a119 100644
--- a/src/ex_cmds.c
+++ b/src/ex_cmds.c
@@ -1446,6 +1446,7 @@ do_shell(
#ifdef MSWIN
int
On Friday, September 9, 2016 at 9:52:09 AM UTC+9, mattn wrote:
> okay, will look into it soon.
I tried this but I cound't reproduce this. hmm, seems to be fixed already?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
okay, will look into it soon.
--
--
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 subscribed to the Google Gro
On Tuesday, September 6, 2016 at 12:01:35 AM UTC+9, mattn wrote:
> Below's change fixes this issue, and not break tests.
>
> https://gist.github.com/214b61186e2fe091fa65e2b6fbaa8069
>
> Thanks.
Ah, sorry noisy. Still wrong...
--
--
You received this message from the &q
Below's change fixes this issue, and not break tests.
https://gist.github.com/214b61186e2fe091fa65e2b6fbaa8069
Thanks.
--
--
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.or
behavior is I expected. but tests are failing with my patch.
>From test_channel.vim:
Found errors in Test_out_close_cb():
function RunTheTest[9]..Test_out_close_cb line 26: Expected 2 but got 0
Found errors in Test_pipe_to_buffer_name():
function RunTheTest[9]..Test_pipe_to_buffer_name[1]..Run_tes
On Monday, September 5, 2016 at 11:30:42 AM UTC+9, mattn wrote:
> > Isn't the best solution then to have channel_wait() not return an error?
> > Or is there some way to detect the situation, perhaps by using
> > LastError(). At least it should only affect Windows, since on
> Isn't the best solution then to have channel_wait() not return an error?
> Or is there some way to detect the situation, perhaps by using
> LastError(). At least it should only affect Windows, since on Unix we
> don't want to make this exception.
I say again, This is posssible to be reproduced
Additional, I could reproduce this on Linux.
http://go-gyazo.appspot.com/d1ac2f988bba9549.png
--
--
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 r
On Sunday, September 4, 2016 at 11:19:35 PM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
> > When the job exit immediately, channel->ch_to_be_closed will be TRUE
> > before channel_read even though the output buffer is filled enough to
> > read. For example, following command doesn't
function! PerlCheck()
let s:job = job_start("perl -cw ".expand("%"), { "callback" :
function("Disp") })
endfunction
-
Below is a patch to fix this. This change doesn't break any tests.
https://gist.github.com/130f41a825ec72ccddb55b189d11558f
Tha
Hi, Bram.
In recently, most of data which is transfered in http is possible to be
intercepted by hackers/crackers. So I guess that many plugin author hope to use
https for the login.
How do you think?
- mattn
--
--
You received this message from the "vim_dev" maillist.
Do no
On Thursday, July 14, 2016 at 3:44:54 PM UTC+9, mattn wrote:
> Next update. Added "auto" and quotes binary literals for C++14.
>
>
> https://gist.githubusercontent.com/mattn/86de0abdac858ed8ff5756bb286e6916/raw/7c9d850996ca1e42181de05cf6749ac887bfbcab/gistfile1.diff
>
On Thursday, July 14, 2016 at 3:44:54 PM UTC+9, mattn wrote:
> Next update. Added "auto" and quotes binary literals for C++14.
>
>
> https://gist.githubusercontent.com/mattn/86de0abdac858ed8ff5756bb286e6916/raw/7c9d850996ca1e42181de05cf6749ac887bfbcab/gistfile1.diff
>
Next update. Added "auto" and quotes binary literals for C++14.
https://gist.githubusercontent.com/mattn/86de0abdac858ed8ff5756bb286e6916/raw/7c9d850996ca1e42181de05cf6749ac887bfbcab/gistfile1.diff
Thanks.
--
--
You received this message from the "vim_dev" maillist.
D
On Thursday, July 14, 2016 at 12:49:58 PM UTC+9, ZyX wrote:
> 2016-07-13 19:17 GMT+03:00 mattn :
> > On Wednesday, July 13, 2016 at 4:11:59 AM UTC+9, Bram Moolenaar wrote:
> >
> > Well, I wonder this lambda will be useful. At the first, we hoped to call
> > st
n's lambda. python's
one doesn't allow statements. So usecase are limited to use. I don't have
strong opinion but I'm thinking that this is an new expresssion or language for
the lambda. It will demand to learn the new expression for the users.
- mattn
--
--
You rece
etween the function and the command that become confusing when they have the
> same name (like which flags are allowed). Now with "execute", the command
> will let you do a :redir inside it, but the function won't.
call and call() are also. But I don't think it makes c
On Friday, July 8, 2016 at 9:24:44 AM UTC+9, mattn wrote:
> I guess that this should work with sandbox or no-modelines.
Sorry, someone already pointed.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
I guess that this should work with sandbox or no-modelines.
--
--
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 ar
Hi, Bram.
We have two updates for vim-cpp.
https://patch-diff.githubusercontent.com/raw/vim-jp/vim-cpp/pull/38.patch
And it seems following change doesn't merged in upstream.
- mattn
diff --git a/syntax/cpp.vim b/syntax/cpp.vim
index c7a6838..aa66cef 100644
--- a/syntax/cpp.vim
+++ b/s
http://www.vim.org/scripts/script.php?script_id=5410#11
Note that don't open the attached file. (on windows)
--
--
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/maill
On Wednesday, June 8, 2016 at 1:13:48 AM UTC+9, Ken Takata wrote:
> Hi mattn and all,
>
> 2015/5/25 Mon 13:15:09 UTC+9 mattn wrote:
> > http://go-gyazo.appspot.com/07b65df3b2cdd94b.png
> >
> > Since vim.exe uses ReadConsoleOutputA/WriteConsoleOutputA, wide characte
please check this.
diff --git a/src/quickfix.c b/src/quickfix.c
index 6a38c78..db4c0fa 100644
--- a/src/quickfix.c
+++ b/src/quickfix.c
@@ -207,9 +207,9 @@ qf_init_ext(
char_u *fmtstr = NULL;
char_u *growbuf = NULL;
intgrowbuflen;
-int
diff --git a/src/eval.c b/src/eval.c
index 3542b77..0045967 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -10406,6 +10406,8 @@ f_ch_logfile(typval_T *argvars, typval_T *rettv UNUSED)
f_ch_open(typval_T *argvars, typval_T *rettv)
{
rettv->v_type = VAR_CHANNEL;
+if (check_restricted() || che
On Monday, April 18, 2016 at 9:46:02 AM UTC+9, h_east wrote:
> I found some old style function declarations.
>
> https://gist.github.com/mattn/5bc8ded21e1033c9c0ea8cd5ecbbce11#file-lambda-diff-L401-L403
> https://gist.github.com/mattn/5bc8ded21e1033c9c0ea8cd5ecbbce11#file-lambda-di
Hi, Bram and list.
Updated lambda patch to be applied for latest code.
https://gist.github.com/mattn/5bc8ded21e1033c9c0ea8cd5ecbbce11
This include examples for timer on help file. I'm thinking lambda() have
cooperative to work with job/timer/channel.
So I hope to add this into vim8. H
diff --git a/src/if_py_both.h b/src/if_py_both.h
index d6ae880..ceedd4c 100644
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -3006,7 +3006,6 @@ FunctionAttr(FunctionObject *self, char *name)
static void
set_partial(FunctionObject *self, partial_T *pt, int exported)
{
-typval_T *curtv;
; call garbagecollect()
> else
> call system('touch Xok')
> qa!
> end
> endf
>
> auto VimEnter * :call Init()
> ---
>
> Regards
> Damien
Thanks. please use writefile() instead of system('touch Xok') because windows
doesn
Still have problem.
1. vim -u NONE -N --noplugin
2. :let g:a = job_start(['ls'])
3. wait few seconds
4. :call garbagecollect()
SEGV
--
--
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 ht
E, 100, QS_ALLEVENTS)
https://gist.github.com/mattn/70305daecfc78a5a82d8fe77416c1a23
This patch was written by Yukihiro Nakadaira.
- mattn
--
--
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,
https://gist.github.com/f70b5b3a8f11ae2bf7c72aa8cc1a84f0
updated
--
--
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
call feedkeys("i", "x")
I think this should back to normal mode like ":normal" command.
diff --git a/src/ex_docmd.c b/src/ex_docmd.c
index 26f4219..1f19c88 100644
--- a/src/ex_docmd.c
+++ b/src/ex_docmd.c
@@ -10068,7 +10068,9 @@ exec_normal(int was_typed)
&& typebuf.tb_len > 0
x1f616, 0x1f616},
> {0x1f617, 0x1f617},
> {0x1f618, 0x1f618},
> {0x1f619, 0x1f619},
> {0x1f61a, 0x1f61a},
> {0x1f61b, 0x1f61b},
> {0x1f61c, 0x1f61e},
> {0x1f61f, 0x1f61f},
> {0x1f620, 0x1f625},
> {0x1f626, 0x1f627},
>
On Sunday, March 20, 2016 at 11:14:50 PM UTC+9, Elimar Riesebieter wrote:
> * Bram Moolenaar [2016-03-19 18:42 +0100]:
>
> >
> > Patch 7.4.1604
> > Problem:Although emoji characters are ambiguous width, best is to treat
> > them as full width.
> > Solution: Update the Unicode c
When typing w to jump words in text file contained emoji(s), emoji are skipped
as same as ASCII letters.
https://gist.github.com/mattn/cf8c6de760a33dbc3a28
This patch check the range of emoji codes. I wonder returning 3 for emoji is
good.
- mattn
--
--
You received this message from the
Hi Bram.
let job = job_start('cmd.exe /c echo hello world',
{'out_io':'buffer','out_name':'output'})
This code change current buffer as buftype=nofile, bufhidden.
Should update the target buffer.
diff --git a/src/channel.c b/src/channel.c
index 2a71077..435bec0 100644
--- a/src/channel.c
+++
On Wednesday, March 16, 2016 at 1:03:36 PM UTC+9, mattn wrote:
> Sorry, still bad. I'll look into it.
Updated. Should work.
https://gist.github.com/mattn/394e8a95be26d9c7bce9
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
On Thursday, March 17, 2016 at 6:45:28 PM UTC+9, Bram Moolenaar wrote:
> Can you find out why the check_due_timer() call isn't reached? I had
> tried this with vim.exe and it worked for me. Didn't try much though.
> Might depend on some setting.
To be called check_due_timer, it need to be calle
On Thursday, March 17, 2016 at 7:24:18 AM UTC+9, Bram Moolenaar wrote:
> Yasuhiro wrote:
>
> > On Wednesday, March 16, 2016 at 1:03:36 PM UTC+9, mattn wrote:
> > > Sorry, still bad. I'll look into it.
> >
> > Updated. Should work.
> >
> >
1 - 100 din 815 matches
Mail list logo
