2017-08-30 4:54 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>:
> On Tuesday, August 29, 2017 at 12:49:33 AM UTC-4, Kazunobu Kuriyama wrote:
> > 2017-08-29 12:16 GMT+09:00 Manuel Ortega <manny...@gmail.com>:
> >
> >
> > On Saturday, August 26, 2017 at 9:58:28 AM UTC-4, Manuel Ortega wrote:
> >
> > > On Sat, Aug 26, 2017 at 9:50 AM, Bram Moolenaar wrote:
> >
> > >
> >
> > >
> >
> > >
> >
> > > It is working on my Mac machine. Can you use ch_logfile() to find out
> >
> > >
> >
> > > what happens?
> >
> > >
> >
> > >
> >
> > > Unfortunately, I don't know how to do this. How do I use a VimScript
> function before doing `make test`?
> >
> > >
> >
> > >
> >
> > > -Manny
> >
> >
> >
> > If someone would post the exact instructions I need to follow, then I
> can do the debugging locally.
> >
> >
> >
> > -Manny
> >
> >
> >
> > If you don't have any specific instructions other than that from Bram, I
> think the following will do.
> >
> > (1) In order to have the test in question write a log, change the file
> src/testdir/test_terminal.vim like this:
> >
> > diff --git a/src/testdir/test_terminal.vim b/src/testdir/test_terminal.
> vim
> > index d651d0bba..e8cdb4a39 100644
> > --- a/src/testdir/test_terminal.vim
> > +++ b/src/testdir/test_terminal.vim
> > @@ -452,6 +452,8 @@ func Test_terminal_list_args()
> > endfunction
> >
> > func Test_terminal_noblock()
> > + call ch_logfile('/tmp/Test_terminal_noblock.log')
> > +
> > let g:buf = term_start(&shell)
> >
> > for c in ['a','b','c','d','e','f','g','h','i','j','k']
> > @@ -481,6 +483,8 @@ func Test_terminal_noblock()
> > unlet g:job
> > unlet g:lnum
> > bwipe
> > +
> > + call ch_logfile('')
> > endfunc
> >
> > func Test_terminal_write_stdin()
> >
> > --
> > Note that how ch_logfile() is used. You can change the file path or
> even the function's behavior. See :help ch_logfile() for details. Also,
> note that ch_logfile('') is used to stop logging. The resulting file will
> get very huge, so if you forget to stop it, then ...
> >
> > (2) Build Vim as usual.
> >
> > (3) Make sure your $PWD is /../vim/src, and run
> >
> > $ make test_terminal
> >
> > Then, you'll have the log file /tmp/Test_terminal_noblock.log.
>
> Thanks, Kazunobu. I did what you said except that I picked a different
> location for the logfile to be recorded to.
Ah, that's what I wanted to mean by "You can change the file path or..."
Perhaps I should have put it more clearly.
I am completely unqualified to recognize what lines in the logfile would
> count as "suspicious". Shall I zip the logifle and post it here?
>
Yeah, resulting log files are large enough to make us hesitant about
sending it to vim_dev, but since there's no other ways than that, I hope
people kindly let us to do so when seeing such files sent zipped.
> -Manny
>
> --
> --
> 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" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
--
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" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
