On 21 mar 2013, at 16:55, FlashBurn wrote:
> I have just loaded tcomment plugin, https://github.com/tomtom/tcomment_vim. I
> code in C and need to be able to do line comments ( // ). For some reason
> this plugin does only block comments ( /* ... */). I looked through the
> documentation but w
Hi Ben!
On Do, 21 Mär 2013, Ben Fritz wrote:
> On Thursday, March 21, 2013 8:14:03 AM UTC-5, ping wrote:
> > sorry to bring this old thread back.
> >
> > but looks I just find a new issue (maybe old/known?), this is reproducible:
> >
> > if the 2 buffer in vimdiff haven't been saved to files ye
Hi,
Is there a way of prioritize the listed files by their extension after a
":e"? I mean, like in zsh completion system?
Thanks in advance
Leo
--
--
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 informat
Hi Gary!
On Do, 21 Mär 2013, Gary Johnson wrote:
> > And it didn't work. I also tried normal "", normal! "\",
> > and normal! "". None of them worked. Does anybody have any
> > other ideas?
>
> I think that should have worked.
>
> I grep'd for a pattern, executed ":copen" and tried various
> ":
On 2013-03-21, FlashBurn wrote:
> On Thursday, March 21, 2013 1:24:12 PM UTC-4, Gary Johnson wrote:
> > However, I also skimmed quickfix.txt and found that the command
> > ".cc" should also work, and it worked for me, so try
> >
> > .cc
> >
> > where you now have
> >
> > normal "\"
> G
On Thursday, March 21, 2013 1:24:12 PM UTC-4, Gary Johnson wrote:
> On 2013-03-20, FlashBurn wrote:
>
> > On Tuesday, March 19, 2013 5:54:23 PM UTC-4, Christian Brabandt wrote:
>
>
>
> > > You need 2 commands:
>
> > >
>
> > > :copen
>
> > >
>
> > > :norm! "\"
>
> > >
>
> >
>
> > I tr
On 2013-03-20, FlashBurn wrote:
> On Tuesday, March 19, 2013 5:54:23 PM UTC-4, Christian Brabandt wrote:
> > You need 2 commands:
> >
> > :copen
> >
> > :norm! "\"
> >
>
> I tried the following:
> function! CscopeFind(action, word)
> try
> exe ':cs f '.a:action.' '.a:word
> copen
>
On Thu, Mar 21, 2013 at 8:09 AM, Marc Weber wrote:
> Use github.com/MarcWeber/vim-adddon-commenting which always prefers
> those # // like line prefix comments and you're done.
Typo in link, should be: https://github.com/MarcWeber/vim-addon-commenting
Nice plugin.
c
--
Chris Lott
--
--
You
Use github.com/MarcWeber/vim-adddon-commenting which always prefers
those # // like line prefix comments and you're done.
Otherwise this is not a question for the vim mailinglist, but for
github/tomtom/issues -> improve documentation (I hope you've read that)
This is my "view" - there might be mo
I have just loaded tcomment plugin, https://github.com/tomtom/tcomment_vim. I
code in C and need to be able to do line comments ( // ). For some reason this
plugin does only block comments ( /* ... */). I looked through the
documentation but was not able to find a way to configure the plugin to
On Thursday, March 21, 2013 11:02:08 AM UTC-4, Ben Fritz wrote:
> On Wednesday, March 20, 2013 9:30:11 AM UTC-5, FlashBurn wrote:
> >
> > I found a solution to this problem. All I needed to do is the following:
> >
> >
> >
> > exe 'normal! copen"
> >
> >
>
> This should NOT work. This should
On Thursday, March 21, 2013 8:14:03 AM UTC-5, ping wrote:
> sorry to bring this old thread back.
>
> but looks I just find a new issue (maybe old/known?), this is reproducible:
>
> if the 2 buffer in vimdiff haven't been saved to files yet, the
>
> converted html output are the same one in the
On Wednesday, March 20, 2013 9:30:11 AM UTC-5, FlashBurn wrote:
>
> I found a solution to this problem. All I needed to do is the following:
>
>
>
> exe 'normal! copen"
>
>
This should NOT work. This should beep at you and fail to do anything, because
from normal mode, it will:
c - start
On Thursday, March 21, 2013 2:15:27 AM UTC-5, sheetal wrote:
> Hello All,
>
> I don't konw if this is possible, but i've a text file on which i've applied
> fold cmd using the marks, Now when i send the file to over email, I want to
> keep the fold intact so that the other person viewing the fil
sorry to bring this old thread back.
but looks I just find a new issue (maybe old/known?), this is reproducible:
if the 2 buffer in vimdiff haven't been saved to files yet, the
converted html output are the same one in the 2 panels -- they are just
2 copies of one of the files.
but if I save th
Another one here:
https://github.com/vim-jp/vim
On Thu, Mar 21, 2013 at 5:44 AM, Christian Brabandt wrote:
> Hi skeept!
>
> On Mi, 20 Mär 2013, skeept wrote:
>
>> Hi,
>>
>> I recall someone having a(non-official) copy of the vim sources on github.
>> This is useful for me because I can download t
Hi Tim!
On Do, 21 Mär 2013, Tim Chase wrote:
> On 2013-03-21 00:15, sheetal wrote:
> > I don't konw if this is possible, but i've a text file on which
> > i've applied fold cmd using the marks, Now when i send the file to
> > over email, I want to keep the fold intact so that the other person
> >
On 2013-03-21 00:15, sheetal wrote:
> I don't konw if this is possible, but i've a text file on which
> i've applied fold cmd using the marks, Now when i send the file to
> over email, I want to keep the fold intact so that the other person
> viewing the file should also see the folds, Current beha
Hello All,
I don't konw if this is possible, but i've a text file on which i've applied
fold cmd using the marks, Now when i send the file to over email, I want to
keep the fold intact so that the other person viewing the file should also see
the folds, Current behaviour is the person viewing t
19 matches
Mail list logo
