Hi,
I have two """problems""":
1.) Splitting line into two from normal mode.
My current "concept" (hu...great word...;) to split a line into
two is (starting and ending in normal mode, which is wanted):
i Ctrl-j
Ar
Hello,
--- Meino Christian Cramer <[EMAIL PROTECTED]> wrote:
>
> 1.) Splitting line into two from normal mode.
> My current "concept" (hu...great word...;) to split a line into
> two is (starting and ending in normal mode, which is wanted):
>
> i Ctrl-j
>
> A
From: Peter Hodge <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Thu, 14 Sep 2006 13:10:43 +1000 (EST)
> Hello,
>
> --- Meino Christian Cramer <[EMAIL PROTECTED]> wrote:
> >
> > 1.) Splitting line into two from norm
t g:maxd_FontSize= g:maxd_FontSize - 1
endif
exec "set
guifont=".g:maxd_Font.":h".g:maxd_FontSize.":".g:maxd_FontOpts
endfunction
> -Original Message-
> From: Meino Christian Cramer [mailto:[EMAIL PROTECTED]
> Sent: Wedne
On Thu, 2006-09-14 at 04:45:12 +0200, Meino Christian Cramer sent:
>2.) Currently I am reading the ascii version of the vimtips
>file. One thing I would like to change physically (that means:
>The file should be changed that way, not only the visual
>representation...) are the super long lines int
> Do you have more of these multi-solver tips
> for me, Peter ??? :)))
The Vim Book (http://iccf-holland.org/click5.html#oualline) will get you up to
speed quickly on most of Vim's important features, and teach you how to use
some important tools you might miss otherwise. Most complex commands ca
Ciao Peter,
> The Vim Book (http://iccf-holland.org/click5.html#oualline) will get
> you up to speed quickly on most of Vim's important features, and
> teach you how to use some important tools you might miss otherwise.
> Most complex commands can still be reduced down to one or two
> keystrokes,
Pete Johns schrieb:
> " For all lines longer than 72 characters, reformat the
> " paragraph from that line..
> 1,$g/.\{73,}/normal v}gq
or just
:set tw=72 " if set otherwise
:g/./normal gqq
Andy
___
--- Andrea Spadaccini <[EMAIL PROTECTED]> wrote:
>
> Well.. the vim book is for vim 5.7.. Are there any plans to make a new
> version for vim 7.x?
>
> I would buy it if only it was up-to-date! :)
>
Many of Vim's best features were included in 5.7. It is still a great book to
get you from a nov
From: Max Dyckhoff <[EMAIL PROTECTED]>
Subject: RE: Two """problems"""
Date: Wed, 13 Sep 2006 20:30:15 -0700
Hi Max,
thanks a lot for your help ! :)
(sorry for the late reply...)
I am maintaining a source code from someone else
(which left the company
From: Meino Christian Cramer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 14, 2006 7:21 PM
> To: Max Dyckhoff
> Cc: vim@vim.org
> Subject: Re: Two """problems"""
>
> From: Max Dyckhoff <[EMAIL PROTECTED]>
> Subject: RE: Two "&quo
From: Pete Johns <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Thu, 14 Sep 2006 13:46:42 +1000
> On Thu, 2006-09-14 at 04:45:12 +0200, Meino Christian Cramer sent:
> >2.) Currently I am reading the ascii version of the vimtips
> >
On Fri, 2006-09-15 at 04:57:24 +0200, Meino Christian Cramer sent:
>Hi Pete!
>
Hi!
>thank you very much for this "line of code" -- works like a
>charme!
>
Delighted to hear it.
>The only """bad""" thing is: I dont understand completly, how it
>works
>
He he... I'm glad that someone's taken
From: Pete Johns <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Fri, 15 Sep 2006 14:19:22 +1000
Hi Pete !
Thank you for "disassembling" the hex into mnemonics! :O)
One question remains in my head:
if /.\{73,}/ find all lines, for wh
Meino Christian Cramer wrote:
From: Pete Johns <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Fri, 15 Sep 2006 14:19:22 +1000
Hi Pete !
Thank you for "disassembling" the hex into mnemonics! :O)
One question remains in my head:
i
From: "A.J.Mechelynck" <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Fri, 15 Sep 2006 16:54:02 +0200
> Meino Christian Cramer wrote:
> > From: Pete Johns <[EMAIL PROTECTED]>
> > Subject: Re: Two "
From: Pete Johns <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Fri, 15 Sep 2006 14:19:22 +1000
...
Hi Pete,
...please check this with your genious vimly mind... :) <<<-- BIG smiley!
Your initial command set was:
1,$g/.\{73,
Meino Christian Cramer wrote:
From: Pete Johns <[EMAIL PROTECTED]>
Subject: Re: Two """problems"""
Date: Fri, 15 Sep 2006 14:19:22 +1000
...
Hi Pete,
...please check this with your genious vimly mind... :) <<<-- BIG smiley!
Your initial
On Fri, 2006-09-15 at 20:20:58 +0200, A.J.Mechelynck sent:
>You could simply do
>
>:%g/.{73,}/normal gqq
>
>see "help gqq"
>
>This would of course keep the hard line break (if there is one)
>between ...Very Very Very and Very Very Very long line. You
>can't have it both ways.
>
Indeed. The alternat
litting
lines?
Thanks!
Chuck
-Original Message-
From: Peter Hodge [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 8:11 PM
To: Meino Christian Cramer; vim@vim.org
Subject: Re: Two """problems"""
Hello,
--- Meino Christian Cramer <[EMAIL P
I had a discussion with a friend today about how to "split
lines effectively" in gvim. The trick below came up and he
mentioned "yeah but I want something that will work in default
gvim without having to create a binding or macro." I'm
curious why gvim doesn't have a single keystroke that does a
On 2006-11-15, Chuck Mason <[EMAIL PROTECTED]> wrote:
> In gvim you can do i or 0i to join lines. So the need for
> (J) is superfluous. Why is there no antithesis to J for splitting
> lines?
Because In The Beginning was Vi, and Vi viewed Files as consisting
of sequences of Lines, each Line bein
What Gary says is historically true, but I would point out that it was
the fact that deep underneath vi was sitting on ed. Many full-screen
versions of line editors, like teco, suffered from having their wings
tied down close to the lowest assumptions and could not spread them and
soar.
I re
23 matches
Mail list logo
