Mapping ,<Space> to ,<Space> in produce strange results in conque terminal.

[GoogleCodeExporter]

If you use
    vim -u blank-conque-vimrc.vim -c 'ConqueTerm sh' -c 'inoremap ,<space> ,<space>' -c 'normal A, |'
with the following lines in blank-conque-vimrc.vim:
    set nocompatible
    set rtp=~/.vam/Conque_Shell
(where ~/.vam/Conque_Shell is a directory which contains only Conque), you will 
see something like
    sh-4.0$ |
while without this mapping you will see
    sh-4.0$ , |
, what is expected in a first case also.

Original issue reported on code.google.com by zyx.msu@gmail.com on 13 Sep 2010 at 3:39

[GoogleCodeExporter]

vim-7.3, amd64, gentoo

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 17 2010 03:28:23)
Modified by Gentoo-7.3
Compiled by zyx@zyx-desktop
Huge version without GUI.  Features included (+) or not (-):
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent 
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs 
-dnd 
-ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path 
+find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv 
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent 
+listcmds 
+localmap -lua +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec 
-mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm 
+multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl 
+persistent_undo +postscript +printer +profile +python -python3 +quickfix 
+reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +startuptime 
+statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white 
-tcl 
+terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit 
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu 
+windows +writebackup +X11 +xfontset -xim +xsmp_interact +xterm_clipboard 
-xterm_save 
   system vimrc file: "/etc/vim/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: 
x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -march=amdfam10 
-pipe -mmmx -msse -msse2 -msse3 -msse4a -m3dnow -mfpmath=sse 
-fomit-frame-pointer -D_FORTIFY_SOURCE=1     -I/usr/lib64/ruby/1.8/x86_64-linux 
-DRUBY_VERSION=18 
Linking: x86_64-pc-linux-gnu-gcc   -L. -Wl,-O1 -rdynamic -Wl,-export-dynamic  
-rdynamic  -Wl,-O1 -L/usr/local/lib -o vim    -lXt -lcurses -lacl -rdynamic  
-L/usr/local/lib64 
/usr/lib64/perl5/5.8.8/x86_64-linux/auto/DynaLoader/DynaLoader.a 
-L/usr/lib64/perl5/5.8.8/x86_64-linux/CORE -lperl -lutil -lc 
-L/usr/lib/python2.6/config -lpython2.6 -lutil -Xlinker -export-dynamic   
-Wl,-R -Wl,/usr/lib64 -L/usr/lib64 -lruby18 -lrt -lm   

Original comment by zyx.msu@gmail.com on 13 Sep 2010 at 3:42

[GoogleCodeExporter]

Normal insert mode mappings won't work in conque. When you press ", " those two 
characters are sent to the terminal instead of displayed on the screen. If you 
want to make ", " send some different text to the terminal the mapping is going 
to get a little weird. E.g.:

{{{
inoremap ,<space> <C-o>:sil exe 'sil exe "python ". b:ConqueTerm_Var . 
".write(\", \")"'<CR>
}}}

The general format for sending text to a conque terminal is

{{{
:python ConqueTerm_3.write('some text')
}}}

Where 3 is the terminal number (also in the buffer name, e.g. "bash - 3").

Original comment by nicora...@gmail.com on 13 Sep 2010 at 9:03

• Changed state: WontFix

[GoogleCodeExporter]

I can't find neither b:ConqueTerm_Var nor write method in documentation.

Original comment by zyx.msu@gmail.com on 14 Sep 2010 at 7:45

[GoogleCodeExporter]

ConqueTerm 1.2 will have some new helper functions to make this stuff easier, 
along with documentation for people who want to interact with ConqueTerm at 
more of an API level.

E.g. 

`inoramap ,<space> <C-o>:call conque_term#write(', ')<CR>`

Reopened the issue for tracking...

Original comment by nicora...@gmail.com on 15 Sep 2010 at 5:57

• Changed state: Accepted

[GoogleCodeExporter]

There are some new API functions in the 1.2 release. Hopefully this will be 
easier now.

Original comment by nicora...@gmail.com on 12 Oct 2010 at 1:29

• Changed state: Fixed