On Mar 29, 8:26 am, <kyu...@gmail.com> wrote:
> I am trying to copy & paste a word under the cursor.
>
> Typing yip in normal mode will yank a word at the current cursor position.
:help ip
*v_ip* *ip*
ip "inner paragraph", select [count] paragraphs (see
|paragraph|).
Exception: a blank line (only containing white space)
is also a paragraph boundary.
When used in Visual mode it is made linewise.
Bill
--
--
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/groups/opt_out.
Friday, March 29, 2013
Re: Plugin alternatives (was: Profiling vim)
On Thursday, March 28, 2013 1:39:16 PM UTC-5, Gary Johnson wrote:
> On 2013-03-27, Christian Brabandt wrote:
> > On Wed, March 27, 2013 10:13, Marco wrote:
> > > On 2013 03 27 Christian Brabandt wrote:
> > >
> > >> What does git-gutter do better than any of the existing plugins?
> > >
> > > What are those existing pluginsť? I'm curious.
> >
> > http://www.vim.org/scripts/script.php?script_id=3052
> > http://www.vim.org/scripts/script.php?script_id=2712
> > http://www.vim.org/scripts/script.php?script_id=2584
> > http://www.vim.org/scripts/script.php?script_id=1881
> >
> > There are probably even more...
This is funny, because I just installed a change indicator plugin yesterday (I
didn't use one before). I used this one (which is quite new, and not in your
list):
http://www.vim.org/scripts/script.php?script_id=4487
I save too often (impulsively, even) for a "changes since last save" to be
useful to me at all. So Christian's "changesPlugin" (at least from reading the
description) is no good for me.
I did not see sign-diff, which is one reason I didn't try it. I may not have
anyway; it has not had an update on vim.org since 2009 (maybe that's just
because it's so stable, I don't know). Additionally, the description says "a
cmd.exe shows up at front". I don't know how distracting that would be, the
video link won't load for me.
I also did not see quickfixsigns, I did not realize that one could show change
indicators as well. This one I probably won't try, unless the balloon popups
show the actual changed lines or something. I already get the quickfix signs
through Eclim so I don't need that feature. Apparently the plugin also does
relative line numbers and some other things. This seems like too much feature
bloat for my tastes. Eclim is the only 3rd-party plugin I use frequently that
has a ton of features I don't use. I generally like my plugins lean, mean, and
focused.
svndiff doesn't work on Windows. I tried this one first and attempted to make it
work on Windows, but it uses shell redirection in ways that just won't work for
Windows, so I gave it up.
From the name and from a quick glance at the documentation, it looks like
git-gutter only supports git. I only use Mercurial and SVN. So that's a complete
nonstarter.
signify (the one I installed) didn't work on Windows out-of-the-box when I
installed it, but the fixes were easy and have been incorporated (in much better
fashion) in the upstream. So I'm using it now and am quite happy with it. It is
a small, focused plugin with all the features I want for now. The only thing
it's missing is an easy way to see the original line for changed or deleted
lines. I could see myself adding a balloonexpr for this in the future if the
devs don't do it for me first.
>
> What is the attractiveness of using signs to indicate where changes
> have taken place? When I follow changes, I'm more interested in
> _what_ the changes were, not just that something changed. For this
> I use DiffOrig or a variation that compares the current buffer with
> the latest (or a specified) VCS version. Having a sign in the left
> column doesn't tell me enough to be useful.
>
I like the visual indication of where I've made changes; I can normally remember
what those changes were after seeing the visual reminder that I made one. It's a
nice way to remind myself, "oops, I'd better remove that debug code before I
build" or "oh yeah, I added a new variable, I better defined it" or other such
things. I always do a full diff before I commit, but most of the time I just am
looking for a quick reminder of what I'm working on, and going out to Kdiff3
or hacking a "diff with comitted version" vim command is overkill.
--
--
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/groups/opt_out.
> On 2013-03-27, Christian Brabandt wrote:
> > On Wed, March 27, 2013 10:13, Marco wrote:
> > > On 2013 03 27 Christian Brabandt wrote:
> > >
> > >> What does git-gutter do better than any of the existing plugins?
> > >
> > > What are those existing pluginsť? I'm curious.
> >
> > http://www.vim.org/scripts/script.php?script_id=3052
> > http://www.vim.org/scripts/script.php?script_id=2712
> > http://www.vim.org/scripts/script.php?script_id=2584
> > http://www.vim.org/scripts/script.php?script_id=1881
> >
> > There are probably even more...
This is funny, because I just installed a change indicator plugin yesterday (I
didn't use one before). I used this one (which is quite new, and not in your
list):
http://www.vim.org/scripts/script.php?script_id=4487
I save too often (impulsively, even) for a "changes since last save" to be
useful to me at all. So Christian's "changesPlugin" (at least from reading the
description) is no good for me.
I did not see sign-diff, which is one reason I didn't try it. I may not have
anyway; it has not had an update on vim.org since 2009 (maybe that's just
because it's so stable, I don't know). Additionally, the description says "a
cmd.exe shows up at front". I don't know how distracting that would be, the
video link won't load for me.
I also did not see quickfixsigns, I did not realize that one could show change
indicators as well. This one I probably won't try, unless the balloon popups
show the actual changed lines or something. I already get the quickfix signs
through Eclim so I don't need that feature. Apparently the plugin also does
relative line numbers and some other things. This seems like too much feature
bloat for my tastes. Eclim is the only 3rd-party plugin I use frequently that
has a ton of features I don't use. I generally like my plugins lean, mean, and
focused.
svndiff doesn't work on Windows. I tried this one first and attempted to make it
work on Windows, but it uses shell redirection in ways that just won't work for
Windows, so I gave it up.
From the name and from a quick glance at the documentation, it looks like
git-gutter only supports git. I only use Mercurial and SVN. So that's a complete
nonstarter.
signify (the one I installed) didn't work on Windows out-of-the-box when I
installed it, but the fixes were easy and have been incorporated (in much better
fashion) in the upstream. So I'm using it now and am quite happy with it. It is
a small, focused plugin with all the features I want for now. The only thing
it's missing is an easy way to see the original line for changed or deleted
lines. I could see myself adding a balloonexpr for this in the future if the
devs don't do it for me first.
>
> What is the attractiveness of using signs to indicate where changes
> have taken place? When I follow changes, I'm more interested in
> _what_ the changes were, not just that something changed. For this
> I use DiffOrig or a variation that compares the current buffer with
> the latest (or a specified) VCS version. Having a sign in the left
> column doesn't tell me enough to be useful.
>
I like the visual indication of where I've made changes; I can normally remember
what those changes were after seeing the visual reminder that I made one. It's a
nice way to remind myself, "oops, I'd better remove that debug code before I
build" or "oh yeah, I added a new variable, I better defined it" or other such
things. I always do a full diff before I commit, but most of the time I just am
looking for a quick reminder of what I'm working on, and going out to Kdiff3
or hacking a "diff with comitted version" vim command is overkill.
--
--
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/groups/opt_out.
how to undo a register insertion using i_CTRL-R?
I love the ability of inserting a register content, directly in insert mode, using i_CTRL-R. However, this gets me into trouble from time to time.
For example, I might be on a roll, and without leaving insert mode, I enter a whole paragraph or three, which I want to finish with a contents of a register, which I insert using i_CRTL-R. Except, it turns out I did not get the right register (e.g., there was an intervening cut, so it's no longer "1 but rather "2 or "3). Instead of the expected word or phrase, I accidentally pasted a register which contained massive amount of text. Great, I'll just hit undo key in normal mode to undo it. But hold on! This also undoes the whole paragraph or three I typed in before the mistake.
Gah, how do I undo just the register insertion?! Or do I have to train myself to leave insert mode before register pastes?
--
--
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/groups/opt_out.
For example, I might be on a roll, and without leaving insert mode, I enter a whole paragraph or three, which I want to finish with a contents of a register, which I insert using i_CRTL-R. Except, it turns out I did not get the right register (e.g., there was an intervening cut, so it's no longer "1 but rather "2 or "3). Instead of the expected word or phrase, I accidentally pasted a register which contained massive amount of text. Great, I'll just hit undo key in normal mode to undo it. But hold on! This also undoes the whole paragraph or three I typed in before the mistake.
Gah, how do I undo just the register insertion?! Or do I have to train myself to leave insert mode before register pastes?
--
--
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/groups/opt_out.
Re: Register overwritten only when clipboard=unnamed
I am trying to copy & paste a word under the cursor.
Typing yip in normal mode will yank a word at the current cursor position.
Move the cursor somewhere else and type viwp then you will paste the yanked word.
I investigated this a little bit and found it's related to guioptions=+a.
Thanks
보낸 사람: Christian Brabandt
보낸 날짜: 2013년 3월 29일 금요일 오후 9:06
받는 사람: vim_use@googlegroups.com
보낸 날짜: 2013년 3월 29일 금요일 오후 9:06
받는 사람: vim_use@googlegroups.com
On Do, 28 Mär 2013, PARK, Kyung-Kook wrote:
> I am not sure whether or not this is an obscure side effect which I
> can figure out. But when I set clipboard=unnamed, vip followed by yiw
> does not operate in the way I expected - actually nothing happens. It
> operates as expected I omit clipboard=unnamed from my vimrc. In a
> normal situation, it must yank a word from the current cursor position
> and paste it somewhere I want.
vip followed by yiw does not make sense. Please be more specific.
What exactly did you do, what do you expect and what happens?
Oh, and what Vim version are you using?
regards,
Christian
--
Hallo Birkenstockträger!
--
--
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/groups/opt_out.
Re: Plugin alternatives
Hi Gary!
On Do, 28 Mär 2013, Gary Johnson wrote:
> On 2013-03-27, Christian Brabandt wrote:
> > On Wed, March 27, 2013 10:13, Marco wrote:
> > > On 2013 03 27 Christian Brabandt wrote:
> > >
> > >> What does git-gutter do better than any of the existing plugins?
> > >
> > > What are those existing pluginsť? I'm curious.
> >
> > http://www.vim.org/scripts/script.php?script_id=3052
> > http://www.vim.org/scripts/script.php?script_id=2712
> > http://www.vim.org/scripts/script.php?script_id=2584
> > http://www.vim.org/scripts/script.php?script_id=1881
> >
> > There are probably even more...
>
> What is the attractiveness of using signs to indicate where changes
> have taken place? When I follow changes, I'm more interested in
> _what_ the changes were, not just that something changed. For this
> I use DiffOrig or a variation that compares the current buffer with
> the latest (or a specified) VCS version. Having a sign in the left
> column doesn't tell me enough to be useful.
I don't know. I made the plugin for fun a couple of years ago after a
similar question here. Personally, I don't see the sense of the
indicators but I can understand, if some people like it.
regards,
Christian
--
Alle Männer vom Fach sind darin sehr übel dran, dass ihnen nicht
erlaubt ist, das Unnütze zu ignorieren.
-- Goethe, Maximen und Reflektionen, Nr. 964
--
--
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/groups/opt_out.
On Do, 28 Mär 2013, Gary Johnson wrote:
> On 2013-03-27, Christian Brabandt wrote:
> > On Wed, March 27, 2013 10:13, Marco wrote:
> > > On 2013 03 27 Christian Brabandt wrote:
> > >
> > >> What does git-gutter do better than any of the existing plugins?
> > >
> > > What are those existing pluginsť? I'm curious.
> >
> > http://www.vim.org/scripts/script.php?script_id=3052
> > http://www.vim.org/scripts/script.php?script_id=2712
> > http://www.vim.org/scripts/script.php?script_id=2584
> > http://www.vim.org/scripts/script.php?script_id=1881
> >
> > There are probably even more...
>
> What is the attractiveness of using signs to indicate where changes
> have taken place? When I follow changes, I'm more interested in
> _what_ the changes were, not just that something changed. For this
> I use DiffOrig or a variation that compares the current buffer with
> the latest (or a specified) VCS version. Having a sign in the left
> column doesn't tell me enough to be useful.
I don't know. I made the plugin for fun a couple of years ago after a
similar question here. Personally, I don't see the sense of the
indicators but I can understand, if some people like it.
regards,
Christian
--
Alle Männer vom Fach sind darin sehr übel dran, dass ihnen nicht
erlaubt ist, das Unnütze zu ignorieren.
-- Goethe, Maximen und Reflektionen, Nr. 964
--
--
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/groups/opt_out.
Re: gVim Hanging/Freezing When Closing
Hi Kenny!
On Do, 28 Mär 2013, Kenny Ballou wrote:
> Hey all.
>
> I haven't found anything on this, and it might be relatively new (i.e., new
> kernel/ new vim release); but I am having an issue with gvim hanging when I try
> to close. That is, the gvim window is clearly _trying_ to close (doesn't
> redraw, no longer responds to commands, etc.) but can't, stuck waiting for ...
> something.
>
> Behavior or characteristics I have discovered so far.
>
> * Happens with a file in buffer or without
>
> * Only happens when launched from system launcher (e.g., Alt-F2) or from a
> shell
>
> * Does *not* happen when launched by double-clicking a file in a file manager
>
> - Tested with Dolphin and Krusader
>
> * Frozen gvim windows have wait channel of `futex_`
>
> * Is local to gvim; vim is unaffected
>
> I'm not sure what needs to be done to further debug this and/or fix. This
> happens on both of my main working machines and only started recently (in which
> time I have had a vim update and a kernel update).
>
> Other relevant information (both machines):
>
> * KDE 4.10.1 with Openbox (3.5.0-7) window manager
>
> * See bugreport.txt
>
> Thanks in advance for any help and/or insight anyone can provide.
You might want to strace it or build gvim with debugging symbols and
attach gdb to it and print a backtrace.
Mit freundlichen Grüßen
Christian
--
Alle Stärke liegt innen, nicht außen.
-- Jean Paul (eig. Johann Paul Friedrich Richter)
--
--
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/groups/opt_out.
On Do, 28 Mär 2013, Kenny Ballou wrote:
> Hey all.
>
> I haven't found anything on this, and it might be relatively new (i.e., new
> kernel/ new vim release); but I am having an issue with gvim hanging when I try
> to close. That is, the gvim window is clearly _trying_ to close (doesn't
> redraw, no longer responds to commands, etc.) but can't, stuck waiting for ...
> something.
>
> Behavior or characteristics I have discovered so far.
>
> * Happens with a file in buffer or without
>
> * Only happens when launched from system launcher (e.g., Alt-F2) or from a
> shell
>
> * Does *not* happen when launched by double-clicking a file in a file manager
>
> - Tested with Dolphin and Krusader
>
> * Frozen gvim windows have wait channel of `futex_`
>
> * Is local to gvim; vim is unaffected
>
> I'm not sure what needs to be done to further debug this and/or fix. This
> happens on both of my main working machines and only started recently (in which
> time I have had a vim update and a kernel update).
>
> Other relevant information (both machines):
>
> * KDE 4.10.1 with Openbox (3.5.0-7) window manager
>
> * See bugreport.txt
>
> Thanks in advance for any help and/or insight anyone can provide.
You might want to strace it or build gvim with debugging symbols and
attach gdb to it and print a backtrace.
Mit freundlichen Grüßen
Christian
--
Alle Stärke liegt innen, nicht außen.
-- Jean Paul (eig. Johann Paul Friedrich Richter)
--
--
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/groups/opt_out.
Re: Register overwritten only when clipboard=unnamed
Hi PARK,!
On Do, 28 Mär 2013, PARK, Kyung-Kook wrote:
> I am not sure whether or not this is an obscure side effect which I
> can figure out. But when I set clipboard=unnamed, vip followed by yiw
> does not operate in the way I expected - actually nothing happens. It
> operates as expected I omit clipboard=unnamed from my vimrc. In a
> normal situation, it must yank a word from the current cursor position
> and paste it somewhere I want.
vip followed by yiw does not make sense. Please be more specific.
What exactly did you do, what do you expect and what happens?
Oh, and what Vim version are you using?
regards,
Christian
--
Hallo Birkenstockträger!
--
--
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/groups/opt_out.
On Do, 28 Mär 2013, PARK, Kyung-Kook wrote:
> I am not sure whether or not this is an obscure side effect which I
> can figure out. But when I set clipboard=unnamed, vip followed by yiw
> does not operate in the way I expected - actually nothing happens. It
> operates as expected I omit clipboard=unnamed from my vimrc. In a
> normal situation, it must yank a word from the current cursor position
> and paste it somewhere I want.
vip followed by yiw does not make sense. Please be more specific.
What exactly did you do, what do you expect and what happens?
Oh, and what Vim version are you using?
regards,
Christian
--
Hallo Birkenstockträger!
--
--
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/groups/opt_out.
Subscribe to:
Posts (Atom)