Bram Moolenaar | 11 Dec 2006 21:57
Picon

The 2007 Vim calendar


Dear Vim users,

The traditional Vim calendar has been updated for 2007!

This is a desktop calendar for 2007, made from one sheet of paper.
After folding, one side contains a useful 12-month calendar.
On the other side there is brief information about ICCF-Holland,
Vim and A-A-P.

	English, A4:     http://www.moolenaar.net/2007_en_a4.pdf
	English, Letter: http://www.moolenaar.net/2007_en_le.pdf
	Dutch, A4:       http://www.moolenaar.net/2007_nl_a4.pdf

Each file is in PDF and about 180 Kbyte.

I'm afraid the problem with scripts on www.vim.org has not been solved
yet.  We are waiting for SourceForge support...

Happy holidays!

--

-- 
It is illegal for anyone to try and stop a child from playfully jumping over
puddles of water.
		[real standing law in California, United States of America]

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///
(Continue reading)

jeffthewookiee | 13 Dec 2006 22:36

Vim Regexes and Mac Newlines


I'm currently working with vi on OS X machines. I'd like to be able to use
its regex support to quickly add newlines and format things nicely. However
when I run something like this command:

:%s/,/,\n/

I end up with output like this:

  CourtDismissedCount3,^ <at> 

Instead of nice newlines, I get ^ <at> 's instead. Is there any way to fix this?
--

-- 
View this message in context: http://www.nabble.com/Vim-Regexes-and-Mac-Newlines-tf2816824.html#a7861848
Sent from the Vim - Mac mailing list archive at Nabble.com.

Bernhard Prümmer | 13 Dec 2006 23:16
Picon
Favicon

Re: Vim Regexes and Mac Newlines


Am 13.12.2006 um 22:36 schrieb jeffthewookiee:

>
> I'm currently working with vi on OS X machines. I'd like to be able  
> to use
> its regex support to quickly add newlines and format things nicely.  
> However
> when I run something like this command:
>
> :%s/,/,\n/
>
> I end up with output like this:
>
>   CourtDismissedCount3,^ <at> 
>
> Instead of nice newlines, I get ^ <at> 's instead. Is there any way to  
> fix this?
> -- 
> View this message in context: http://www.nabble.com/Vim-Regexes-and- 
> Mac-Newlines-tf2816824.html#a7861848
> Sent from the Vim - Mac mailing list archive at Nabble.com.
>

What I do, and what has always worked for me is

	:%s/,/,^V^M/

where ^V and ^M mean Ctrl-V and Ctrl-M.
See
(Continue reading)

Marvin Humphrey | 13 Dec 2006 23:58

Re: Vim Regexes and Mac Newlines

> Am 13.12.2006 um 22:36 schrieb jeffthewookiee:
>
>>
>> I'm currently working with vi on OS X machines. I'd like to be  
>> able to use
>> its regex support to quickly add newlines and format things  
>> nicely. However
>> when I run something like this command:
>>
>> :%s/,/,\n/
>>
>> I end up with output like this:
>>
>>   CourtDismissedCount3,^ <at> 
>>
>> Instead of nice newlines, I get ^ <at> 's instead. Is there any way to  
>> fix this?

What happens if you try this?

:%s/,/,\r/

That works for me on gvim 6.3 for Mac.  Seems wrong, but it puts in  
newlines.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/

(Continue reading)

Chris Eidhof | 19 Dec 2006 08:50
Picon
Gravatar

Edit in Vim plugin

Hey everyone,

one of the reasons why I was considering to switch to TextMate, was  
because of the "Edit in TextMate"-button the TM-users have. They can  
edit the text of any cocoa-text-widget in their favourite editor,  
just with a press of the button. Ofcourse, I've used vim heavily for  
a couple of years, and TM wasn't really a substitute, so I switched  
back to vim.

Is there anyone with enough experience to build something like this?  
I think we need someone with heavy cocoa-experience? I'd love to see  
this feature, and I'm willing to help, but I have no experience with  
either cocoa-hacking or vim-hacking.

Thanks,
-chris

James Hague | 19 Dec 2006 15:17
Picon

Ugly/slow startup

1. When gvim 7 starts, a small, entirely white window appears for a
second or so, then the window is replaced by the larger gvim window.
My gut feeling is that the window should be hidden until after it is
resized.  Anyone try to fix this yet?

2. gvim 7 is noticibly slower to start on my new MacBook than on my
two-year old Windows box.  Anyone else notice this or is it just me?

James

Jussi Hagman | 19 Dec 2006 18:35
Picon

Re: Ugly/slow startup


On 19.12.2006, at 16:17, James Hague wrote:

> 1. When gvim 7 starts, a small, entirely white window appears for a
> second or so, then the window is replaced by the larger gvim window.
> My gut feeling is that the window should be hidden until after it is
> resized.  Anyone try to fix this yet?

Hmm... This is a double sided sword, on one hand it's good to have  
less flicker but on the other it's good to show user that something  
is really happening.

At the moment there are lots of bigger issues with vim on OS X that  
should be solved, unfortunately I don't have the time to do much and  
the same problem seems to be common among the mac vim developers. But  
I'm sure this thing will be investigated later.

> 2. gvim 7 is noticibly slower to start on my new MacBook than on my
> two-year old Windows box.  Anyone else notice this or is it just me?

On my (almost) three year old PowerBook Vim 7 starts in about 3.5  
seconds. (warm startup, it would take somewhat more if it was a cold  
start). I had lots of other things running and my HD is *full*, those  
contribute negatively to the score.

I know that it is quite common that applications start longer under  
OS X than under Windows, I gather there are some issues that make OS  
X a bit slower in that regard. If the thing you are seeing is just  
difference in operating systems or if there are other problems is  
hard to say.
(Continue reading)

Rainer Schmid | 20 Dec 2006 10:02

Re: Edit in Vim plugin

Hi,

> one of the reasons why I was considering to switch to TextMate, was
> because of the "Edit in TextMate"-button the TM-users have. They can
> edit the text of any cocoa-text-widget in their favourite editor,
> just with a press of the button. Ofcourse, I've used vim heavily for
> a couple of years, and TM wasn't really a substitute, so I switched
> back to vim.
>
> Is there anyone with enough experience to build something like this?
> I think we need someone with heavy cocoa-experience? I'd love to see
> this feature, and I'm willing to help, but I have no experience with
> either cocoa-hacking or vim-hacking.

If you google for this TextMate feature, you can actually find the link

http://anon:anon-jlSwmc+ugeV0ubjbjo6WXg <at> public.gmane.org/svn/Bundles/trunk/Tools/Edit%20in%20TextMate/

which is actually the source code for it. I am not sure about the
license of the sources (it doesn't say anything), so I don't know if
one is allowed to simply take it and add vim support for it. But one
can take it at least as an inspiration on how to do it in principal.

Rainer

James Hague | 20 Dec 2006 15:10
Picon

Re: Ugly/slow startup

> How long does it actually take to start? Have you got a long .vimrc
> file?

~3 seconds on a recent MacBook (2GHz).  On my Windows PC, it's ~0.5
seconds.  So it's not slow slow, but not snappy either.  It's the same
158 line .vimrc file on both machines.

> Another thing to check is to make sure you are using Universal binary
> of Vim 7, starting PPC native binaries with Rosetta is much slower
> than running native binaries.

I'm pretty sure I stripped the PPC code after I downloaded it, but
I'll double check.

Jussi Hagman | 20 Dec 2006 16:40
Picon

Re: Ugly/slow startup


On 20.12.2006, at 16:10, James Hague wrote:

>> How long does it actually take to start? Have you got a long .vimrc
>> file?
>
> ~3 seconds on a recent MacBook (2GHz). On my Windows PC, it's ~0.5
> seconds.  So it's not slow slow, but not snappy either.  It's the same
> 158 line .vimrc file on both machines.

I actually redid my test and a warm start (vim already in disk cache)  
it took just 1.6s-2s (with/without 100 line .vimrc), I'm not sure why  
the difference to yesterday, maybe I've changed energy settings or  
have less other programs running.

MacBook being slower than my G4 is surprising. Even given that  
your .vimrc is longer than mine I was expecting the start time to be  
much faster on Intel. I'm probably going to look at it as soon as I  
get my hands on an Intel Mac, unfortunately that will take some time :(

In the mean time you could try to check if an empty .vimrc file makes  
any significant difference. If it does there's some OS X specific  
speed problems with the startup and we could look into that. If not  
it's some bigger thing :(

Vim uses some older APIs that could (in theory) make even startup  
slower on Intel machines but that's just another guess.

> I'm pretty sure I stripped the PPC code after I downloaded it, but
> I'll double check.
(Continue reading)


Gmane