On Mon, 2004-05-17 at 17:06, Steve Hall wrote:
> > There's of course still some cream issues:
> > The toolbar still crashes - I had to delete
> > /usr/share/vim/cream/cream-menu-toolbar.vim.
> What version of vim are you using? There were some ancient icon issues
> with vim, but these were resolved ages ago. Other than that, I don't
> know what this could be. Does anyone else see this?
Well, gvim version is the one in debian:
VIM - Vi IMproved 6.3a BETA (2004 May 6, compiled May 13 2004 15:04:55)
Included patches: 1-18
Compiled by Norbert Tretkowski <nobse@...>
Big version with GTK2-GNOME GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+cryptv +cscope +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags
+ex_extra +extra_search +farsi +file_in_path +find_in_path +folding
+fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap
+libcall +linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm
+mouse_netterm +mouse_xterm +multi_byte +multi_lang +netbeans_intg
+path_extra -perl +postscript +printer -python +quickfix +rightleft
+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
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows
+X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/X11R6/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1
-pthread -I/usr/include/libgnomeui-2.0 -I/usr/include/libgnome-2.0
-I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/X11R6/include
-I/usr/include/libxml2 -O2 -DFEAT_LANGMAP -DFEAT_KEYMAP -DFEAT_SIGNS
Linking: gcc -L/usr/X11R6/lib -L/usr/local/lib -o vim
-Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
-lgdk_pixbuf-2.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0
-lgmodule-2.0 -lglib-2.0 -L/usr/X11R6/lib -lgnomeui-2 -lbonoboui-2
-lxml2 -lz -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lpangoft2-1.0
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0
-lpangox-1.0 -lpango-1.0 -lbonobo-2 -lgconf-2 -lgnomevfs-2
-lbonobo-activation -lORBit-2 -lgobject-2.0 -lgthread-2.0 -lm
-lgmodule-2.0 -lglib-2.0 -lXt -lncurses -lgpm
I can't say why it crashes, but if I don't delete the toolbar.vim,
whenever a cream window closes, the gnome crash dialog pops up (without
any info) asking me if i want to restart the crashed application. With
the toolbar.vim removed, everything works.
> > It would be nice if I could disable the time-consuming
> > positioning/resizing everytime a window is opened, without having to
> > hack cream-lib.vim. Maybe a patch for debian users could be done? It
> > would just comment out the last 3 lines of the function
> > Cream_screen_init in there.
> How long is "time-consuming"? GNOME 1.4 on a P3-450 startup for me was
> around a second, GNOME 2.4 on the same box is faster. I think this is
> quite tolerable, considering on the Windows 95a partition it feels
> even faster.
Well, maybe it just feels slow. If the window would open at the saved
position, it would be ok.. but it first opening somewhere, then me
adjusting to that position and preparing to manually move it, then
suddenly the window disappearing under the mouse and spawning somewhere
else.. definitely not a good behavior :P
So an option to disable it really would be nice, since now, whenever a
new version/package is out, I have to re-edit the .vim files. Something
I could put into cream-user.vim would be enough.
> > But if you just want to go with the official releases, then ignore
> > them for now like the imdisable.. Steve already knows about
> > everything and hopefull it will all be fixed in 0.30 :)
> I'm going to try and look at imdisable, but these other issues haven't
> shown up as show-stoppers for others that I'm aware. I'm going to need
> help finding the problem, I can't see it.
Yeah, the window positioning is rather minor. For the other 2.. i'm not
aware of having any non-standard settings (except running
Elias Pschernig <elias@...>