> > Thanks
> >
> > -- Forwarded message -
> > From: tyru
> > Date: 2018年9月23日(日) 19:54
> > Subject: [Patch] Prolog indent plugin for Vim
> > To: Gergely Kontra
> >
> >
> > Dear Gergely,
> >
> > I created a pat
Hello Bram,
I have sent a patch to $VIMRUNTIME/indent/prolog.vim maintaner.
But the email is no longer available.
kgerg...@mcl.hu
So please review and include below patch.
Thanks
-- Forwarded message -
From: tyru
Date: 2018年9月23日(日) 19:54
Subject: [Patch] Prolog indent plugin
Oh someone says help should be wrong because tiny build does not
include +eval,
so +packages is not necessary (thanks @thinca).
Attached patch fixes the help.
2018年7月12日(木) 15:43 tyru :
> Hi Bram,
>
> According to :help +feature-list , +packages feature is enabled by normal
> build.
Hi Bram,
According to :help +feature-list , +packages feature is enabled by normal
build.
But it is actually enabled by tiny build.
Either help or implementation seems wrong.
Thanks
--
Takuya Fujiwara
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your repl
2018年6月11日(月) 3:01 Bram Moolenaar :
>
> Takuya Fujiwara wrote:
>
> > If I don't misunderstand, it seems has('win95') always returns 0 (no
> > entry at f_eval() in evalfunc.c).
> > But it remains in feature-list.
> > I created a patch to remove the line.
>
> I think we can keep the line, since the
2018年6月11日(月) 1:55 tyru :
> Hi Bram,
>
> If I don't misunderstand, it seems has('win95') always returns 0 (no
> entry at f_eval() in evalfunc.c).
>
oops, sorry.
s/f_eval/f_has/
But it remains in feature-list.
> I created a patch to remove the line.
Hi Bram,
If I don't misunderstand, it seems has('win95') always returns 0 (no
entry at f_eval() in evalfunc.c).
But it remains in feature-list.
I created a patch to remove the line.
Thanks
--
Takuya Fujiwara
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type yo
Oh, I forgot to add vim_dev to CC...
-- Forwarded message -
From: tyru
Date: 2018年5月7日(月) 2:43
Subject: Re: Vim license compatibility when porting to another language
To: Bram Moolenaar
Thanks for response!
2018-05-07 2:29 GMT+09:00 Bram Moolenaar :
>
> Tyru wrote:
>
ter *class*, not next word of separated
by whitespaces.
And I ported the original Vim functions in search.c, mbyte.c, and so on.
This is simple library to determine a class of given character.
https://github.com/tyru/node-vim-char-class
And question is, is it safe to port Vim source code to anothe
Hi Bram,
The example code in runtime/doc/if_pyth.txt which was introduced by
40962ec was wrong (it occurs error if it is executed).
Attached the fixed code.
Thanks
--
Takuya Fujiwara
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
Hi Bram,
2017-03-06 1:07 GMT+09:00 Bram Moolenaar :
>
> Tyru wrote:
>
>> > > I sent patches to indent plugins about shiftwidth().
>> > > https://github.com/vim/vim/pull/578
>> > >
>> > > And Bram has fixed it in these co
2017/03/06 15:28 "tyru" :
Hi Bram,
2017/03/06 1:07 "Bram Moolenaar" :
Tyru wrote:
> > > I sent patches to indent plugins about shiftwidth().
> > > https://github.com/vim/vim/pull/578
> > >
> > > And Bram has fixed it in these co
Hi Bram,
2017/03/06 1:07 "Bram Moolenaar" :
Tyru wrote:
> > > I sent patches to indent plugins about shiftwidth().
> > > https://github.com/vim/vim/pull/578
> > >
> > > And Bram has fixed it in these commits (thanks!).
> > > https://g
Hi Bram!
2017/02/19 23:26 "Bram Moolenaar" :
Tyru wrote:
> I sent patches to indent plugins about shiftwidth().
> https://github.com/vim/vim/pull/578
>
> And Bram has fixed it in these commits (thanks!).
> https://github.com/vim/vim/commit/705ada1aff27ecd9c47c690
/89bcfda6834aba724d12554a34b9ed49f5789fd5
https://groups.google.com/forum/#!topic/vim_dev/mRhdDBJh07Y/discussion
But there still are indent plugins which use &shiftwidth directly.
Please see attached patch.
You can see the diff also here.
https://github.com/tyru/vim/commit/a89bc2acb8dfc164a6d98caee20b6787141e64b1
Th
Hi list and Bram,
":&&" tag exists in ":help &" .
=
& Synonym for `:s` (repeat last substitute). Note
that the flags are not remembered, thus it might
actually work differently. You can use `:&&` to keep
the flags.
=
But failed to jump to ":&&" b
Hi Bram,
2016/07/25 0:33 "Bram Moolenaar" :
>
>
> Nicola wrote:
>
> > On 2016-07-24 13:02:56 +, Bram Moolenaar said:
> >
> > > Vim has always been conservative about the default option values.
> > > Without any .vimrc the default is 'compatible'. That's nice for
people
> > > who rely on the o
Hi Bram!
2016-07-24 22:02 GMT+09:00 Bram Moolenaar :
>
> Vim has always been conservative about the default option values.
> Without any .vimrc the default is 'compatible'. That's nice for people
> who rely on the old Vi. But how many of these still exist? I expect
> nearly all Vim users to wan
On Tue, May 3, 2016 at 5:31 PM, tyru wrote:
> On Tue, May 3, 2016 at 5:03 PM, Bram Moolenaar wrote:
>>
>> It appears SourceForge has a problem. It's very slow, database access
>> is timing out. It seems a bit better at the moment.
>
> Thanks for reply.
> Ok
On Tue, May 3, 2016 at 5:03 PM, Bram Moolenaar wrote:
>
> Takuya Fujiwara wrote:
>
>> When I click "login" button at http://www.vim.org/login.php ,
>> I get the following error message since yesterday.
>>
>> > POST has been used more than 500 times within 5 hours.
>> > Assuming bot attack. Retry a
Hi list!
When I click "login" button at http://www.vim.org/login.php ,
I get the following error message since yesterday.
> POST has been used more than 500 times within 5 hours.
> Assuming bot attack. Retry again later. If you continue having trouble write
> to the mailinglist.
What should I d
On Sat, Apr 23, 2016 at 12:55 AM, Charles E Campbell
wrote:
> I think you misunderstood me. The script that I was talking about is
> the one you sent me (ie. the one with autocmd vimrc-guioptions
> FocusGained ... instead of autocmd FocusGained vimrc-guioptions ...).
> Its the second time I've
2016/04/22 6:20 "Charles E Campbell" :
>
> tyru wrote:
>>
>> Hi Vimmers and Dr.Chip,
>>
>> Some items seems to be highlighted wrongly in my vimrc.
>> Please see attached Vim script file, HTML(:TOhtml), screenshot.
>>
>> Vim script fi
2016/04/18 23:05 "Charles E Campbell" :
>
> tyru wrote:
> > Hi Vimmers and Dr.Chip,
> >
> > Some items seems to be highlighted wrongly in my vimrc.
> > Please see attached Vim script file, HTML(:TOhtml), screenshot.
> >
> > Vim script file: repr
sorry, I forgot to say:
* colorscheme is "evening"
* CUI version
* my full vimrc is here:
https://github.com/tyru/dotfiles/blob/1a507e8a0949bf79d5976ae2bb87f6e56fc7c8cd/dotfiles/.vim/vimrc
On Sun, Apr 17, 2016 at 3:14 PM, tyru wrote:
> Hi Vimmers and Dr.Chip,
>
> Som
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
> But what's the difference between backtick(`) and bar(|) ?
@Bram what do you think about this?
On Mon, Mar 28, 2016 at 12:04 AM, LCD 47 wrote:
> On 27 March 2016, Bram Moolenaar wrote:
>>
>> Tyru wrote:
>>
> [...]
>> > * In some places in repeat
On Sun, Mar 27, 2016 at 9:23 PM, Bram Moolenaar wrote:
>
> The backticks work like bars, but highlight the text as a command. I
> started doing this a year ago, so there are still lots of commands in
> bars. The idea is to use backticks where possible.
Oh, I didn't notice that K command works f
On Sun, Mar 27, 2016 at 12:52 AM, Bram Moolenaar wrote:
>
> Gary Johnson wrote:
>
>> I read ":help packages" and ":help add-package", trying to get a
>> better understanding of how this all works, and had a few comments.
>> Vim version is 7.4.1655.
>
> Thanks. The changes after changes may have l
Hi Bram,
On Sun, Mar 27, 2016 at 5:00 AM, Bram Moolenaar wrote:
>
> Patch 7.4.1658
> Problem:A plugin does not know when VimEnter autocommands were already
> triggered.
> Solution: Add the v:vim_did_enter variable.
> Files: src/eval.c, src/main.c, src/vim.h, src/testdir/tes
Hi Gary and Bram,
2016/03/26 1:32 "Gary Johnson" :
>
> I never copied the matchit plugin, as that would have prevented me
> from automatically picking up changes to it. Instead, I created the
> file ~/.vim/plugin/matchit.vim containing this line:
>
> runtime macros/matchit.vim
>
> What is the
2016/03/13 22:34 "Bram Moolenaar" :
>
>
> Patch 7.4.1556
> Problem:"make install" changes the help tags file, causing it to
differ
> from the repository.
> Solution: Move it aside and restore it.
> Files: src/Makefile
>
Thanks :)
so I can keep my local repository clean!
--
Hi list,
I found an interesting feature in 'todo.txt'.
> 8 Custom completion of user commands can't use the standard completion
> functions. Add a hook to invoke a user function that returns the type of
> completion to be done: "file", "tag", "custom", etc.
Could Vim provide this stan
This is small but very significant change for me :)
Thanks Bram!
On Sun, Mar 13, 2016 at 3:04 AM, Bram Moolenaar wrote:
>
> Patch 7.4.1546
> Problem:Sticky type checking is more annoying than useful.
> Solution: Remove the error for changing a variable type.
> Files: src/eval.c, src/te
On Sat, Mar 12, 2016 at 3:32 AM, Bram Moolenaar wrote:
>
> Yasuhiro Matsumoto wrote:
>
>> I often want to clear :messages while debuging vim plugins. So added
>> ":message clear" feature. And this can display last N messages like
>> below.
>>
>> :messages 5
>>
>> How about this?
>
> Hmm. We usual
Is there any progress on this? >Removing sticky type checking
On Tue, Feb 9, 2016 at 8:47 AM, tyru wrote:
> On Tue, Feb 9, 2016 at 6:08 AM, Bram Moolenaar wrote:
>>
>> Takuya Fujiwara wrote:
>>
>>> On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
>>
Hi Bram,
After 'make && make install' in Vim source directory,
runtime/doc/tags gets modified in current HEAD (Patch 7.4.1412).
Normally tags file is not managed under version control.
I know tags file is needed to look up runtime's help,
but the tags file is generated by 'make install'.
I don't
2016/02/23 6:19 "Bram Moolenaar" :
>
>
> Yasuhiro Matsumoto wrote:
>
> > Bram, it seems no one close the channel.
> >
> > diff --git a/src/channel.c b/src/channel.c
> > index aa97088..0cf8718 100644
> > --- a/src/channel.c
> > +++ b/src/channel.c
> > @@ -1708,7 +1708,7 @@ channel_read(channel_T *ch
Hi Vimmers!
I have compiled Vim 7.4.1386 with GTK2 GUI.
And tested the following command:
echo job_start('echo hi')
It hangs only in GTK2 GUI.
CUI Vim does not hang, though.
My :version output is here.
https://gist.github.com/tyru/9647351555282ebc2509
--
Takuya Fujiwara
-
Oh! I was wrong, very upset, sorry... ;(
On Fri, Feb 12, 2016 at 1:26 AM, tyru wrote:
> On Fri, Feb 12, 2016 at 1:08 AM, Bram Moolenaar wrote:
>>
>> Now that we have some functions with a common prefix, it seems to work
>> quite well. The older way of having
On Fri, Feb 12, 2016 at 1:08 AM, Bram Moolenaar wrote:
>
> Now that we have some functions with a common prefix, it seems to work
> quite well. The older way of having read_xxx(), write_xxx(),
> check_xxx() makes functions scatter. xxx_read(), xxx_write() and
> xxx_check() looks better, easier t
On Thu, Feb 11, 2016 at 11:09 PM, h_east wrote:
>
> I suggest that we rename these function names to:
> json_encode()
> json_decode()
> js_encode()
> js_decode()
>
+1
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying t
On Thu, Feb 11, 2016 at 2:00 AM, Bram Moolenaar wrote:
> Keep in mind that the plan is to keep the distributed files where they
> are. This is only for when you want the latest version, or something
> that is not part of the distributed files.
Oh, I have mistaken this.
I got it.
> We might nee
Hi Bram,
On Tue, Feb 9, 2016 at 7:03 PM, Bram Moolenaar wrote:
>
> I had another idea. Currently when installing a plugin or support for
> a language, the files are scattered over different directories under
> $VIMRUNTIME. That makes it hard to update them.
>
> How about this: use $VIMRUNTIME/b
On Tue, Feb 9, 2016 at 6:08 AM, Bram Moolenaar wrote:
>
> Takuya Fujiwara wrote:
>
>> On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
>> >
>> > [adjusted the subject, it was "Why is v:none needed"]
>> >
>> > Takuya Fujiwara wrote:
>> >
>> >> > [...]
>> >> >
>> >> > > >> let json = jsone
On Mon, Feb 8, 2016 at 3:22 AM, Bram Moolenaar wrote:
>
> Tyru wrote:
>
> On Sun, Feb 7, 2016 at 10:27 PM, Bram Moolenaar wrote:
>>
>> Patch 7.4.1274
>> Problem:Cannot run a job.
>
> Please don't quote the whole patch!
>
>> This is a re
On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
>
> [adjusted the subject, it was "Why is v:none needed"]
>
> Takuya Fujiwara wrote:
>
>> > [...]
>> >
>> > > >> let json = jsonencode({"key": v:none})
>> > > >> if json is v:none
>> > > >> echoerr 'error!'
>> > > >> ret
2016/02/08 10:53 "tyru" :
>
> Hi Bram,
>
> 2016/02/08 3:22 "Bram Moolenaar" :
>
> >
> >
> > Takuya Fujiwara wrote:
> >
> > [...]
> >
> > > >> let json = jsonencode({"key": v:none})
> > >
Hi Bram,
2016/02/08 3:22 "Bram Moolenaar" :
>
>
> Takuya Fujiwara wrote:
>
> [...]
>
> > >> let json = jsonencode({"key": v:none})
> > >> if json is v:none
> > >> echoerr 'error!'
> > >> return ...
> > >> endif
> > >
> > > Well, let's just return an empty string. Retur
On Mon, Feb 8, 2016 at 3:22 AM, Bram Moolenaar wrote:
>
> Patch 7.4.1279
> Problem: jsonencode() is not producing strict JSON.
> Solution: Add jsencode() and jsdecode(). Make jsonencode() and
jsondecode()
> strict.
HUGE.
Thanks!! :D
--
--
You received this message from the "vim_dev" maillist.
On Mon, Feb 8, 2016 at 12:53 AM, Bram Moolenaar wrote:
>
> Patch 7.4.1278
> Problem:When jsonencode() fails it still returns something.
> Solution: Return an empty string on failure.
Confirmed.
Thanks! :)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
Sorry, my post are folded in Google Groups because patch content is too big.
Send again.
On Sun, Feb 7, 2016 at 10:27 PM, Bram Moolenaar wrote:
>
> Patch 7.4.1274
> Problem:Cannot run a job.
> Solution: Add job_start(), job_status() and job_stop(). Currently only works
> for Uni
Hi Bram!
On Sun, Feb 7, 2016 at 10:27 PM, Bram Moolenaar wrote:
>
> Patch 7.4.1274
> Problem:Cannot run a job.
> Solution: Add job_start(), job_status() and job_stop(). Currently only works
> for Unix.
> Files: eval.c, structs.h, runtime/doc/eval.txt, src/os_unix.c,
>
On Sun, Feb 7, 2016 at 10:40 PM, Nikolay Aleksandrovich Pavlov
wrote:
> 2016-02-07 8:07 GMT+03:00 tyru :
>> On Sun, Feb 7, 2016 at 8:17 AM, Bram Moolenaar wrote:
>>>
>>> Tyru wrote:
>>>
>>>> >> Sorry Bram, I forgot to send this mail to vim
detect an error, like 'delete()' returns -1 with an error.
>>
>> let json = jsonencode({"key": v:none})
>> if json is v:none
>> echoerr 'error!'
>> return ...
>> endif
>
> Well, let's just r
On Sun, Feb 7, 2016 at 8:17 AM, Bram Moolenaar wrote:
>
> Tyru wrote:
>
>> >> Sorry Bram, I forgot to send this mail to vim_dev.
>> >> Send again with +alpha about problems of current JSON features.
>> >>
>> >> On Sat, Feb 6, 2016 at 11:5
Hi Bram,
On Sun, Feb 7, 2016 at 2:42 AM, Bram Moolenaar wrote:
>
> Tyru wrote:
>
>> Sorry Bram, I forgot to send this mail to vim_dev.
>> Send again with +alpha about problems of current JSON features.
>>
>> On Sat, Feb 6, 2016 at 11:50 PM, Bram Moolenaar wr
Sorry Bram, I forgot to send this mail to vim_dev.
Send again with +alpha about problems of current JSON features.
On Sat, Feb 6, 2016 at 11:50 PM, Bram Moolenaar wrote:
>
>> What do you think about this?
>
> I don't want to spend much time discussing this. v:null and v:none are
> needed just li
> Bram
What do you think about this?
On Thu, Feb 4, 2016 at 11:33 PM, tyru wrote:
> On Thu, Feb 4, 2016 at 10:08 PM, tyru wrote:
>> Hi Nikolay,
>>
>> Thanks for lots of follow-up examples :)
>>
>> On Thu, Feb 4, 2016 at 8:33 AM, Nikolay Aleksandrovich Pav
On Thu, Feb 4, 2016 at 10:08 PM, tyru wrote:
> Hi Nikolay,
>
> Thanks for lots of follow-up examples :)
>
> On Thu, Feb 4, 2016 at 8:33 AM, Nikolay Aleksandrovich Pavlov
> wrote:
>> Since that thread is over I would reply here (did not reply previously
>> because I
ccepts JSON, it should accept
> JSON and not something else. I am not much fond of idea of
> jsondecode() extensions, but do not create *yet another* standard in
> interprocess communications, this action is worse then creating yet
> another non-strict parser.
>
>>
>> So
is very similar.
If a user mistake v:none for v:null,
an invalid JSON (for strict JSON parser) will be generated!
jsonencode([1,v:none,v:none,4])
"undefined" and "null" in JavaScript is totally a bad part.
Please don't follow that.
Best wishes,
tyru
--
--
You receive
Hi list.
On Tue, Feb 2, 2016 at 8:38 PM, Bram Moolenaar wrote:
>
> Yasuhiro Matsumoto wrote:
>
>> > > connect() doesn't have timeout. So when server is down, connect()
>> > > hangs while 1 or 2 minuts. Below is a patch to add timeout query like
>> > > URL.
>> > >
>> > > connect("localhost:12345
/mma.vim
On Mon, Jan 25, 2016 at 11:58 PM, tyru wrote:
> Hi, Vimmers.
>
> I'm sending this email to Vim indent plugins maintainers and vim_dev.
> I suppose all of you maintain `$VIMRUNTIME/runtime/indent/*.vim`.
> I want you to review and merge my modifications.
>
> No
Hi, Vimmers.
I'm sending this email to Vim indent plugins maintainers and vim_dev.
I suppose all of you maintain `$VIMRUNTIME/runtime/indent/*.vim`.
I want you to review and merge my modifications.
Now I'm working on the issue about Vim indent plugins.
(See details below)
https://github.com/vim/v
Hi Manuel
Thanks for your advice.
The advice for English is very helpful!
2013/12/09 2:56 "Manuel Ortega" :
>
>
>> + "nowait" Do not wait another longer mappings
>> +(|:map-|).
>
>
> This isn't quite English. Perhaps "Do not wait to see wheth
Hi list.
maparg() returns Dictionary which contains a key "nowait".
but it is not described in help.
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 08edd10..cc85452 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -4134,6 +4134,8 @@ maparg({name}[, {mode} [, {abbr}
t mode and lang-insert mode, the last one
> doesn't work. (Tyru, 2010 May 6) Or is this intended?
If :lmap is not remappable, above todo also can be removed.
On Sun, Aug 4, 2013 at 4:57 AM, Bram Moolenaar wrote:
>
> Ron Aaron wrote:
>
>> On Friday, August 2, 2013 9:16
Hi Bram!
If my understanding is correct,
The reply doesn't seem to be the answer for the problem I posted?
How about that? Is it a bug? or the behavior is supposed to work?
On Sat, Aug 3, 2013 at 3:16 AM, Bram Moolenaar wrote:
>
> Ron Aaron wrote:
>
>> Perhaps this is related to the bug I repor
Hi list,
The following steps reproduce the problem.
1. :lmap [ {{{
2. i
3. qai[q
4. @a
Step 4 inserts a string "[", not "{{{".
Regards,
--
--
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, visi
Hi Bram.
A random thought floated in my mind,
that checking :TOHtml output between new/old regexp engines can
automate output checking?
On Sun, May 12, 2013 at 1:16 AM, Mark Manning wrote:
> I maintain the freebasic.vim and ibasic.vim files. They are already a part
> of the vim release. No cha
Hi list.
I have read a blog post about gcc extension.
http://mkosaki.blog46.fc2.com/blog-entry-1228.html (Japanese)
The blog title says "_FORTIFY_SOURCE without
__attribute__((alloc_size)) doesn't make sense" .
I've seen some "_FORTIFY_SOURCE" outputs while compiling Vim.
Should we add __attribu
Hi list.
I wrote a patch to add mapadd(), mapdelete() functions,
which adds a new mapping, or deletes existing mapping.
https://gist.github.com/tyru/5460911
current revision:
https://gist.github.com/tyru/5460911/6ecfa0509c0679469d6843026ed08280ef1260c1
test script(it can't be placed i
Hi vimmers!
On Sat, May 11, 2013 at 11:45 AM, Tony Mechelynck
wrote:
> On 10/05/13 10:54, Jan Pobrislo wrote:
>>
>> On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar
>> wrote:
>>>
>>> The top five of the voting list:
>>> http://www.vim.org/sponsor/vote_results.php
>>>
>>> 1. add IDE features
>>
Hi list.
If 'runtimepath' string exceeds 1024 bytes,
'set rtp' output is truncated to 1023 bytes.
Although 'runtimepath' value seems to have complete string value
which exceeds 1024 bytes.
I could see the complete string value by '=&rtp' in insert mode.
Hirohito Higashi(a.k.a. h_east) checked Vi
any response?
On Tue, Feb 19, 2013 at 12:31 AM, tyru wrote:
> Hello vim_dev and Sirtaj Singh Kang(who is the first author of this script).
>
> I wrote a patch for vim2html.pl, which I found in vim runtime directory.
> (":e $VIM/doc/vim2html.pl" to open it)
>
> Here i
Hello vim_dev and Sirtaj Singh Kang(who is the first author of this script).
I wrote a patch for vim2html.pl, which I found in vim runtime directory.
(":e $VIM/doc/vim2html.pl" to open it)
Here is the latest revision of the patch:
https://gist.github.com/ty
On Sun, Feb 3, 2013 at 9:48 PM, Bram Moolenaar wrote:
>
> Hirohito Higashi wrote:
>
>> Hi Bram and Tyru!
>>
>> 2013/1/9(Wed) 5:24:42 UTC+9 Bram Moolenaar:
>> > Tyru wrote:
>> >
>> >
>> >
>> > > Here is a patch to add sha2
On Sat, Feb 2, 2013 at 9:36 PM, h_east wrote:
> Hi Bram and Tyru!
>
> 2013/1/9(Wed) 5:24:42 UTC+9 Bram Moolenaar:
>> Tyru wrote:
>>
>>
>>
>> > Here is a patch to add sha256({string}) function,
>>
>> > which returns SHA256 checksum of {strin
On Tue, Jan 8, 2013 at 10:19 PM, Ingo Karkat wrote:
> On 08-Jan-13 21:58:49 +0900, tyru wrote:
>
>> Hi list.
>>
>> Here is a patch to add sha256({string}) function,
>> which returns SHA256 checksum of {string}.
>>
>> To be honest, I don't know th
Hi list.
Here is a patch to add sha256({string}) function,
which returns SHA256 checksum of {string}.
To be honest, I don't know this patch is useful.
because I've never had a time to use SHA256 checksum in my vim plugins.
but adding sha256() function is quite easy
because SHA256 implementation (
Hi list.
Would you add the following line into $VIMRUNTIME/filetype.vim ?
it is helpful for Mozilla developer.
autocmd BufNewFile,BufRead *.xul setf xml
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 mo
On Tue, Jan 31, 2012 at 7:04 PM, mattn wrote:
> I would sooner add support expanding selected lines than avoiding calling
> with [count].
> For example,
>
> ---
> Supported foo
> Fixed bar
> Fixed baz
> ---
>
> If select lines above and type o, I expect following text.
>
> ---
> 2012-01-31 Yasuhi
On Tue, Jan 31, 2012 at 6:58 PM, Ingo Karkat wrote:
> On 31-Jan-2012 18:49:36 +0900, tyru wrote:
>
>>>> It'd be better if rhs is ":call ..." instead of ":call ..."
>>>
>>> Do you mean that avoid to call the function with :'
oh, I mistook "noremap" for "nnoremap" .
What I wanted to say was that nnoremap's rhs should concern about
input when [count] was given in order to avoid "E481: No range allowed" .
However, in this case, that's not the case I said because the patch is
"noremap", not "nnoremap" .
or more paranoiall
It'd be better if rhs is ":call ..." instead of ":call ..."
2012/01/31 14:07 "mattn" :
> Hi.
>
> o make flicker. is needless.
>
> diff -r 54d621a3b561 runtime/ftplugin/changelog.vim
> --- a/runtime/ftplugin/changelog.vim Thu Jan 26 20:58:26 2012 +0100
> +++ b/runtime/ftplugin/changelog.vim Tue Ja
On Fri, Dec 2, 2011 at 6:40 PM, Yukihiro Nakadaira <
yukihiro.nakada...@gmail.com> wrote:
> `:help getcharmod()` is not correct.
> Result was changed by v7-0055.
> And mouse double, triple and quadruple do not have individual bit.
> Actual result is
>
> 2 shift
> 4 control
> 8 alt
> 16
Yukihiro Nakadaira has told me that each value does not become 1 or 0.
fixed in attached patch.
On Thu, Dec 1, 2011 at 10:49 PM, tyru wrote:
> oops, sorry.
> forgot to fix getcharmod()'s return value. should be "Number or
> Dictionary", not "Number".
>
>
oops... forgot to attach the patch...
On Thu, Dec 1, 2011 at 11:03 PM, tyru wrote:
> Hi list.
>
> I found a small small doc bugs.
> * maparg() can return Dictionary when {dict} was given.
> so return value should be "String or Number"
> * garbagecollect(): &quo
Hi list.
I found a small small doc bugs.
* maparg() can return Dictionary when {dict} was given.
so return value should be "String or Number"
* garbagecollect(): "at_exit" => {at_exit} (argument should be presented as
{arg} or [arg] , right?)
--
You received this message from the "vim_dev" mai
oops, sorry.
forgot to fix getcharmod()'s return value. should be "Number or
Dictionary", not "Number".
On Thu, Dec 1, 2011 at 10:42 PM, tyru wrote:
> Hi list.
>
> I wrote a patch to add {dict} argument to getcharmod().
> `getcharmod(1)` returns Dict
://github.com/tyru/stickykey.vim/blob/aabe981322e7be283b3fc005070e1f99f449558f/autoload/stickykey.vim#L87-L126
--
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/maillis
Also in my environment, the patch fixed the problem. thanks.
On Wed, Nov 30, 2011 at 6:49 AM, Bram Moolenaar wrote:
>
> Ivan Krasilnikov wrote:
>
> > Attached are stack traces of these warnings. Warnings are printed
> > inside removeEventHandler() at gui_beval.c:479..487 as a result of
> > some
I also met this warnings. (I captured the warnings then here)
https://gist.github.com/1393489
My memory is not clear but maybe the warnings occurred when jumping across
windows.
but I don't use netrw.vim. (I use vimfiler.vim instead)
My environment is Linux Mint 11.
My :version is:
VIM - Vi IMpro
Thanks for the review.
I updated the patch.
On Tue, Oct 4, 2011 at 4:19 AM, Yasuhiro MATSUMOTO wrote:
> It prefer to return zero for invalid cases.
>
> let sid getsid()
> if sid
> " using sid
> endif
>
> On Sun, Oct 2, 2011 at 1:52 PM, tyru wrote:
>> Hi list
Hi list.
Vimscript does not have the easy way to get current script ID.
so :help recommends that add s:SID() and use it.
but it is a little bit hacky thing.
so I want to add new vimscript function getsid().
Attached patch added the function and its help.
Could you include this patch?
--
You re
Hi list.
I've found remaining todo which was already implemented.
the todo is "There is no command line completion for ":lmap"."
(it was implemented at this revision
http://code.google.com/p/vim/source/detail?r=bbff28ebfc7a)
Attached patch removes the todo.
--
You received this message from the
Hi list.
Calling a vimscript function which has duplicated argument causes
internal error.
- test.vim -
function! s:foo(a, a)
endfunction
call s:foo(1, 2)
- test.vim end -
$ vim -u NONE -i NONE -S test.vim
will output "E685: Internal error: hash_add()".
Attached patch fixed it t
2011/6/30 lilydjwg :
> On Thu, Jun 30, 2011 at 02:15:51AM +0900, tyru wrote:
>> www.vim.org login page is not working?
>>
>> 1. plugin's page
>> 2. click "upload new version" button
>> 3. login page shows up even if I already logged in.
>>
&
www.vim.org login page is not working?
1. plugin's page
2. click "upload new version" button
3. login page shows up even if I already logged in.
I met this issue in this page:
http://www.vim.org/scripts/script.php?script_id=3133
No message "Authentication failed." in login page
so ID and passwor
1 - 100 din 142 matches
Mail list logo
