Hi, Bram and list
I reproduce on console vim 7.3.1195 on linux (fedora 17 64bit)
How to reproduce:
1. Prepare rc file
$ cat ~/vimrc_foo
set tabline=%!Foo()
set guioptions-=e
function! Foo()
return gettabwinvar(1, 0, 'foo')
endfunction
2. Start Vim and :tab new
$ vim -
Hi Bram,
2013/6/16(Sun) 00:55:06 UTC+9 Bram Moolenaar:
> Patch 7.3.1200
>
> Problem:When calling setline() from Insert mode, using CTRL-R =, undo does
>
> not work properly. (Israel Chauca)
>
> Solution: Sync undo after evaluating the expression. (Christian Brabandt)
>
> Files:
Hi Bram and List,
:helptags runtime/doc
E154: Duplicate tag "g:tex_fast" in file runtime/doc/syntax.txt
E154: Duplicate tag "g:tex_isk" in file runtime/doc/syntax.txt
My environment get from most recent repository. (rev. 5023)
--
Best regards,
Hirohito Higashi
--
--
You received this message
Hi Bram,
2013/6/29(Sat) 0:49:19 UTC+9 h_east:
> Hi Bram and List,
>
> :helptags runtime/doc
> E154: Duplicate tag "g:tex_fast" in file runtime/doc/syntax.txt
> E154: Duplicate tag "g:tex_isk" in file runtime/doc/syntax.txt
>
> My environment get fr
Hi Bram,
2013/6/29(Sat) 1:43:05 UTC+9 Bram Moolenaar:
> Hirohito Higashi wrote:
>
>
>
> > :helptags runtime/doc
>
> > E154: Duplicate tag "g:tex_fast" in file runtime/doc/syntax.txt
>
> > E154: Duplicate tag "g:tex_isk" in file runtime/doc/syntax.txt
>
> >
>
> > My environment get from mos
Hi, Manuel and Vimmers.
2013/7/3(Wed) 0:27:51 UTC+9 Manuel Ortega:
> On Tue, Jul 2, 2013 at 3:44 AM, Kazunobu Kuriyama
> wrote:
>
>
> That said, the vim shipped with MacOS X 10.8.4, the version of which is 7.3
> and looks no patch applied, not linked against X11, works well. This
> suggests
Hi Bram and Vim developers,
How to reproduce. (on linux)
- set terminal size to 80x20
- make test
- test92 and test93 fail.
- test92.in and test93.in become empty.<--- unexpected!
Expect behavior
- test92.in and test93.in keep the contents of file.
Investigation result
Line 34th of test92.in
Hi Bram, Christian and Vimmers,
I received a bug report from Taro Muraoka.
This bug occurd in 7.4.085 or later.
How to reproduce.
1. Open new buffer and input below and cursor on the '2'.
123
4567
2. Input j$Aab
Actual behavior
- "23" in the second line is strange obviously.
Hi Ken!
2013/11/19(Tus) 9:34:00 UTC+9 Ken Takata:
> Hi h_east,
>
> 2013/11/19 Tue 3:14:22 UTC+9 h_east wrote:
> > Hi Bram, Christian and Vimmers,
> >
> > I received a bug report from Taro Muraoka.
> > This bug occurd in 7.4.085 or later.
> >
> > --
Hi Bram and Vimmers,
2013/11/19(Tue) 4:09:39 UTC+9 Bram Moolenaar:
> Hirohito Higashi wrote:
>
>
>
> > Hi Bram, Christian and Vimmers,
>
> >
>
> > I received a bug report from Taro Muraoka.
>
> > This bug occurd in 7.4.085 or later.
>
> >
>
> >
>
> > How to reproduce.
>
> >
>
Hi Johannes and Bram,
I received a bug report from Masami Hirata.
runtime/ftplugin/python.vim has two problrems.
#1.
> if exists('*Python_jump') | finish | endif
Line 29 or later is script-local scope. But exists buffer-local
processing.
It's from line 43 to line 62.
How to reproduce.
1. New fi
Hi Christian,
2013/11/27(Wed) 0:10:35 UTC+9 Christian Brabandt:
> I don't have anything to contribute except for this part of the patch:
>
>
>
> > +if has("gui_win32") && !exists("b:browsefilter")
>
> > +let b:browsefilter = "Python Files (*.py)\t*.py\n" .
>
> > +
Hi Bram,
2013/11/28(Thu) 20:46:55 UTC+9 Bram Moolenaar:
> Hirohito Higashi wrote:
>
>
>
> > Hi Christian,
>
> >
>
> > 2013/11/27(Wed) 0:10:35 UTC+9 Christian Brabandt:
>
> > > I don't have anything to contribute except for this part of the patch:
>
> > >
>
> > >
>
> > >
>
> > > > +if
+ b/src/move.cWed Sep 09 12:23:54 2015 +0900
@@ -1769,7 +1769,11 @@
i = 1;
else
#endif
+#ifdef FEAT_DIFF
i = plines_nofill(top);
+#else
+ i = plines(top);
+#endif
used += i;
if (extra + i <= off && bot < curbuf->
ill in src/misc1.c has the same #if so when
> > inside:
> >
> > #if defined(FEAT_DIFF) || defined(PROTO)
> >
> > plines_nofill should be available
>
> correct and that compiles here fine with a tiny version.
defined(PROTO) is no need function caller part.
Only gl
Hi again,
2015-9-9(Wed) 19:01:36 UTC+9 h_east:
> Hi!
>
> 2015-9-9(Wed) 18:17:20 UTC+9 Christian Brabandt:
> > Am 2015-09-09 10:47, schrieb Ike Devolder:
> > > On Wed, Sep 09, 2015 at 01:38:18AM -0700, Tony Mechelynck wrote:
> > >> On Wednesday, September 9,
Hi Yegappan,
2015-9-9(Wed) 23:35:32 UTC+9 yega...@gmail.com:
> Hi,
>
> On Tue, Sep 8, 2015 at 10:59 PM, Yegappan Lakshmanan
> wrote:
> > Hi,
> >
> > On Tue, Sep 8, 2015 at 8:30 PM, h_east wrote:
> >> Hi Tony and Yegappan!
> >>
> >&g
undisplayed.
Actual behavior:
- remains popup menu displayed.
I wrote a patch to fix this issue.
Please check this.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are r
ge) in
settabwinvar(), setwinvar(), gettabwinvar() and getwinvar().
I was previously discussed the similar topic. (sorry in Japanese)
https://github.com/vim-jp/issues/issues/765
I don't know the autocommand block/unblock policy.
Thanks.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
little lost
What Vim version are you using?
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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
---
Hi,
2015-10-1 (Thu) 7:51:32 UTC+9 h_east:
> Hi,
>
> 2015-10-1 (Thu) 7:11:19 UTC+9 Celes-Eternal:
> > Hello,
> >
> >
> > I have a problem with my vim since some times.
> >
> > I'm using compton + urxvt + vim with true transparency (that'
pos in findmatchlimit().
But, next call find_start_rawstring() calls findmatchlimit().
This may the contents of comment_pos is changed unexpectedly.
I wrote a patch contains test.
Please check this.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "
constructor, so it can be used
> as the basis for indenting the block, finds the scope declaration and
> keys off of that instead.
>
> The cindent code is pretty hairy. I wasn't able to find an obvious fix.
I can reproduce it.
And began to investigate.
Perhaps I would fix this p
Hi James and Bram,
2015-10-4 (Sun) 22:29:23 UTC+9 h_east:
> Hi James!
>
> 2015-8-2 (Sun) 13:46:34 UTC+9 James McCoy:
> > Given the file foo.cc
> >
> > -- >8 --
> > class a {
> > public:
> > a() : i(0)
> >
HON3 and UNIX.
Not only Unix.
I think Masatoshi's patch is right.
And patch 7.4.890 is wrong.
Look for combination of DYNAMIC_PYTHON and DYNAMIC_PYTHON result on build.
enable DYNAMIC_PYTHON enable DYNAMIC_PYTHON3 Build result
yes yes OK
yes no
Bram,
Thanks for brushing up my patch. Excellent!!
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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/ma
y called once from if_python.c, when both python and
> > > python3 are compiled in. And only for Unix. So the #if should use an
> > > AND between DYNAMIC_PYTHON and DYNAMIC_PYTHON3 and UNIX.
> >
> > Not only Unix.
> > I think Masatoshi's patch is right.
Hi, Masatoshi and Bram,
2015-10-9 (Fri) 0:45:46 UTC+9 Masatoshi SUGIURA:
> 2015年10月7日水曜日 22時48分46秒 UTC+9 h_east:
> > Hi Bram,
> >
> > 2015-10-7 (Wed) 21:37:46 UTC+9 Bram Moolenaar:
> > > Hirohito Higashi wrote:
> > >
> > > > 2015-10-4 (Sun)
Hi
2015-10-7 (Wed) 10:26:08 UTC+9 h_east:
> Hi James and Bram,
>
> 2015-10-4 (Sun) 22:29:23 UTC+9 h_east:
> > Hi James!
> >
> > 2015-8-2 (Sun) 13:46:34 UTC+9 James McCoy:
> > > Given the file foo.cc
> > >
> > > -- >8 --
Hi Bram,
2015-10-12 (Mon) 0:18:12 UTC+9 h_east:
> Hi
>
> 2015-10-7 (Wed) 10:26:08 UTC+9 h_east:
> > Hi James and Bram,
> >
> > 2015-10-4 (Sun) 22:29:23 UTC+9 h_east:
> > > Hi James!
> > >
> > > 2015-8-2 (Sun) 13:46:34 UTC+9 James McCoy
Hi Kazuki and Bram,
2015-10-18 (Sun) 0:19:18 UTC+9 Bram Moolenaar:
> Kazuki Sakamoto wrote:
>
>
>
> > On Unix, the 'luadll', 'perldll', 'pythondll', 'python3dll', and 'rubydll'
>
> > options can be used to specify the shared library file for the interfaces
>
> > instead of DYNAMIC_*_DLL files
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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 su
Hi Bram and Charles,
2015-10-14(Wed) 0:00:09 UTC+9 Charles Campbell:
> h_east wrote:
> > To: vim_dev
> > Cc: Charles E. Campbell (As a Vim syntax file Maintainer)
> >
> > Hi,
> >
> > I add a few keywords to syntax/vim.vim
> > (belloff bo invfixeol invf
cations' is not a
> directory
>
> What is the correct directory?
I don't know well.
But, Installation succeed on fedora 21.
cp ../runtime/vim.desktop ../runtime/gvim.desktop \
/usr/local/share/applications
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
variable: g:nr:
E15: Invalid expression: str[g:nr:]
Expected behavior:
- Both displayed 'de'
Actual behavior
- Occured E121 and E15.
I wrote a patch. (including test)
Please check this.
--
Best Regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "
Hi Tony,
2015-11-4(wed) 18:07:49 UTC+9 Tony Mechelynck:
> On Wed, Nov 4, 2015 at 5:33 AM, h_east wrote:
> > Hi Bram and List!
> >
> > How to reproduce:
> > - Start pure vim with new file a.vim
> > $ vim -N -u NONE a.vim
> >
> > (1)
> > :let st
Hi Christian!
2015-11-4(Thu) 18:53:13 UTC+9 Christian Brabandt:
> Am 2015-11-04 05:33, schrieb h_east:
> > Hi Bram and List!
> >
> > How to reproduce:
> > - Start pure vim with new file a.vim
> > $ vim -N -u NONE a.vim
> >
> > (1)
> > :let st
to this email directly or view it on GitHub.
--
Best Regards,
Hirohito Higashi (a.k.a h_east)
--
--
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.
ime is about 20:00)
--
Best Regards,
Hirohito Higashi (a.k.a h_east)
--
--
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 Christian and Bram,
2015-11-6(Fri) 19:55:44 UTC+9 h_east:
> Hi Christian!
>
> 2015-11-6(Fri) 17:28:03 UTC+9 Christian Brabandt:
> > Bram,
> > here is another one (possibly).
> >
> > https://github.com/neovim/neovim/pull/3614
> >
> > Not sure, i
is is as far as I could investigate - does anyone know a way to debug
> what sequences are sent to the terminal?
It can be confirmed by trachet.
(http://saitoha.github.io/trachet/)
I use often this.
--
Best Regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "
Hi Bram,
The termcap code 't_Cs' and 't_Ce' is not supported.
But documented. so that delete this.
It doesn't seem to be supported at least Vim 7.0.001.
(I don't know it previously.)
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this messa
rite that are not well understood.
Thanks
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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
---
Y
288
Bram>
If is the following display by make, Please check and commit
runtime/syntax/vim.vim.
make[1]: Entering directory '/home/h_east/vim/vim/src/gen_syntax_vim'
Update ../../runtime/syntax/vim.vim
make[1]: Leaving directory '/home/h_east/vim/vim/src/gen_syntax_vim'
'+eval'
> > - Never update when error in gen_syntax_vim.vim script.
> > - Neovim already generate syntax/vim.vim automatically.
> > https://github.com/neovim/neovim/pull/2288
> >
> >
> > Bram>
> > If is the following display by make, Please che
tabpagenr()
> +: let tab_change = 1
>
>
> But here it is `tab_change`.
>
>
> +: exec "tabnext " . a:tab
> +: endif
> +: let bufname = fnamemodify(bufname(winbufnr(a:win)), mod)
> +: if tab_changed
> +: tabprevious
> +: endif
Oops, Thanks fo
and window and
> 2. allows getcwd({tab}) to return tab-local working directory should this
> feature be implemented (see https://github.com/neovim/neovim/pull/3229).
These added arguments was imitating an existing built-in function arglistid().
I think this is better.
--
Best regards,
Hirohi
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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 s
ci.appveyor.com/project/chrisbra/vim/build/75
Thanks for reporting!
This breaks may be fixed by attached patch.
Please confirm a patch.
--
Best Regards,
Hitohiro Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below
igashi (a.k.a h_east)
--
--
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
Hi,
2015-11-20(Fri) 14:20:48 UTC+9 h_east:
> Hi,
>
> 2015-11-20(Fri) 6:43:29 UTC+9 Christian Brabandt:
> > Which one is line 5790? Can you print the value ofr fr and curfr? (use p fr
> > and p curfr on the gdb prompt at frame 7)
>
> I can reproduced it. (fedora21 +
Hi,
2015-11-20(Fri) 15:10:26 UTC+9 h_east:
> Hi,
>
> 2015-11-20(Fri) 14:20:48 UTC+9 h_east:
> > Hi,
> >
> > 2015-11-20(Fri) 6:43:29 UTC+9 Christian Brabandt:
> > > Which one is line 5790? Can you print the value ofr fr and curfr? (use p
> > >
mode after operation
> + zzz
> + xxx
> + ---
> +
> + gv in exclusive select mode without operation
> + xxx
> + ---
> *** ../vim-7.4.928/src/version.c 2015-11-19 19:55:12.340839491 +0100
> --- src/version.c 2015-11-19 19:59:18.198202378 +0100
>
veyor.com/project/chrisbra/vim
I think 'feedkeys()' has bug on Windows.
Perhaps, It takes time to find out. First, How about to revert the test_utf8?
Thanks.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not
problem.
I PRed.
Please check this thread.
https://groups.google.com/d/topic/vim_dev/AoP6YvafJM8/discussion
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
ring after that character.
>
>
>
> So the simple solution is to tell feedkeys() to insert, using the "i"
>
> flag. I tried it and it fixes the problem for me.
I see! It is great solution!
I think it should be documented for the people to write the test.
Like one:
W
gt;
> > Best regards,
> > Laurent Lyaudet
> >
> >
> Hello!
>
> I don't mind the snapshots -- but I'd really like to have a copy of the
> file causing problems so that I don't have to type it myself.
>
> Thank you, and thank you for the feedba
Hi Chip Campbell,
2015-11-24(Tue) 0:42:54 UTC+9 DrChip:
> h_east wrote:
> > BTW, There is a thread that you must reply.
> > https://groups.google.com/d/topic/vim_dev/ZSUw8grrOhw/discussion
> I already have a vim.vim syntax generator.
Of course I know.
Please read my comm
ir/test_eval.ok has changed
>
> This part is missing. Perhaps you can attach the file as it is after
> the patch.
Sorry. I update a patch.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply
agcase, When feature is small or tiny.
I wrote a patch.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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/ma
hanks.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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,
2015-12-3(Thu) 7:09:43 UTC+9 Random832:
> On 2015-12-02, h_east wrote:
> > I am trying to add new feature to Vim.
> > It's CLPUM(Command-line mode PopUp Menu)
>
> Would this replace 'wildmenu'? Would it work with it, if someone
> still prefers the sing
Hi Gary,
2015-12-3(Thu) 11:16:52 UTC+9 Gary Johnson:
> On 2015-12-02, h_east wrote:
> > Hi,
> >
> > 2015-12-3(Thu) 7:09:43 UTC+9 Random832:
> > > On 2015-12-02, h_east wrote:
> > > > I am trying to add new feature to Vim.
> > > > It's
Hi Random832,
2015-12-3(Thu) 11:18:21 UTC+9 Random832:
> On 2015-12-03, h_east wrote:
> > Yes and No.
> > It can be switched by the 'clpum' option.
>
> It seems like two parallel ways of implementing essentially the same
> functionality. I'm particula
r will it fall back to not showing the mode when 'cmdheight' is
> one?
Yes. When 'cmdheight' is one, do not show the completion mode.
Is it better to show?
>
> I don't think the completion itself should be different from 'wildmenu',
> only the way th
2015-10-13 23:21:27 +0200 2122) au BufNewFile,BufRead
*/systemd/*.{automount,mount,path,service,socket,swap,target,timer} setf
systemd
Above line was changed by following commit.
> commit 60cce2fb736c8ff6fdb9603f502d3c15f1f7a25d
> Author: Bram Moolenaar
> Date: Tue Oct 13 23:21:
2015-12-5(Sat) 21:54:36 UTC+9 h_east:
> Hi,
>
> 2015-12-5(Sat) 21:07:19 UTC+9 Christian Brabandt:
> > Hi Elimar!
> >
> > On Fr, 04 Dez 2015, Elimar Riesebieter wrote:
> >
> > > * Christian Brabandt [2015-12-04 14:33 +0100]:
> > >
> &g
> > 1 25
> > 4 58
> > -
> >
> > actual:
> >
> > -
> > 2 24
> > 5 57
> > -
> >
> > It appears that content of redobuff is incorrect.
> >
> > expected: 1j11
> > actual:
for me. Any idea what makes it fail?
>
> Some feature missing perhaps?
>
>
> It fails for me too on OS X 10.11.1.
I got the failed result that same as Kenichi's and Manuel's.
I using latest git repository. Check on fedora.
Vim configure is below:
./congifure --w
ine is not wrapped. And cursor move to after the last character of the
last line.
Investigation result:
- The 'linebreak' process should do after 'listchars-spaces'.
I wrote a patch.
Please check it.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this messa
ded from 'big' or 'huge'. (Default feature is
'normal')
You should add configure option to 'with-features=big'.
Please see a following help.
:h 'conceal'
:h +conceal
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this
- Vi IMproved 7.4 (2013 Aug 10, compiled Dec 9 2015 09:59:20)
Included patches: 1-963
Compiled by h_east@localhost.localdomain
Huge version with GTK2-GNOME GUI.
...
Confirm result:
The following message has been displayed in the vim.
GOT HERE#1
GOT HERE#2
GOT HERE#3
server's repl
Hi Christian,
2015-12-9(Wed) 19:31:40 UTC+9 Christian Brabandt:
> On Sa, 05 Dez 2015, h_east wrote:
>
> > Hi Bram and List,
> >
> > How to reproduce:
> > - Start Vim with some setting.
> > $ vim -N -u NONE -c "set listchars=space:_ list line
Hi Chip and Vim developer!
NOTE:
I received by e-mail directly to the following reply from Chip.
On 2015/12/10 1:31, Charles E Campbell wrote:
> h_east wrote:
>> Hi Chip,
>>
>> 2015-12-9(Wed) 8:26:41 UTC+9 Charles Campbell:
>>> Hello!
>>>
>>>
other local changes.
>
> For details of my Vim installation, see the attached bugreport.txt.
I can not reproduce it.
But I make a patch to Avoid SEGV in preedit finish.
Can you try this patch?
Thanks
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message
Hi Timo and Chiristian!
2015-12-12(Sat) 22:32:52 UTC+9 h_east:
> Hi Timo,
>
> 2015-12-12(Sat) 16:59:21 UTC+9 Timo Mihaljov:
> > I'm experiencing random segmentation faults in GVim when searching the
> > file list in the vim-ctrlspace plugin. I don't have a reliable
Hi Christian,
2015-12-12(Sat) 22:45:35 UTC+9 Christian Brabandt:
> On Sa, 12 Dez 2015, h_east wrote:
>
> > > Can you try this patch?
> >
> > Oh, I was duplicate to Christian's patch :-)
>
> quite amusing...
Marrie me! :-)
--
Best regards,
Hirohito Higash
#issuecomment-164290359
https://groups.google.com/d/msg/vim_dev/yYBH5sNXejU/iACNdveHBgAJ
Thanks.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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 informat
Hi Christian,
2015-12-14(Mon) 22:51:35 UTC+9 Christian Brabandt:
> Am 2015-12-14 13:12, schrieb h_east:
> > Hi,
> >
> > I have a little confusion by this. I would like you to fix quickly, if
> > possible.
> >
> > Sample #1
> > This comment contrib
Hi Christian,
2015-12-15(Tue) 4:43:30 UTC+9 Christian Brabandt:
> On Mo, 14 Dez 2015, h_east wrote:
>
> > Hi Christian,
> >
> > 2015-12-14(Mon) 22:51:35 UTC+9 Christian Brabandt:
> > > Am 2015-12-14 13:12, schrieb h_east:
> > > > Hi,
> > >
Hi Bram,
2014-11-24(Mon) 7:28:36 UTC+9 Bram Moolenaar:
> Hirohito Higashi wrote:
>
> > 2014/11/23(Sun) 0:03:33 UTC+9 Bram Moolenaar:
> > > Hirohito Higashi wrote:
> > >
> > > > 2014/11/22(Sat) 11:08:53 UTC+9 h_east:
> > > > > Hi Bram an
e
numerical reference process.
Please check this.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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
h:
:set bs=2
:set bs?
backspace=2
After this patch:
:set bs=2
:set bs?
backspace=indent,eol,start
I think this is no problem :-)
>
> When refactoring it's always good to first have a test, so we can check
> if the behavior before and after is the same. There is some testing o
5.4 and earlier:
doc> value effect
doc> 0 same as ":set backspace=" (Vi compatible)
doc> 1 same as ":set backspace=indent,eol"
doc> 2 same as ":set backspace=indent,eol,start"
snip...
>
> > > When refactoring it
e left alone, but they can get
> overwritten.
>
> Comments are welcome.
Vim body and the runtime files until now had been provided at the same time.
However, care must be taken a little When it comes to update only the runtime
files.
If we use the new options or commands in runtim
d the following to the end of the test_cdo.vim?
" Tests for ldo and lfdo
function Test_ldo()
call XdoTests('l')
call XfdoTests('l')
endfunction
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
D
Hi Bram and List,
2015-12-18(Fri) 15:39:03 UTC+9 h_east:
> Hi Bram and List,
>
> 2015-12-17(Thu) 23:04:20 UTC+9 Bram Moolenaar:
> > Hirohito Higashi wrote:
> >
> > > 2015-12-17(Thu) 21:30:43 UTC+9 Bram Moolenaar:
> > > > Hirohito Higashi wrote
func Test_assert_false()
call assert_false(0)
endfunc
func Test_assert_true()
snip...
- run test_assert
$ make test_assert
cd testdir; rm -f test_assert.res; make -f Makefile test_assert.res
VIMPROG=../vim SCRIPTSOURCE=../../runtime
make[1]: Entering directory '/home/h_east/xxx/github/vim/src/testdir&#
n,
> > Error occured.
>
> >
>
> > Example:
>
> > ```
>
> > $ cd vim/src/testdir
>
> > $ make clean
>
> > $ cd ..
>
> > $ make test_alot
>
> > Error detected while processing
> > /home/h_east/samba/github/vim/src/testdir/r
s: $(NEW_TESTS)
>
> .vim.res:
> ! $(RUN_VIMTEST) -S runtest.vim $*.vim
snip...
Individual test results are unnoticed from this changes.
How to reproduce:
$ cd vim/src
$ make test_alot
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "
Hi Bram and List,
2015-12-29(Tue) 8:24:18 UTC+9 h_east:
> Hi Bram,
>
> 2015-12-28(Mon) 22:05:54 UTC+9 Bram Moolenaar:
> > Patch 7.4.980
> > Problem:Tests for :cdo, :ldo, etc. are outdated.
> > Solution: Add new style tests for these commands. (Yegappan Laks
d, ...) can
be used only in the features normal or later.
Sorry, My mistake.
I wrote a patch.
Please check and include it.
Thanks for reporting this.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
27;* *'nf'*
-'nrformats' 'nf' string (default "octal,hex")
+'nrformats' 'nf' string (default "bin,octal,hex")
local to buffer
{not in Vi}
This defines what base
is patch.
Jason Schulz>
Sorry to such just your patch was included.
I have just completed the doing has been working since last fall :-)
Thanks.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
Hi Bram,
2016-1-7(Thu) 16:04:39 UTC+9 h_east:
snip...
> > That's a big change. Can you give an example of what didn't work before
> > and works now?
>
> Please see Test_visual_increment_27() ~ Test_visual_increment_34().
> Below is ather exsample.
>
> C
e what is going on, the commands themselves are still a
> bit of a puzzle. Since the explanations were already written, we can
> keep them. Using the comment above the test function should work well.
Indeed. I did it. Please check and include attached patch.
BTW, The following changes
;g:cryptmethod = cm_save
endif
return ret
endfunc
It will also be able to correspond to the blowfish2 with a little ingenuity.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
explanations were already written, we can
> > > keep them. Using the comment above the test function should work well.
> >
> > Indeed. I did it. Please check and include attached patch.
>
> Thanks!
Thanks for including this.
Patch 7.4.1072
https://groups.google.com/d/
ttached patch.
> > >
> > > Thanks!
> >
> > Thanks for including this.
> > Patch 7.4.1072
> > https://groups.google.com/d/topic/vim_dev/_K0eQkIB5aY/discussion
> >
> > >
> > > > BTW, The following changes I thought happy for
ached patch would be fixed this warning.
Please confirm this.
Thanks for reporting.
--
Best regards,
Hirohito Higashi (a.k.a h_east)
--
--
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
1 - 100 din 703 matches
Mail list logo
