FS#13937 - [vim] CSApprox needs gui support - not loading.

Attached to Project: Arch Linux
Opened by Vasilii (Vasilii) - Tuesday, 24 March 2009, 10:51 GMT
Last edited by Tobias Kieslich (tobias) - Thursday, 25 June 2009, 16:31 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

VIM is not compiled with graphical support and signs by default. Why ?

Also sometimes I get message like "Signs not supported by this compilation" and some of plugins do not work.


Additional info:
* package version(s)

VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec 7 2008 18:43:21)
Заплатки: 1-65
Скомпилирован ArchLinux
Большая версия без графического интерфейса

( That means without graphical interface ).



Включённые (+) и отключённые (-) особенности:
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv +cscope +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 +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 +postscript +printer -profile +python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff
+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
общесистемный файл vimrc: "/etc/vimrc"
пользовательский файл vimrc: "$HOME/.vimrc"
пользовательский файл exrc: "$HOME/.exrc"
значение $VIM по умолчанию: "/usr/share/vim"
Параметры компиляции: gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=i686 -mtune=generic -O2 -pipe -D_FORTIFY_SOURCE=1 -D_REENTRANT -D_GNU_SOURCE -I/usr/loc
al/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/core_perl/CORE -I/usr/include/python2.6 -pthread -I/usr/lib/ruby/1.8/i686-linux
Сборка: gcc -L. -rdynamic -Wl,-export-dynamic -Wl,-E -L/usr/local/lib -o vim -lXt -lncurses -lacl -lgpm -Wl,-E -L/usr/local/lib -L/usr/lib/perl5/cor
e_perl/CORE -lperl -lutil -lc -L/usr/lib/python2.6/config -lpython2.6 -lutil -Xlinker -export-dynamic -Wl,-R -Wl,/usr/lib -L/usr/lib -lruby -lm
* config and/or log files etc.

% vim CSApprox needs gui support - not loading.
















Steps to reproduce:
This task depends upon

Closed by  Tobias Kieslich (tobias)
Thursday, 25 June 2009, 16:31 GMT
Reason for closing:  Not a bug
Additional comments about closing:  people who want extended support for stuff in vim shall install gvim as it also makes the console based vim binary more powerful
Comment by Kessia Pinheiro (even) - Tuesday, 24 March 2009, 12:13 GMT
Hi, please, use english when post something.
GUI support are provided with GVIM, not VIM.
Comment by Vasilii (Vasilii) - Tuesday, 24 March 2009, 13:18 GMT
> Hi, please, use english when post something.

Im sorry for that.

>GUI support are provided with GVIM, not VIM.

Yes I know, but vim can be compiled with gui support and signs support too as far as i know, this way it works fine in Xterm and other terminals that support 256 colors. Of course i can start it like gvim -v in my xterm but this way I have to make /usr/bin/vim as an alias to script that executes gvim -v
Comment by Vasilii (Vasilii) - Sunday, 19 April 2009, 17:17 GMT
http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
Comment by Tobias Kieslich (tobias) - Monday, 01 June 2009, 21:12 GMT
not all people like to install all the dependencies (like x and gtk2) just to run vim from a terminal. Therefore, vim is compiled without those dependencies. If you need fancier things, install gvim. It replaces the vim binary with a more capable one, so after install calling "vim" actually will have all that support, even if called from a terminal.
Comment by Vasilii (Vasilii) - Tuesday, 02 June 2009, 07:31 GMT
And many people I know who would like to have it :) .
> so after install calling "vim" actually will have all that support, even if called from a terminal.
Unfortunatelly not. I have installed gvim and execution from terminal "vim" still alerts "No gui support, and without signs ".
It replaces the vim binary with a more capable one - seems it does'nt do that.

Ok. If this makes too much pain you can close this issue. No problem. Thank you for response.
Comment by Kessia Pinheiro (even) - Tuesday, 02 June 2009, 12:09 GMT
Why not create two packages: vi-minimal (without X and gtk2 depends) and vim-full (with all what we need)? These resolve all problems. I like vim, i dont care with X dependencies, if i dont want those, i install vi.

Comment by Tobias Kieslich (tobias) - Tuesday, 02 June 2009, 15:09 GMT
The vim packaging scheme is changing at the moment:
nvi for core, a minimalistic vim for config files upon startup
vim for extra, the smaller vim mainly for console application
gvim for the full fletched stuff, X support, GUI support, all scripting

allthough currently the vim/gvim duties are the same as in th new scheme, it's exactly what you are describing anyway ...
@Vasilii: it should replace those (not directly, but via Symlinking) if not the install mechanism is borked but with the current scheme I haven't heard of anyone having trouble with that

Loading...