Strange reaction of gvim to : in a normal mode

I use gvim from xfce4 and sometimes get into a strange
situation when pressing : while being in a normal mode
leads not to the command line mode but instead highlights
the icon "Copy to clipboad".

Just now I have noted that in this situation I also cannot
see the version of my gvim via the Help menu (but saving via
the the "Save current file" icon usually works).

The output from the :version command (executed from a newly
started gvim) is as follows:

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Sep 7 2014 11:35:08)
Included patches: 1-273
Modified by Gentoo-7.4.273
Compiled by myself.
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +cmdline_compl +diff +find_in_path +keymap +modify_fname +mouse_xterm +profile -sniff +termresponse +vreplace -xterm_save
+arabic +cmdline_hist +digraphs +float +langmap +mouse +multi_byte +python +startuptime +textobjects +wildignore +xpm
+autocmd +cmdline_info +dnd +folding +libcall +mouseshape +multi_lang -python3 +statusline +title +wildmenu
+balloon_eval +comments -ebcdic -footer +linebreak +mouse_dec -mzscheme +quickfix -sun_workshop +toolbar +windows
+browse +conceal +emacs_tags +fork() +lispindent -mouse_gpm -netbeans_intg +reltime +syntax +user_commands +writebackup
++builtin_terms +cryptv +eval +gettext +listcmds -mouse_jsbterm +path_extra +rightleft +tag_binary +vertsplit +X11
+byte_offset -cscope +ex_extra -hangul_input +localmap +mouse_netterm -perl -ruby +tag_old_static +virtualedit -xfontset
+cindent +cursorbind +extra_search +iconv -lua +mouse_sgr +persistent_undo +scrollbind -tag_any_white +visual +xim
+clientserver +cursorshape +farsi +insert_expand +menu -mouse_sysmouse +postscript +signs -tcl +visualextra +xsmp_interact
+clipboard +dialog_con_gui +file_in_path +jumplist +mksession +mouse_urxvt +printer +smartindent +terminfo +viminfo +xterm_clipboard
system vimrc file: "/etc/vim/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "/etc/vim/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include
/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I
/usr/lib64/glib-2.0/include -I/usr/include/freetype2 -march=native -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: x86_64-pc-linux-gnu-gcc -Wl,-O1 -L/usr/local/lib -Wl,--as-needed -o gvim -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgo
bject-2.0 -lglib-2.0 -lfreetype -lfontconfig -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lncurses -lelf -lacl -lattr -ldl -L/usr/lib64/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -X
linker -export-dynamic

Any ideas how to fix it?

And whom to blame? (Except for myself, of course. :)
My first guess that something is wrong with xfce4 here.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to fix a bug in VIM?

Hi,

On Sat, Nov 1, 2014 at 12:19 PM, Ricardo Teles
<ricardo.oliveira.teles@gmail.com> wrote:
> Hello,
>
> My name is Ricardo, I study at São Paulo university and I am beginner here.
>

Welcome to the list.

>
> I'd like to know how I can contribute to vim? Is there some todo's list?
> How can I take a issue to solve?
>

You should start with the following pages:

http://vim.sourceforge.net/develop.php
https://code.google.com/p/vim/source/browse/runtime/doc/develop.txt

The latest todo list is at:

https://code.google.com/p/vim/source/browse/runtime/doc/todo.txt

Another way to contribute to Vim is to develop unit tests for the
various Vim functionalities.

https://code.google.com/p/vim/source/browse/src/testdir/README.txt

- Yegappan

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: .vimrc not always used

Am Samstag, 1. November 2014 17:53:53 UTC+1 schrieb Eric Christopherson:
> On Thu, Oct 30, 2014, Vlad Ghitulescu wrote:
> > Hello!
> >
> >
> > I'm using the current version of MacVim (Sanpshot 73) on an iMac running
> > OS X 10.10 Yosemite.
> >
> > I have in my home-directory the .vimrc-file attached below.
> > However the .vimrc is working only when opening first MacVim and then a
> > file in a tab. Opening a file via the context-menu or from MacVim via
> > the menu File > Open opens the file in a standard MacVim-window (see the
> > two attached screenshots).
> >
> > Do you have an idea?
>
> I'm not sure if this is related, but MacVim has a preferences option (in
> the MacVim menu > Preferences > Advanced > Enable Quickstart) that
> controls whether .vimrc and ~/.vim/** are reloaded for new windows.
>
> --
> Eric Christopherson

Hi, Eric!

I've put everything from ~/.vimrc in ~/gvimrc too and now all's well.

Regards,
Vlad

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

how to fix a bug in VIM?

Hello,

My name is Ricardo, I study at São Paulo university and I am beginer here. I'd like to know how I can contribute to vim? Is there some todo's list? How can I take a issue to solve?

Thankful.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

vim: Zoomwin plugin stop working after

it's very easy to reproduce. just <c-w><c-o> and then all windows
won't came back anymore. I know this is expected. but what's the value
to keep that if we have Zoomwin? the suggestion will be to provide an
option to also map that to what <c-w>_o does...

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: .vimrc not always used

On Thu, Oct 30, 2014, Vlad Ghitulescu wrote:
> Hello!
>
>
> I'm using the current version of MacVim (Sanpshot 73) on an iMac running
> OS X 10.10 Yosemite.
>
> I have in my home-directory the .vimrc-file attached below.
> However the .vimrc is working only when opening first MacVim and then a
> file in a tab. Opening a file via the context-menu or from MacVim via
> the menu File > Open opens the file in a standard MacVim-window (see the
> two attached screenshots).
>
> Do you have an idea?

I'm not sure if this is related, but MacVim has a preferences option (in
the MacVim menu > Preferences > Advanced > Enable Quickstart) that
controls whether .vimrc and ~/.vim/** are reloaded for new windows.

--
Eric Christopherson

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble using blockwise actions on visual selections in a function/command

On Fri, Oct 31, 2014, Charles Campbell wrote:
> Josef Fortier wrote:
> >I'm trying to extend a "copy and comment" action (leveraging one of the numerous "smart comment" plugins). I've a simple line-wise command and was trying to extend to it work on a visual selection.
> >
> >It looks like vim is set to work linewise (and only linewise) here. Which is not ideal, as rather then commenting a block all at once, I end up with single line comment -> copy repetitions.
> >
> >Things I've tried:
> >
> >A command with -range. This is meant to work in a blockwise fashion
> >
> >A mapping to a function. I have trouble getting the start end end lines. I've tried using `< and `> but these values don't get set (maybe the function is called too soon?).
> >
> >It seems like there should be a way to manipulate visual blocks in a function, but it's not clear to me. Can someone offer assistance?
> >
> You might find the following plugins helpful:
>
> vis.vim (http://www.drchip.org/astronaut/vim/index.html#VIS) : Performs an
> arbitrary Ex command on a visual highlighted block
> NrrwRgn.vim (http://www.vim.org/scripts/script.php?script_id=3075) :
> Narrow Region plugin for Vim
> :he /\%c regexp for restricting match to a specified column
> :he /\%l regexp for restricting match to a specified line
>
> Regards,
> Chip Campbell

I remember seeing another plugin that allowed the user to select text in
any visual mode and then treat the selection as if it were another kind
of selection, e.g. originally selecting in linewise mode but then
prepending characters on it as if it were blockwise. Unfortunately I
can't find that plugin, though.

--
Eric Christopherson

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.