Charles Campbell, 20.05.2009:
>
> Linda W wrote:
> > I seem to remember using variable tabstops at one point - but it might
> > have been an older (~20-25 years ago), that I used for a while, not sure.
> >
> > I seem to remember being able to something along the lines of
> > : vim:ts=17,34,51,55
Ben Fritz, 27.05.2009:
>
> On May 22, 12:24 pm, Markus Heidelberg
> wrote:
> > Ben Fritz, 22.05.2009:
> > > Why bypass the .bat wrappers?
> >
> > To make vimdiff work when invoked in a shell.
> >
> > > I've never seen any problems with them.
> >
> > I
> > have:http://git.kernel.org/?p=git/git.g
On Wed, May 27, 2009 at 12:17 AM, Mahurshi Akilla wrote:
>
> Under my current linux xterm settings, in vim, shit+insert generally
> helps paste things from the clipboard, whether i am in escape mode or
> insert mode.
>
> However, pressing shift+insert only pastes "" in gvim. Is
> there a way to c
Under my current linux xterm settings, in vim, shit+insert generally
helps paste things from the clipboard, whether i am in escape mode or
insert mode.
However, pressing shift+insert only pastes "" in gvim. Is
there a way to change this behavior and have it actually print the
contents of the cli
On 2009-05-26, smu johnson wrote:
> How do you get rid of the "# files to edit" message that always scatters my
> terminal whenever I do this?
Using the ! after :q or :qa will fix that, too.
Regards,
Gary
--~--~-~--~~~---~--~~
You received this message from th
Hello,
I would like to create a foldexpr that turns this Groovy closure:
def list = {
if (!params.max) params.max = 10
[personList: Person.list(params)]
}
def show = {
blah
blah
blah
}
Into this fold text:
def list = {
def show
Yes, type
:%s/
Then hit the up arrow and cycle through previous patterns.
Also
:%s//dave
Notice no search pattern is specified, this says use the previous search
pattern.
So I do what you do all the time.
/mypattern
:%s//myreplacement/g
HTH,
Dave
Sent from my BlackBerry device on the Roge
You don't needed "copy".
If you wrote
/something
to find what will be changed, just type
:s//change_something
or
:%s//change_something
or else
:%s//change_something/g
Vim will reuse your last search pattern
It's magic!
Alessandro Antonello
2009/5/26 :
>
> Hi there,
> When I substitut
> When I substitute using ":s/{pattern}/{string}/{option}", I prefer to use
> "/{pattern}" to check out
> whether the pattern is satisfactory. After checking, I will run the
> substitute command. However, if
> the pattern string is too complicated, typing it twice is boring. I would
> like to
Hi there,
When I substitute using ":s/{pattern}/{string}/{option}", I prefer to use
"/{pattern}" to check out
whether the pattern is satisfactory. After checking, I will run the
substitute command. However, if
the pattern string is too complicated, typing it twice is boring. I would
like to kn
On May 26, 3:54 am, Hunt Jon wrote:
> Hi I'm new to Vim. I would like to print out some of the documentations,
> which are located in ~/.vim/doc
>
> They are written in the unique format. Is there any good way to
> print out them? Possibly in colorful formats as we read on screen?
>
You have s
On May 22, 12:24 pm, Markus Heidelberg
wrote:
> Ben Fritz, 22.05.2009:
> > Why bypass the .bat wrappers?
>
> To make vimdiff work when invoked in a shell.
>
> > I've never seen any problems with them.
>
> I
> have:http://git.kernel.org/?p=git/git.git;a=commitdiff;h=bad42732008cb0c1e...
>
vimd
I suppose it's time to donate to Uganda in order to vote for this trivial
feature :)
2009/5/26 Tim Chase
>
> > Hello Tim, you are a good man! You solved my problem. Since you knew
> the
> > answer to that, perhaps you could help me with this even easier question:
> >
> > How do you get rid o
On 2009-05-26, smu johnson wrote:
> Hi,
>
> If anyone has known the bliss of vimdiff, I'm sure you realize that probably
> in most cases, you will vimdiff file1 and file2. The problem with that I
> have found, is that when I want to quit after seeing what I need to see, it
> treats the args as s
> Hello Tim, you are a good man! You solved my problem. Since you knew the
> answer to that, perhaps you could help me with this even easier question:
>
> How do you get rid of the "# files to edit" message that always scatters my
> terminal whenever I do this?
I'm not sure this is an easier q
Hello Tim, you are a good man! You solved my problem. Since you knew the
answer to that, perhaps you could help me with this even easier question:
How do you get rid of the "# files to edit" message that always scatters my
terminal whenever I do this?
Many thanks in advance!
2009/5/26 Tim Chas
The bug has been fixed in a recentish Vim patch--you can now explicitly enable
ff=dos when opening a file, and Vim will obey you.
:e ++ff=dos
I believe in this case Vim will treat CRLF and LF as line breaks, i.e. it will
silently convert single LF into CRLF. Single CR will show up as ^M in the
> If anyone has known the bliss of vimdiff, I'm sure you realize that probably
> in most cases, you will vimdiff file1 and file2. The problem with that I
> have found, is that when I want to quit after seeing what I need to see, it
> treats the args as still a list of files "to edit", so I have t
Hi,
If anyone has known the bliss of vimdiff, I'm sure you realize that probably
in most cases, you will vimdiff file1 and file2. The problem with that I
have found, is that when I want to quit after seeing what I need to see, it
treats the args as still a list of files "to edit", so I have to qu
> back to the window and it is there. If it just appears, when I return
> or if it was there a while? I can't tell. I wonder, if there is a way
> to log a keystrokes received by vim?
Not an elegant way, but I found that you can read the swp file with vim
from another window. It will show inserte
Dear all,
a small question: when searching for a pattern, after reaching the
bottom of the file one gets the message "search hit BOTTOM, continuing
at TOP" (same after hitting TOP). Is it possible to get also a beep,
together with the message?
Thank you,
Marco
--~--~-~--~~-
You will have more success if you post your question to the Vim-LaTeX list.
vim-latex-de...@lists.sourceforge.net
To support the old eqnarray environment, Vim-LaTeX will replace every
"==" with a "&=&". Are you sure you're not accidentally hitting "="
twice when you only mean to hit it once?
Where is simple: At the current cursor position
When not so simple any more: It just happens from time to time. I got
back to the window and it is there. If it just appears, when I return
or if it was there a while? I can't tell. I wonder, if there is a way
to log a keystrokes received by vim?
Th
On Tue, May 26, 2009 at 12:37 PM, Tim Chase wrote:
>
>> I think the culprit is
>>
>> C:\Programmi\Vim\vimfiles\after\ftplugin\help.vim
>>
>> which contains the line
>>
>> wincmd o
>
> wow. Yeah, that would do it. I'm not sure what was desired when
> creating this, but it looks like some add-on f
> I think the culprit is
>
> C:\Programmi\Vim\vimfiles\after\ftplugin\help.vim
>
> which contains the line
>
> wincmd o
wow. Yeah, that would do it. I'm not sure what was desired when
creating this, but it looks like some add-on filetype rather than
one that comes with the stock build of V
Tim Chase wrote:
>> If I'm editing a file and then press , I get the help page
>> and when I come back to my editing page, it is saved and
>> without the possibility to undo what I've already written. If
>> I press u, it says "Already at oldest change". Is there the
>> possibility to undo an editi
>-Original Message-
>From: vim_use@googlegroups.com [mailto:vim_...@googlegroups.com] On Behalf Of
>Andy Wokula
>Sent: Tuesday, May 26, 2009 8:41 AM
>To: vim_use@googlegroups.com
>Subject: Re: Highlight Everything But a Specific Pattern
>
>
>Waters, Bill schrieb:
>> I see discussions rela
>Thanks for your info. I've wanted to like to read particular files
>such as NERDTree and rails.vim
When editing a normal file an I'd just hit file->print, it does so in
the selected colorscheme. When you're in the help window, why not try
that? (I haven't, but it's a suggestion anyway.)
--~--
>Vim inserts strange characters into the file from time to time.
>This is either a =, == or &=&.
>It there a way to track down, what/who inserts them?
*Where* and *when* does it insert them? You accidentally hitting a
key-combo that triggers a (re)mapping or something?
--~--~-~--~~-
On Mon, May 25, 2009 at 11:32 AM, Simon Ruderich wrote:
>> Matt your are probably right, but how can i see which plugin
>> mapped the ?
>>
>> -nicolas
>
> :verbose map!
>
> Simon
thank you Simon, for your tip!
after some research it seems like the problem isn't caused by a bad
mapping but by pl
Bit of a weird issue that I am hoping someone can provide some
direction to research what has changed so I can fix it.
WinXP SP3
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Mar 28 2009 22:11:15)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-148
If I use any command to open
On Tue, May 26, 2009 at 05:54:14PM +0900, Hunt Jon wrote:
>
> Hi I'm new to Vim. I would like to print out some of the documentations,
> which are located in ~/.vim/doc
>
> They are written in the unique format. Is there any good way to
> print out them? Possibly in colorful formats as we read o
Did you read Wikipedia's own take on this?
http://en.wikipedia.org/wiki/Wikipedia:Text_editor_support#Vim
Personally, I use Wikipedia.vim (mentioned there) combined with
Vimperator (which has similar features as "It's All Text" but is meant
to be more than just an editor launcher).
Some othe
Waters, Bill schrieb:
> I see discussions related to this, but not exactly what I am looking
> for.
>
> I have a file that is made up of mostly a specific pattern. I want to
> highlight all of the text that is NOT that specific pattern.
>
> I see how to highlight the lines that don't contain the
> If I'm editing a file and then press , I get the help page
> and when I come back to my editing page, it is saved and
> without the possibility to undo what I've already written. If
> I press u, it says "Already at oldest change". Is there the
> possibility to undo an editing file after I've pre
On Tue, May 26, 2009 at 6:20 PM, John Beckett wrote:
>
> Hunt Jon wrote:
>> Hi I'm new to Vim. I would like to print out some of the
>> documentations, which are located in ~/.vim/doc
>
> I hardly ever print stuff so I'll leave that part to someone
> else, but you might like to look at the items
Hunt Jon wrote:
> Hi I'm new to Vim. I would like to print out some of the
> documentations, which are located in ~/.vim/doc
I hardly ever print stuff so I'll leave that part to someone
else, but you might like to look at the items here:
http://vim.wikia.com/wiki/Vim_documentation
John
--~--~-
Hi I'm new to Vim. I would like to print out some of the documentations,
which are located in ~/.vim/doc
They are written in the unique format. Is there any good way to
print out them? Possibly in colorful formats as we read on screen?
Jon
--~--~-~--~~~---~--~~
Y
Hi,
I'm using vim with latex-suite for a while now and a pretty happy with
it.
Unfortunately there is a strange problem.
Vim inserts strange characters into the file from time to time.
This is either a =, == or &=&.
I don't know why? The characters are sometimes there, when I change
the
focus ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, May 26, 2009 at 04:18:16PM +0900, Hunt Jon wrote:
> I would like to use Markdown and found
> http://plasticboy.com/markdown-vim-mode/
>
> I need to have file extensions as ".mdown", ".markdown" and ".md",
> which are supported in
> GitHub a
I would like to use Markdown and found http://plasticboy.com/markdown-vim-mode/
I need to have file extensions as ".mdown", ".markdown" and ".md",
which are supported in
GitHub and TextMate.
Can anybody help me how I can set up the files to be recognized as
Markdown files?
Jon
--~--~-~
41 matches
Mail list logo
