On 15.08.15 19:47, BPJ wrote:
> I have acquired a tendency to overuse `v` or `V` in cases where it is
> not (strictly) needed. When writing prose I type `vipgq` or somesuch
> and then immediately `v:w` or even `gv:w` on misguided reflex. I'm
> curious what others have done when getting into such ba
On Saturday, August 15, 2015 at 5:36:44 PM UTC-5, ZyX wrote:
> 2015-08-16 1:27 GMT+03:00 Peng Yu :
> > Hi,
> >
> > I have the following modline in a .py file. When I type TAB, two TAB
> > characters are entered into the file. How only let one TAB characters
> > entered? Thanks.
> >
> > # vim: set n
2015-08-16 1:27 GMT+03:00 Peng Yu :
> Hi,
>
> I have the following modline in a .py file. When I type TAB, two TAB
> characters are entered into the file. How only let one TAB characters
> entered? Thanks.
>
> # vim: set noexpandtab tabstop=2:
Default shiftwidth for Python files is 4 (which is &ta
2015-08-16 0:02 GMT+03:00 "Cedric Bhihe (毕生泰)" :
> Is there a way to limit the size of the ~/.viminfo file from within vim ?
> (not manually or with an external script skimming
> I am thinking specifically about limiting the extent to which cmd history
> accrues.
Input history is limited by 'histo
Hi,
I have the following modline in a .py file. When I type TAB, two TAB
characters are entered into the file. How only let one TAB characters
entered? Thanks.
# vim: set noexpandtab tabstop=2:
--
Regards,
Peng
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Typ
Is there a way to limit the size of the ~/.viminfo file from within vim
? (not manually or with an external script skimming
I am thinking specifically about limiting the extent to which cmd
history accrues.
Cheers.
-ced
/GMT+1/
Hello @lcd047:
Thank you for your reply. I gather from it that you have nothing to offer
that could remotely look like an answer to my simple query.
I also think that you may well have misunderstood my message as well as
the purpose of this list. Please stay constructive. Cheers.
-ced
/GMT+1/
Den 13 aug 2015 19:27 skrev "Ben Fritz" :
>
> Today I stumbled on a feature that saved me some headaches. When I
accidentally did :'<,'>w instead of just :w Vim warned me that I was trying
to write a partial file and asked for confirmation.
>
> Awesome! I chose "no" and lost no work at all.
I'm sa
On 13 August 2015, "Cedric Bhihe (毕生泰)"
wrote:
[...]
> *Q-1*: Instead of consulting Syntastic's help within vim (:help
> syntastic) with only 23 lines of scrolling text in terminal is there
> an online html doc I can look at ? (I want to improve on default
> Syntastic settings in my ~/.vimrc file.
Hey again,
i solved it:
if (winheight(0)!=&lines-2)
nnoremap -
endif
(changed j to k, because i mistaken them before)
return the height of the current window and compare it to the height of
the whole vim window (which includes one line for the statusline and one
for the command line,
On 14.08.15 04:02, Oliver Wraight wrote:
> The behaviour I'm after is ludicrously simple:
>
>/*
> Comment block indented
> by shiftwidth
>*/
>
> The behaviour I'm getting is:
>
>/*
> Comment block indented
> by shiftwidth
> */
>
...
> comments=sO:* -,mO:*
On Saturday, August 15, 2015 at 12:42:27 AM UTC-6, Gary Johnson wrote:
> On 2015-08-14, wolfv wrote:
> > I am using vim 7.4 with
> > markdown heading folding from https://gist.github.com/vim-voom/1035030
> > and highlighting from /usr/share/vim/vim74/syntax/markdown.vim
> >
> > With this setup, fo
12 matches
Mail list logo
