Clewn

On Fri, Nov 20, 2009 borasah wrote:
>
> I asked this question, "can I keep the command line window open until it is
> closed by a key stroke", to vim-users mailing list and got an answer:
>


Hello Bora,

The command line window is implemented in the ex_window() function in
ex_getln.c in Vim source code. This is the function header comment:

/*
 * Open a window on the current command line and history.  Allow editing in
 * the window.  Returns when the window is closed.
 * Returns:
 *	CR	 if the command is to be executed
 *	Ctrl_C	 if it is to be abandoned
 *	K_IGNORE if editing continues
 */

So you can't have the window kept open after the command has been
entered, the window is closed at the end of ex_window() before
returning control to the main Vim code.

BTW, why do you want to keep the window open ?


Xavier

2009/11/9 yu huang:
> hi, Xavier,
>
> Here is the output:
> ...
>
>> Please send the output of clewn when you run it with Vim and
>> +netbeans_intg, and with gdb 6.8.


Thanks for the output of clewn.

Please make sure that clewn has been rebuilt from scratch after your
Ubuntu upgrade.

Can you run strace on clewn with the same set of commands as
previously. The command is:

    strace /path/to/clewn 2>strace.log

and please send me `strace.log`.


Xavier

2009/11/11 yu huang:
> Btw, this strace.log is generated from the clewn built from scratch and
> reinstalled


Hello Yu Huang

Thanks for the strace.log.

This looks like a bug in clewn.
On your system, gdb sends to clewn all the command responses in one
shot at the init stage, including the last prompt. Clewn forgets he
has already received the last prompt and hangs waiting for it in the
main loop.

I have made a patch, attached to this mail, that fixes this and adds
log traces in order to confirm this guess, or to help if this is
wrong.

To apply the patch:

    $ tar xzf clewn-1.14.tar.gz
    $ cd clewn-1.14.tar.gz
    $ patch -p0 < /path/to/clewn-hang.diff
    $ ./configure
    $ make clean; make

To test the patch (redirecting logs from stderr to a file):

    $ ./clewn 2> clewn.log

Could you please send me the log file 'clewn.log'.
Thanks.

BTW, from which terminal are you running clewn (xterm, rxvt, ...) ?


Xavier

2009/11/14 yu huang:
>
> I have followed the instructions in the email to make the patch (it patched
> file clewn.c and gdb_lvl3.c),
> and it shows similar behavior when I start clewn.
>
> Here is the clewn.log file.


Thanks for the log file, it helps a lot.
I have managed to tweak clewn code so that it simulates the same
behavior as on your system by receiving gdb data in one chunk, and I
can reproduce the bug. So it is possible now to implement a valid fix.

I will send you a patch shortly, hopefully with a correct fix.


Xavier

On Sun, Nov 15, 2009 at 5:37 PM, Xavier de Gaye wrote:
> 2009/11/14 yu huang:
>>
>> I have followed the instructions in the email to make the patch (it patched
>> file clewn.c and gdb_lvl3.c),
>> and it shows similar behavior when I start clewn.
>>
>> Here is the clewn.log file.
>
>
> Thanks for the log file, it helps a lot.
> I have managed to tweak clewn code so that it simulates the same
> behavior as on your system by receiving gdb data in one chunk, and I
> can reproduce the bug. So it is possible now to implement a valid fix.
>
> I will send you a patch shortly, hopefully with a correct fix.


The attached patch fixes the problem for me, when emulating the pseudo tty
behavior on your system. To apply the patch:

   $ tar xzf clewn-1.14.tar.gz
   $ cd clewn-1.14.tar.gz
   $ patch -p0 < /path/to/clewn-hang-2.diff
   $ ./configure
   $ make


Xavier

On Fri, Nov 6, 2009 at 5:48 AM, yu huang wrote:
>
> I have been using clewn in ubuntu 8.04/8.10 for a long time. It works great.
> Recently I installed ubuntu 9.10, and when I run clewn, it shows
>
> //////////////////////////////////////////////////
> ...
> ... Clewn 1.14 running GDB in level 3 mode
> ...
>
> GNU gdb (GDB) 7.0-ubuntu
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
>
> pre-prompt
> (gdb)
> prompt
> `run' commands do input and output on the terminal /dev/pts/0
>
> NetBeans listens on localhost:3219
>
> NetBeans connected to 127.0.0.1:38666
> ////////////////////////////////////////////////



Gdb 7.0 has been released exactly one month ago (and already in
Ubuntu !).

I have not really tested gdb 7.0  with clewn 1.14, but it runs and I
can set a breakpoint (no error such as the one you are reporting).

Gdb 7.0 introduces important changes in the gdb/mi protocol and
although clewn does not use much of gdb/mi, you should not use gdb
7.0 with clewn 1.14. You can download gdb 6.8 from
http://ftp.gnu.org/gnu/gdb/. The gdb build process is quite
straightforward.


Xavier

2009/11/6 yu huang :
>
> At this time whatever command I type it doesn't respond.
> And then I quit gvim, and it shows
>
> ///////////////////////////////////////////
> disconnected by editor
> NetBeans data socket disconnected
> (gdb)  file test
> ************************************************
> The netbeans socket to Vim is not connected yet.
> Please check that the netbeans_intg feature is compiled in your Vim version
> by running the Vim command ":version", and checking that this command
> displays "+netbeans_intg".
> ************************************************
> //////////////////////////////////////////


Please check that Vim has the netbeans_intg feature, as suggested in
the above error message.

If not, then you can download the latest Vim source from
ftp://ftp.vim.org/pub/vim/unix/

The build process is also easy, although not quite standard:

* run make in vim7/src/ (netbeans_intg is enabled by default)
* run 'make install' as root
* vim is installed in /usr/local/bin


Xavier

On Sat, Nov 7, 2009 at 2:23 PM, Xavier de Gaye <xdegaye@...> wrote:
> 2009/11/6 yu huang :
>>
>> At this time whatever command I type it doesn't respond.
>> And then I quit gvim, and it shows
>>
>> ///////////////////////////////////////////
>> disconnected by editor
>> NetBeans data socket disconnected
>> (gdb)  file test
>> ************************************************
>> The netbeans socket to Vim is not connected yet.
>> Please check that the netbeans_intg feature is compiled in your Vim version
>> by running the Vim command ":version", and checking that this command
>> displays "+netbeans_intg".
>> ************************************************
>> //////////////////////////////////////////
>
>
> Please check that Vim has the netbeans_intg feature, as suggested in
> the above error message.
>
> If not, then you can download the latest Vim source from
> ftp://ftp.vim.org/pub/vim/unix/
>
> The build process is also easy, although not quite standard:
>
> * run make in vim7/src/ (netbeans_intg is enabled by default)
> * run 'make install' as root
> * vim is installed in /usr/local/bin


Sorry to answer to myself.

Before building Vim from source, please check if Ubuntu provides a Vim
package with more features than the one you have installed. Vim may be
built as tiny, small, normal, big and huge, and Ubuntu may have chosen
to provide more than one Vim package.


Xavier