Re: h j k l -- keys

[Phil Dobbin]

On 16/12/11 13:42, "Sven Guckes"  wrote:

> "you will be assimilated.  resistance is futile."  hehe

I just commit the ultimate heresy & use the arrow keys. Lead him away ;-)

Cheers,

Phil...

-- 
Nothing to see here... move along, move along

-- 
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 information, visit http://www.vim.org/maillist.php

Odd problem...

[Phil Dobbin]

Hi.

This is a real shot in the dark but here goes...

I had a build fail on me. This is the relevant part of the log:

`#   Failed test 'right path detected'
350 #   at t/mojo/home.t line 17.
351 # Structures begin differing at:
352 #  $got->[1] = 'users'
353 # $expected->[1] = 'Users'
354 
355 #   Failed test 'right path detected'
356 #   at t/mojo/home.t line 33.
357 # Structures begin differing at:
358 #  $got->[1] = 'users'
359 # $expected->[1] = 'Users'
360 # Looks like you failed 2 tests of 16.`

My pwd at the prompt is '/Users/dobbin/' & after checking all relevant RC
files there was nothing amiss. However when reading the log for nth time in
vim I noticed the if I issued `:pwd` it returned `/users/dobbin'.

I started vim with -u NONE & all was OK so I don't think vim has anything to
do with it (it still returned `/users/dobbin` when asked as does mvim) but
maybe there's a clue in there somewhere as to why this is happening which
for the life of me I can't see.

Any help appreciated.

Cheers,

Phil.

-- 
Nothing to see here... move along, move along

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Odd problem...

[Phil Dobbin]

On 7/1/12 05:18, "Phil Dobbin"  wrote:

> This is a real shot in the dark but here goes...

[...]

FWIW, the answer was that the box I encountered the error on was formatted
HFS+ therefore case-insentitive & that's the reason it failed. It built OK
on Linux.

Sorry for the noise,

Cheers,

Phil...

-- 
Nothing to see here... move along, move along

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Hel with vim-addon-manager -a

[Phil Dobbin]

On 8/1/12 18:10, "Eric Weir"  wrote:

[...]

> I believe I have git in PATH, but I'm not certain. How do I check?

`$ which git`

If you don't get an answer, it's not in your $PATH

Cheers,

Phil...

-- 
Nothing to see here... move along, move along

-- 
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 information, visit http://www.vim.org/maillist.php

Re: What's your favorite color scheme?

[Phil Dobbin]

On 10/1/12 09:01, "ConcreteVitamin"  wrote:

> Please share your the name of your favorite color scheme, your working
> environment (gvim under windows 7/ubuntu terminal... etc), and any other
> specific settings! It would be best if you share a link to snapshots.

solarized. I use it for gnome-terminal in Linux as well as vim/gvim &
sometimes OS X too though on that platform the Textmate-like theme Twilight
renders better.



Cheers,

Phil...

-- 
Nothing to see here... move along, move along

-- 
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 information, visit http://www.vim.org/maillist.php

Re: What's your favorite color scheme?

[Phil Dobbin]

On 11/1/12 11:04, "Charlie Kester"  wrote:

> On 01/10/2012 11:02 AM, Boyko Bantchev wrote:
>> 
>> 1. I strongly believe that, in general, a dark background
>> reduces the eye strain.
> 
> When they get older, many people (myself included) find it more
> difficult to read light text on a dark background.  I don't know if it's
> eye strain, or if it's an inability to make out certain shapes.
> All I know is that I find a light background less tiring.
> 
> There doesn't seem to be any settled science on this topic, and
> therefore there is room for disagreement.  Vim allows its users to use
> whatever colorscheme they like, and that's something we should all
> appreciate.
> 
> I only wish web page designers were as accommodating.

Having passed the half century myself & having to use reading glasses, I
really struggle with a light background. My eyes have always been
over-sensitive to light though (I wear sunglasses outdoors year round) so
maybe that's it...

Cheers,

Phil...

-- 
Nothing to see here... move along, move along

-- 
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 information, visit http://www.vim.org/maillist.php

Re: What did I do?

[Phil Dobbin]

On 16/1/12 18:04, "Eric Weir"  wrote:

[...]
 
> Again, thanks to all. Perhaps the beginning of another stage in my vim
> education.

Be warned. I've lost days of life reading vim's documentation. Habit
forming... ;-)

Cheers,

Phil.

-- 
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
   -Larry Wall

-- 
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 information, visit http://www.vim.org/maillist.php

Re: What did I do?

[Phil Dobbin]

On 16/1/12 23:28, "Eric Weir"  wrote:

>> On Jan 16, 2012, at 1:37 PM, Phil Dobbin wrote:
 
>> Be warned. I've lost days of life reading vim's documentation. Habit
>> forming... ;-)
> 
> As a novice, and nonprogrammer, I find it hard to get help from the help. I
> try. The elementary stuff I can take in. But must of it, as I and others have
> said previously, seems written for those who already know how to do whatever
> it is the documentation might "help" them with. When I can't get help from the
> help I turn to the FAQs--or ask here. It's always a lot more helpful--really!

I first started reading the documentation in a web browser & found it very
hard going. Page after page of uniform black text on a white background that
was very thorough indeed.

So I started to search the Internet for people's hints, tips, vimrc's, etc &
then read most of the online vim wiki before finally settling upon calling
specific parts of the documentation when needed & slowly started to
understand the way it was written. This mailing list is an invaluable
resource of very helpful people who are very patient & friendly to newcomers
(some other lists are the exact opposite I'm afraid to say. Not vim related
ones however) so in time it's all starting to drop into place.

Happy vimming :-)

Cheers,

Phil...

-- 
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
   -Larry Wall

-- 
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 information, visit http://www.vim.org/maillist.php

Re: What did I do?

[Phil Dobbin]

On 17/1/12 03:04, "Vlad Irnov"  wrote:

> It's easy to make such mistake if selected text in Visual mode does
> not stand out and looks similar to Folded lines. Then you may not
> notice that you are in Visual mode. This is unfortunately a problem
> with many Vim color schemes, including the default one for GUI. They
> use the same or similar background color for selected text (Visual),
> folded lines (Folded), and current line/column (CursorLine,
> CursorColumn) highlight groups. I recommend setting background color
> for Visual selection to some bright, garish color that is different
> from all other highlightings. Something like CadetBlue2 or cyan. Then
> you will always know when you are in Visual mode. If you use default
> GUI colorscheme, try putting this in your .vimrc:
> hi Visual gui=NONE guifg=NONE guibg=CadetBlue2

The plugin Powerline  is
invaluable for identifying which mode you're in along with being able to
tell easily if a file's been modified & plenty of other Good Stuff.

As its name suggests it replaces & pimps your statusline.

Cheers,

Phil...

-- 
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
   -Larry Wall

-- 
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 information, visit http://www.vim.org/maillist.php

Re: What did I do?

[Phil Dobbin]

On 18/1/12 16:52, "Eric Weir"  wrote:
 
> >On Jan 17, 2012, at 4:19 AM, Phil Dobbin wrote:
>>
>> The plugin Powerline <https://github.com/Lokaltog/vim-powerline> is
>> invaluable for identifying which mode you're in along with being able to
>> tell easily if a file's been modified & plenty of other Good Stuff.
> 
> I'm intrigued by this, Phil. The documentation recommends installing by
> pathogen or vundle. I'm assuming vim-addon-manager will do as good a job. In
> any case, it's what I would use. A little concerned at the requirement of use
> of a "fontpatcher and "patched font." Might be more than I want to get into.

Hi, Eric.

I've never used vim-addon-manager but from a previous post to the list
tonight on a similar subject it looks pretty much as if pathogen/vundle are
based on its concept.

Here's the relevant extract of the said post:

`Its Giacomo task to add that name to his .vimrc. Then he is done. It
then looks like this:

  call vam#ActivateAddons(['gituhb:yourname/repo-name'])`

As for the font, I've installed Powerline on OS X & Debian & have had no ill
effects from it on either. I used pathogen to install all three times & it
created the relevant folders for the font & all that was necessary so thumbs
up from me.

Cheers,

Phil...

-- 
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
   -Larry Wall

-- 
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 information, visit http://www.vim.org/maillist.php

Caught deadly signal

[Phil Dobbin]

Hi, all.

For the first time since I seriously started using Vim about six months ago
I got this message on startup:

`Vim: Caught deadly signal ABRT Vim: Finished. Abort trap`

I'd been using it all day & had just come back to it. This version of Vim
(7.3 Included patches: 1-244, 246-353) is on OS X & I compiled it myself
back in December & has worked fine. I subsequently got it back working by
removing the FuzzyFinder plugin which I had recollections of reading about
being troublesome some while ago but had since been fixed so whether this
was a lucky guess or not I'm not sure. As an aside MacVim on the same
machine worked fine when the terminal one wasn't working.

Seeing as this is first problem I've had in this respect, can anyone advise
on the best way to troubleshoot this kind of occurrence? I've Googled on it
but nothing much came up. I've also got a copy of the crash log if that's
any help to anybody.

Any help appreciated,

Cheers,

Phil...

-- 
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
   -Larry Wall

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Caught deadly signal

[Phil Dobbin]

On 19/1/12 15:59, "Charles Campbell"  wrote:

> Phil Dobbin wrote:
>> Hi, all.
>> 
>> For the first time since I seriously started using Vim about six months ago
>> I got this message on startup:
>> 
>> `Vim: Caught deadly signal ABRT Vim: Finished. Abort trap`
>> 
>> I'd been using it all day&  had just come back to it. This version of Vim
>> (7.3 Included patches: 1-244, 246-353) is on OS X&  I compiled it myself
>> back in December&  has worked fine. I subsequently got it back working by
>> removing the FuzzyFinder plugin which I had recollections of reading about
>> being troublesome some while ago but had since been fixed so whether this
>> was a lucky guess or not I'm not sure. As an aside MacVim on the same
>> machine worked fine when the terminal one wasn't working.
>> 
>> Seeing as this is first problem I've had in this respect, can anyone advise
>> on the best way to troubleshoot this kind of occurrence? I've Googled on it
>> but nothing much came up. I've also got a copy of the crash log if that's
>> any help to anybody.
>>
> * try to get a reproducible example; preferably with  vim -u NONE  .
> Barring that, try to isolate to a minimal .vimrc and minimal qty of plugins.
> * I'm not familiar with OS-X; under linux, I'd advise compiling with -g
> and getting a core dump.  Find out where the crash occurred (file, line
> number), and values of pertinent variables
> * see if valgrind helps

Hi, Chip.

Thanks for the reply.

The relevant part of the crash log as far as I can see is:

`Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x, 0x
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib 0x7fff891000b6 __kill + 10
1   vim   0x0001000df604 0x1 +
914948
2   libSystem.B.dylib 0x7fff891121ba _sigtramp + 26
3   libSystem.B.dylib 0x7fff891000b6 __kill + 10
4   libSystem.B.dylib 0x7fff891a09f6 abort + 83
5   libSystem.B.dylib 0x7fff890b8195 free + 128
6   dyld  0x7fff5fc06d5f`

Going on what I could glean from that & what I read at:

<http://www.gnu.org/s/libc/manual/html_node/Program-Error-Signals.html>

is that Vim aborted before it crashed on launch. Starting Vim -u NONE it
functioned as normal & upon removing a couple of plugins it reverted to
normal.

Modifying `libSystem.B.dylib 0x7fff891000b6 __kill + 10` to make it a
viable search term in Google/Stack Overflow turns up scores of entries of
crashes across several different applications on OS X Snow Leopard (which is
the OS this particular version of Vim of mine crashed on) so it may seem
reasonable to  conjecture that this problem is OS specific. The odd thing
however, is that the gui version MacVim functioned normally the whole time
with the same plugins & vimrc.

Cheers,

Phil...

-- 
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
   -Larry Wall

-- 
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 information, visit http://www.vim.org/maillist.php

Re: "save as" from toolbar with MacVim

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 24/01/2012 10:04, eNG1Ne wrote:
> OK, normally I'd use :sav – but when I want to save from hard drive to
> USB stick, and as an occasional Mac user, I'm a long way from sure
> about how to navigate.
> 
> So, I go to the cuddly, friendly toolbar and select Save as from the
> menu. Nothing happens, except that MacVim stops responding. Am I doing
> something wrong? is this known behaviour? is there a workaround?
> 
> Thanks in advance for any tips.
> 


I can't reproduce your problem with Save As in MacVim's menu using
MacVim 7.3 (snapshot 63) on OS X 10.6.8.

Maybe some details i.e. run:version in MacVim & which version of OS X
you're running may start to help to fix the problem.

Cheers,

   Phil...

- -- 
This is the most entertaining bug report I have ever read...
and it actually DOES work. Where's the catch?! You must be insane...
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPHqLAAAoJEKpMeDHWT5ADvikIALMeFQV9ffKpuLyCqZEoIdgJ
k3/BwI85iQGqD5rr+SqXrZ1Crpv/8RUbmc8GzKDOOwPcJfyG4I6C5397DNYLLloN
f2CguBDTqGQt7yfo1vjsnUpTrMQnYWxuOBqdXCPjBt5FBbqnK67BQvTMYS+Gf4kg
o+pggj9D2qEtdGRYU/rZ0e8VE92yairMnI5/BsiHIYKOh8Lqv9enm9soIgT6Li5O
+m7XFYNSUUxpD4523ya30lTuBnRJg34/kZ2Dn8sj8thN07a8Eng1Bap+e4EoaFul
zvwn0mBzT6Yc+lsQPzv7TgU4uTbB5VWhfmZAZZJ4V86w+qVAT7yAh8NDqzwl1vM=
=mGIP
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Strange highlighting

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

I'm seeing a very odd & annoying highlighting anomaly.

In certain files (& on occasion all files) certain words will be
highlighted in only orange & grey. These words seem to be totally
arbitrary. For example, in, say, my .bashrc the words `usr`, `dropbox` &
`storage1` will suffer. Or some single characters like on my PS1 entry
just the `d` `u` & `h` but not the `t` or `w`.

This only happens on terminal vim on Linux & doesn't occur in gvim on
Linux or terminal vim/MacVim on OS X.

I suspect it may have something to do with Gnome Terminal (it happens in
xterm & terminator too). The problem disappears when vim is started -u
NONE. My vimrc is identical on all my machines (Debian Linux & Mac OS X).

Any thoughts or suggestions appreciated.

Cheers,

   Phil...

- -- 
This is the most entertaining bug report I have ever read...
and it actually DOES work. Where's the catch?! You must be insane...
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIFREAAoJEKpMeDHWT5ADiJYH/iKLp8moCJ2zaAi2Jhf08ZzZ
LrhSROopD4qWKb6sAZSv990Y4IsM+gZb8bh9TDPtGQmGArcyT6yG/VzOpIC0AMeY
whXXh0qkeU81x3GSRO4AyUrDZISwi3M0QdIicgq9q2ngDBQVo70QlXUKz6HuUQnY
wFnVLf3wY6yTv4t68tTFyfzPcAjTKoWJYbhFuBO/8R6TTiwJ/PhVod7SHcBueRJo
XJs6D3UxkfwbWQKkAEYeNoiWY8PXfKw77xcdGqkRf7XQm2GFeWDNF4hZCNwTuoEv
qsCDR6MSxBWrOWWr1lP/0ZbCS5k+YfZXEzki/CddkuVfimIoD644l6gFw/ZRs3I=
=W1tx
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Strange highlighting

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25/01/2012 19:13, Phil Dobbin wrote:

> I'm seeing a very odd & annoying highlighting anomaly.
> 
> In certain files (& on occasion all files) certain words will be 
> highlighted in only orange & grey. These words seem to be totally 
> arbitrary. For example, in, say, my .bashrc the words `usr`,
> `dropbox` & `storage1` will suffer. Or some single characters like
> on my PS1 entry just the `d` `u` & `h` but not the `t` or `w`.
> 
> This only happens on terminal vim on Linux & doesn't occur in gvim
> on Linux or terminal vim/MacVim on OS X.
> 
> I suspect it may have something to do with Gnome Terminal (it
> happens in xterm & terminator too). The problem disappears when vim
> is started -u NONE. My vimrc is identical on all my machines
> (Debian Linux & Mac OS X).




As a follow up to this I've discovered the odd highlighting only
occurs when passing an argument to Vim i.e `vim .bashrc`

If I start Vim & then edit the same file all is OK.

Cheers,

   Phil...

- -- 
This is the most entertaining bug report I have ever read...
and it actually DOES work. Where's the catch?! You must be insane...
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIGVhAAoJEKpMeDHWT5ADtaQH/2ydZSM4PhVlcr4CJBt53VXw
Y8PFhlJNd7n6FqcFdmXhpa2gLjQBDQWYbqIAcrUN79adDNqw49v/lQ+KGTmNquzc
9GySK0AaQDzfGH3t5OK0nydAIx1VuNFn3vcmqH/8dGh5ibQDV3CaTBpAr5VkXLz2
oJm3MO//bleIzzlJkThtNlAR7h6Is6KNc/Y+Z223VAc5ASy3QTrnJTdXgyzIRPQ/
3UWdNWYhBThv+ifyTUB6JnuB2nXbx1DRa8ejBz793Y0ra7kJeg1jHmQiGLOKtqtw
bn2QuYOMJMCWVR70oIyOhGGj4f2JSm4oMil2imlwKYkV7iO8jUGnNgj8dqSq7e0=
=m34g
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Strange highlighting

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25/01/2012 21:41, Charles Campbell wrote:
> Phil Dobbin wrote:

[...]

>> As a follow up to this I've discovered the odd highlighting only
>> occurs when passing an argument to Vim i.e `vim .bashrc`
>>
>> If I start Vim&  then edit the same file all is OK.
>>


> Well, I was thinking that perhaps your termtype database was incorrect,
> but that should affect :e .bashrc, too.
> 
> So, what's the filetype?
> 
>   vim .bashrc
>   :echo &ft
> 
> Do files other than shell script files appear odd?
> 
> Does
> 
>   vim -u NONE .bashrc
>   :set nocp
>   :syn on
> 
> have odd highlighting?




Running the first instance the filetype returns `sh`.

In the second there's no odd highlighting when the commands are run.

The odd highlighting also occurs in text files, python & perl scripts.
It doesn't happen in helpfiles but I guess that's because Vim's already
running.

Cheers,

  Phil...


- -- 
This is the most entertaining bug report I have ever read...
and it actually DOES work. Where's the catch?! You must be insane...
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIHo0AAoJEKpMeDHWT5ADs3UIAIip6YKhBn3CkO4+Z1gEjWU3
b0cIjQbMZ+l5CDwvdDDlpCiVflRq/09CflY6g0mQVzs1o2vNJMAimikCsOnwOu4o
+4YjiEFWSn4EKmqmtJq3M8xymROe9NOocwBsig8s2fE1SxTHlEL25JydUsoL4oz4
4/PSFeZQXTqfHTr6GG2/IHc2JT35iWaKD4fsqPb4Sp4ZBzggwyT/Lnseq+8ISs/V
AocIH21qH3aUOrfBviUH3NNIS3MiYXRm2072LtH4rfRlxJcH3pgYS4RwRNX8J5Xp
wAPHCBgx5OLqsmzo8j5OKZDeGBUcOo2/z99qT2A7ELYtAeSOV+E8JlJFV4j4s88=
=qTGq
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Strange highlighting

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 26/01/2012 01:44, Charles E Campbell Jr wrote:
> Phil Dobbin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 25/01/2012 21:41, Charles Campbell wrote:
>>   
>>> Phil Dobbin wrote:
>>>  
>> [...]
>>
>>   
>>>> As a follow up to this I've discovered the odd highlighting only
>>>> occurs when passing an argument to Vim i.e `vim .bashrc`
>>>>
>>>> If I start Vim&   then edit the same file all is OK.
>>>>
>>>>
>>
>>   
>>> Well, I was thinking that perhaps your termtype database was incorrect,
>>> but that should affect :e .bashrc, too.
>>>
>>> So, what's the filetype?
>>>
>>>vim .bashrc
>>>:echo&ft
>>>
>>> Do files other than shell script files appear odd?
>>>
>>> Does
>>>
>>>vim -u NONE .bashrc
>>>:set nocp
>>>:syn on
>>>
>>> have odd highlighting?
>>>  
>>
>>
>>
>> Running the first instance the filetype returns `sh`.
>>
>> In the second there's no odd highlighting when the commands are run.
>>
> I'm afraid that I'm not certain what you're saying here -- does the
> third question, with "vim -u NONE .bashrc", have no odd highlighting?
> In that case, it seems likely that you've got a plugin problem or
> something odd with your .vimrc.  Would you care to post your .vimrc?
> If its a plugin problem, may I suggest that you
> 
>   cd .vim
>   mv plugin PLUGIN
>   mv ftplugin FTPLUGIN
> and then move files, one at a time, from PLUGIN (or FTPLUGIN) to their
> corresponding lowercase directory and try  "vim .bashrc", looking for
> odd highlighting.  When it occurs, you'll at least know which
> plugin/ftplugin is involved.
>> The odd highlighting also occurs in text files, python&  perl scripts.
>> It doesn't happen in helpfiles but I guess that's because Vim's already
>> running.



Sorry for the confusion. When using Vim -u NONE .bashrc there is no odd
highlighting.

I've moved the directories as suggested but there seems to be a conflict
somewhere between the two which makes for spotting the culprit somewhat
problematical.

As luck would have it, I'm setting up a new VPS today so this will an
ideal opportunity as I'm adding the plugins to determine at which point
the problem occurs (the VPS is Debian Linux same as my desktop box where
the problem lies so I should hopefully find out what's causing it).

Cheers,

  Phil...


- -- 
This is the most entertaining bug report I have ever read...
and it actually DOES work. Where's the catch?! You must be insane...
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIUnAAAoJEKpMeDHWT5ADYcIIANfjVMTWQE4HDUyB2ZjZw+1v
5Xk3HJSsexN3IwSTs+ynQAzG+la3X47sx4JnDio9Ssqx/UVww2oqmU8TC4k+Crkv
nEz4FbaWFVYUM2dKrC6wDkK2dpRlQeVqCw+Gj/uWK/QN6CJHPMWuVffgTsrpJd1I
Dv0WvzcjZIiVa2nLmDynhIQX6Mr8zH49eW39LjsDjADVPaVn6QdVZ+5V7pi/Kuvx
XUnRiMk9pmr0CthkeLgFyDIaGi6ceRR1loq9Rvax7r2UG3fIXYZXsExngl8kdmkW
0oKT9gpPiEtLD5ZD3awytByIZnURCI/no1NUsgPO7+iHEEK+nLvU+EMEhpQFo5Q=
=0JZt
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

new version of Vim?

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

On my OS X box I use a MacPort's version of console Vim & after running
a selfupdate on MacPorts I noticed there's a new version of Vim (7.3.410_0).

I can't seem to find any information about it anywhere at the usual
places & Google drew a blank.

Anybody else seen it?

Cheers,

   Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIyToAAoJEKpMeDHWT5ADWDoIAIh1XzioLE1/oEHkLZS+QXOR
jhrpXzI5EvFfZmqG0w9vUbMdXnHRSV5gBDefy5N1cqUJaiW2fjlSEUuWDxnjjtBA
NQuNSTV6ns1k0nDARD4Qv0fAXeV8ffdZ09v6paqRpc9I+bYSB7sRMVliydwk5f/z
zjuk0at5hgtJqdgKq4x1OFM/6HXWM0BWsaengpxArytR321Ga+F8ugt2X2r7rBm5
Q0dGfT9/TkyIkHkR1Ksh7ZGoaAlg7d92raqJWiLCAlzl6X4WpcWr48s6CwN3m/4d
+v3hYd8e4eMsoqia4t2T7N8q6dZVrGaPlBgPFJ1D934KBCbQqAswaKCG3tqm2Yg=
=2pD2
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: new version of Vim?

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 27/01/2012 23:39, Ben Fritz wrote:

> On Jan 27, 4:27 pm, Phil Dobbin  wrote:
>>
>> Hi, all.
>>
>> On my OS X box I use a MacPort's version of console Vim & after running
>> a selfupdate on MacPorts I noticed there's a new version of Vim (7.3.410_0).
>>
>> I can't seem to find any information about it anywhere at the usual
>> places & Google drew a blank.
>>
>> Anybody else seen it?
>>
> 
> What are you asking? Do you need to know where to get the latest Vim?
> Or just what version 7.3.410 changed from previous releases?
> 
> For the latter, see ftp://ftp.vim.org/pub/vim/patches/7.3/README


Hi, Ben.

Yeah, I just wanted to see the readme. Thanks for that.

Cheers,

   Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIzubAAoJEKpMeDHWT5ADs80IAL9RBnKFGXVWua1oUQk8uHFr
2f6nYbbxl2KZx/79cz8f030paZX5uJsE7lRKs0SNyasctry1cl648MaMJOeP75Ks
/EeZKdqEHhUhNcptyPhB+TH5TdzH4YX8fMz7pABfPFGDIkcuDGtY8wNGa3M5cbVp
13sdfgESGBhoys3y1iqTUn4TPevw1AKj07ufoNNfHzORVqCiqnkNk0FgoTWW0xIt
B40KIBDIX6pm0mukGGVI0QGiHgtO2NmVkl3P44O0kMKhrDtU3rEn/VI+jsXdUs3I
rE7+RMdKsTAj26GN9e8rwDVOL5KL7C01vhBod6o+8pXY5KGhbvqNNf3QrgfgVZM=
=UMlt
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: compiling 7.3+ with the conceal option

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/2012 20:03, Dominique Pellé wrote:

[...]

> I don't think that works. I build Vim (huge) as follows:
> 
> $ cd vim
> $ hg pull
> $ hg up
> $ ./configure --with-features=huge --enable-gui=gnome2
> $ make
> 
> According to ":help +feature-list", the +conceal feature is
> enabled in Vim big (and thus also in Vim huge).


Hi, Dominique.

On which version of Linux do you build Vim like so (I'm speculating as
to it being Linux)?

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: Ā§auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPKwzJAAoJEKpMeDHWT5ADoAkH/j1x6XCpNsmoadS5AjzxzvtS
KyMZvjADsMmT+xOEPkvrtqI+2AbuUXtRXtJCPiXW0fNlYXBm0TEhWH8ZTcffvgv/
PqgknyWgCeG4k3La+R0w6Xlp8aK7p2pq+QgSwb2SPDUG5Dfo3IUy9JVGoMq6t7mQ
rTgvsb+N25JwgRb27rUAqt596AXW/QSw4Qxm4Uh5KyEenZbDsGaox8QoHWbx/+Z+
Q0wKC9aQmQsmjKVOuQXx5F9y7hVeHZfu/fgFrC6+U4alWz9xVv82Qkv8Outbp9+P
4+4E54zUYsvfwfoBjw2skQYeakYWQ84VoUFQS1CopsC+tGVaREZl3ba54stGXHM=
=riQ+
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Vim from Mercurial

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

This isn't strictly a Vim question so I hope you'll forgive & indulge me.

I pull the code for Vim from the Mercurial/Googlecode repos & it works
great on OS X on which I've got installed hg 2.0.1 but trying to pull to
my Debian boxes running hg 1.6.4 I get:

`Abort: destination 'vim' is not empty'

I ran it with --debug --traceback & the errors were mainly centred
around `/usr/lib/pymodules/python2.6/mercurial/dispatch.py`.

Having Googled for half an hour I can't seem to find a solution
(apparently there was a problem of this sort in hg 1.5 but that was
fixed, again apparently, in v.1.6).

This is a Mercurial problem but I wondered if anybody in the community
had faced this before & if so, could they point me towards a solution?

Many thanks,

Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPMYXxAAoJEKpMeDHWT5ADk74H/ic1lI60+IFBVaR3jyHXySyv
ciF222wDHUtmUeQPGzpENAMslpdbN+rk/JOB7nhJZia2jwJo/8Mmx0wFM+DcnZQe
+Oz19CyAKyn1kuXr1OceCBxzlFyaJdKSNsyw2QFdwEylOODHEbGxBc4SsL4VHDbw
erF78yxOOf4wVT2wcVUtFTJ+lZqXzo04aGFXu0mP9JZioyvNUBBElayruhHRCa7p
rh3RAsOD3U6EsSY78MoGHcM+DbBZJHAif0TLhawQyryfkG35nvpwRyoiU6FW4YHA
VriB2MYS2AgHHgXgSfIBdodVf76EAfrS13M1YshypS6xUpveDwBIjFmstceYXb4=
=cMwm
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Vim from Mercurial

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/02/2012 20:13, Phil Dobbin wrote:
> Hi, all.
> 
> This isn't strictly a Vim question so I hope you'll forgive &
> indulge me.


It was just a case of removing hg 1.6 & fetching 2.0.1 from Squeeze
back-ports & now all is well.

Sorry for the noise & hopefully if somebody is scouring the archives
one night, this may help them out ;-).

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPMZvVAAoJEKpMeDHWT5ADMmsIALi+9nz6++l6AtdDAPlyTMk3
bHpDsOEe8qyYO42ek9fqg4fCjL4w9q2FfWM8prQBa4cxd97kgQ2uQmdCuZh+0hzH
I59B8s11ZDOOjZfhOQtRHAxgw9Yvspfsb/5JcnxEFi0elgL8jy0dkt/dygkeNDPK
x5wEZe2f2sa+OKX1hNeWzkr/i6O5DBpYj7pUQ1lgWgOYoIgXfU9xFkc6KQRjBs8m
pixYCuNw6Q/ZfpYitc5dEEize0cwqMkEB6c9QpeQlquXH/Uzlq7O5NxEEmKZiRKw
5/9VdsF9aJVGX8Pu0J/fWMmR6PjZpWdaIx8G0kahN9VOPKsQVQ/tC7X41/lTFt0=
=SvJP
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Vim from Mercurial

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/02/2012 01:49, Rich Healey wrote:
> http://xkcd.com/979/
> 
> Glad you got it sorted :)

lmao ;-)


- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPMzHJAAoJEKpMeDHWT5ADYzQH/jP+bU/3VLWXDppjVz67BlL6
DSNXSoVNsHGJHsULa48m/AF7IVy5M7GLkwL3c3wp9myaz4UdMj6ivdyxOJAnJkWH
IRMmJAYBHkehCvHwW8E+i6u4kYWY8wpjAYXp5DlSkFh5+7ZxXiKZAuPT6KcBatbY
drfK00mzRrO1RQW200Rz0t0bLwSLuWcQw6I+l4wu3RLlXit7gFzlsJaMZlqVCiNG
+ezFbJkxOhsloUAXFAdvbaYREqe3h2IYAFrrPAPI2tpbpfSB64UQ2AxZm45YlNKl
oybmanEwNLlB3Qn7HRz0cnm+9CuCi1Lci5QVhVDj36RjCjh0t95CNDOsAxWyO7U=
=xc8g
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

E365 again

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

I'm setting up a Fedora 12 box & Vim's going well apart from the error
message I'm getting when trying to print - :hardcopy

I've had this before on OS X & Debian & solved it by adding this to my
vimrc:

`set pdev=boring_printer_n...@192.168.1.xx`

& that is the system default printer. I can print from the command line:

`lp print_test`

which prints & returns `request id is printer-2 (1 file(s))

but Vim returns `E365 can't find postscript file`

After Googling around I found this on the subject from Bram back in 2002

"Perhaps it's a matter of ownership.  Vim creates the /tmp/v521333
directory only readable for the user (for security reasons).  If your
print program runs set-user-id with another user it can't read the temp
file".

Could anybody point me in the right direction as to how I can check that
this is/is not the case? Or any other suggestions?

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPPqsTAAoJEKpMeDHWT5ADTPsH/0F/XDWlqtZvcNKHEVboB8UT
tKTg0f5H4lvl/DgptWZDu1p2PZbRUkomaHjh9QNkdUZME/i2OGGyxp6Ufb1Htkmf
eVYxae6DXa9W0yuU1/PWtAYDovPhyoywElKHkmSWkcCKEf1vmZNa3Cblq8isSuCX
LB6WSZdJzw0mL2rCW/zQRO44Y3MxaAcn3j60kfmR3i8e++/XGro6UzD/6buVZG4A
HXOXFvB3Q5l1aHP4Gvd7JFrYInFp0iSS9XHJKSwzWJjoWEqTj3L/oZl/nM6KbGfe
JXuY8wTeuCh8RrQsbbSAv6qpMY3tNfo8Iqqbdk7nO+RDB9+eZPqBf6r8/sRbtVk=
=oPB5
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: E365 again

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 17/02/2012 19:31, Phil Dobbin wrote:


> I'm setting up a Fedora 12 box & Vim's going well apart from the
> error message I'm getting when trying to print - :hardcopy


[snip]

Apologies for replying to own post but the problem was that in the OS
GUI print preferences the printer had defaulted to the name `printer`
when I set it up. Once I corrected my vimrc to reflect this everything
worked OK.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPPrqUAAoJEKpMeDHWT5ADu6IH/047YjOnq4SeSYAA81/BFXtW
VwVv35RmwLhgFDUlwEZY+a3s+mtqfpSkoMTvCnHRzrtwXA2KIdicoR+45/8ziHQS
UwG+f+8IeKeoaeyt5kA+V/3pq9RoLiGV1HAXyT8jEnWU3XZSYla87zGLMIG2tu+3
tmODbL2rkOUJCgMhaK8XZNTmPc+K8kS9T4DEQro1KNlOR1zM3jiPveDoje+rcbUa
b1SNab37rF3lroLDKkueiMeT3SpLZUPZuhtUdr+ld+0K/6cjE4ph3P+tOk9Hv0JE
PNIMblr0zrE1KHzwV9OJ32rwWdKDFovMnQ7ihsHSZWy+ru/n78LV7juxno6AGAY=
=0LHQ
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Vim Script Spam

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 19/02/2012 07:14, John Beckett wrote:
> Marc Weber wrote:
>>> At any rate, I have deleted the following scripts and their
>>> download packages: 1301, 1476, 1670, 1789, 2664.
>>
>> Those other packages - did they contain some strange
>> downloadable content as well?
> 
> The above scripts each had an image (not relevant to Vim) for
> the package download. In a couple of cases, it was obviously a
> good contributor who was frustrated that they could not remove
> an obsolete script. At any rate, none were helpful and it is
> best to remove stuff that is unrelated to Vim as it is
> distracting in searches, and wastes people's time when they
> download it.
> 
> I am confident that none were related to malware or spam.


Although the guy in the jpeg was pretty scary looking ;-)

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPQKRFAAoJEKpMeDHWT5ADJeEH/jIiSKbyHgJJO0txzH1tdMPB
0LHTigQUpg8DD1GMUXplWxwB9ED3iSVlX+zobH24uYamb+PIwCxNrQc0F92rslAP
EOOrKenQgi2mm8EvDEVr8VnP5VbHbZqg9glPXdrlaV5aeBdVfaa6v/w6+0ICG8QC
vi9u/GxGoZDpuMY7risM4A4MoKnlJl0h+9AQX4lR+rO/WS8Q8Of1d91y2SOk/b6m
qGyLxfGjq9lTBwLMoCBNO3smA56dNbcdgJCqaXbMXJFakCa0H0UfZPGOHVRv5UbF
Bga02MuyCvP74BpBrW1InDyXaOfnc17uXaZyU0kiq1LMCMSBHZrtoyl8ZjOtrkA=
=uOpU
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: www.vim.org contents - what about adding a git based wiki everybody can edit?

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21/02/2012 16:27, Marc Weber wrote:


> Excerpts from Ben Fritz's message of Tue Feb 21 16:48:36 +0100 2012:
>> Why not a real wiki with real wiki syntax? Or why not just create
>> pages on the existing wikia.com wiki with prominent links from
>> vim.org? code.google.com also provides a wiki, IIRC. I don't see a
>> need to create something new.
> Because its you who can download it and use it as local resource.
> That in turn could make people contribute little bit more because
> *editing in vim* is that easy :)
> 
> And no, I'm not talking about reinventing the wheel,
> it does already exist:
> 
> solution 1: http://hackage.haskell.org/package/gitit
> solution 2: Vim help file syntax
> solution 3: http://www.vim.org/scripts/script.php?script_id=2226
> 
> Why not mediawiki? Because sending patches requires "logging in"
> Because you can't use Vim for editing (I know that there are plugins
> which come close - but - we just *love* Vim, don't we?)


I personally think that it's a terrific idea, Marc.

As you point out you can fork the repo, apply changes or add commits all
the while using Vim thereby extricating any copy/paste/convert ugliness
& have fun & help the community too.

FWIW, I'm all for it.

Cheers,

  Phil..

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPQ+3PAAoJEKpMeDHWT5ADTvcIAKq8L5Of1qIaoJ0PCE+v3VNY
mxsBMdPGnptLyyaBv3Rqh03VhJvYOSg7b5ipqQ7QeeEXsUKbmNeaB/VCK+UGWP7T
qxTKwlbUTS00XUinSM7701EcoaOYbwfhlWTU+Y5dQdp6MYO4sc2Ad4oQyYjbLUEU
hPD/fyZpkQAZIjtxh5kExtdsXWx9PbYTahUE2pgRkdDyUGj2TzOBszpPJkkWHRs7
It5QhXPuyTizDdutIM7Zjb9aPm97ka31NSI76joPEzX4ezlk6Qy2VQjcjIyBgxOq
QAVVALzPd3EIJk22Gm3uvdNFrikZRgyqovyStbXZ3Q4MfIj55Z3rAkM1Jcp5gLU=
=zJ84
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Strange highlighting [SOLVED]

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25/01/2012 19:13, Phil Dobbin wrote:


> I'm seeing a very odd & annoying highlighting anomaly.
> 
> In certain files (& on occasion all files) certain words will be
> highlighted in only orange & grey. These words seem to be totally
> arbitrary. For example, in, say, my .bashrc the words `usr`, `dropbox` &
> `storage1` will suffer. Or some single characters like on my PS1 entry
> just the `d` `u` & `h` but not the `t` or `w`.
> 
> This only happens on terminal vim on Linux & doesn't occur in gvim on
> Linux or terminal vim/MacVim on OS X.

[snip]

Just a quick follow up to this post in case somebody has the same
problem one day...

After removing plugins,etc, re-creating the same Vim configuration on a
VPS & installing on different OSs, it was down to the fact that these
"strange highlights" were Vim's spell checker on just one machine (face
palm). Didn't spot it because the spell checker thought `autocmd` was OK
but not the `u` in `\u@\h:\w` (it also complained about `etc` only when
it was commented out).

Only reason I found out was due to my habit of practising navigating
through files full of code as if I was going to correct the spelling
misatkes & I actually did hit `zg`.

We live & learn.


Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEbBAEBAgAGBQJPRuxrAAoJEKpMeDHWT5ADfJgH9Rf5ElKU2IAUPbsAHUZ51QYJ
PmvxxzQ7rD3MQdC3hVjyPkp/+hLmmxHJOEG0UtIZDPCZSGtCn8erT5BdSFLGDJOX
pcFBE8wlPBE6NrlUXgU9ETGrOR5hyyog9sc8NAuy2Q5x6oeoGt5ar5TKbtfgOfxa
Dm6HBktmyXyBVnwzon5CDL67LGfYUte6BRKK6eogwHaD5ITE4E+Fzhl1Lc2Uy37J
/tEFFx3BCGzzmogLlx322X6Icy+hlgVg6rKB+mP78FLreroz0gEZsl388UD8LzgT
mf5e0mOA7s+VkEOR2JMXtcx24HRqvj4UQkaxt45xXdcDX6sHPzYdaxHEG+xyqQ==
=tmnb
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

installing/upgrading Vim

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

I've got a version of Vim (see below) which was the first Vim I used. I
compiled it myself from source into /usr/local/ & nowadays the Vim I use
is in /opt/local/ & has very many more features.

Question is I've pulled the latest source code from Mercurial with the
intention of installing that into /usr/local/ & now no longer having the
original source code I can't do a `sudo make uninstall` to clean the
directory.

Which is the better option? Trying to clean the old Vim from /usr/local/
(& if so, what's the best way to do it) or just install over the top?

Many thanks for any help or suggestions (vim --version to be deleted or
over written below)

`$ /usr/local/bin/vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 28 2011 11:11:06)
MacOS X (unix) version
Compiled by dob...@unknown-00-1f-5b-c9-e5-e4.home
Normal version without GUI.  Features included (+) or not (-):
- -arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset
+cindent
- -clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
- -conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con +diff
+digraphs
- -dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi
+file_in_path
+find_in_path +float +folding -footer +fork() -gettext -hangul_input -iconv
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
- -mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse
+mouse_xterm -multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype
+path_extra -perl +persistent_undo +postscript +printer -profile -python
- -python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs
+smartindent
- -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects
+title
 -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra
+viminfo
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset
- -xim -xsmp
 -xterm_clipboard -xterm_save
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
  user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X_UNIX
- -no-cpp-precomp  -g -O2 -D_FORTIFY_SOURCE=1
Linking:
gcc   -L/usr/local/lib -o vim   -lm -lncurses  -framework Cocoa`




-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPUaKWAAoJEKpMeDHWT5ADhgUIAIkpCtG3UgFggaC6BLzpmN0r
c/ZvwN40p+w2H0wWTeH+2CwkzV7osagkWIBla8LsQDkfPr3a38BDM7NBJvn3w360
/mmTYlo6jhFyePzvmsE6k/qGBcvCPVz+B5u7YErk7nSYUa2E2/2tq2KfKFnGSaJz
+P17bH+kLNigbN2hnOLymKyoEPab50IPwsFE/dkGV4LQJ/9IrOC5v2CqxaCaUAS8
ITf2SJ6zeLT7ogxjiaxot1s4PZHbXVXcPYzUbqnpMwR8W3e11piyIAgzYiWs9KtZ
k/cLJKVGgRV72uK38Q1EG41WXkTMte2197nn6vKH8hp+jnvK9tHg6ZBH4jy5h3o=
=y89o
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: installing/upgrading Vim

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/03/2012 09:15, Tony Mechelynck wrote:


> On 03/03/12 05:48, Phil Dobbin wrote:

>> I've got a version of Vim (see below) which was the first Vim I used. I
>> compiled it myself from source into /usr/local/&  nowadays the Vim I use
>> is in /opt/local/&  has very many more features.
>>
>> Question is I've pulled the latest source code from Mercurial with the
>> intention of installing that into /usr/local/&  now no longer having the
>> original source code I can't do a `sudo make uninstall` to clean the
>> directory.
>>
>> Which is the better option? Trying to clean the old Vim from /usr/local/
>> (&  if so, what's the best way to do it) or just install over the top?
> 
> The following will uninstall Vim if you have a standard installation:
> 
> rm -Rvf /usr/local/vim /usr/local/share/vim/vim??
> 
> You may want to do also the following (e.g. by pasting it as a script to
> be run by bash) if you want to remove all traces of Vim executables
> (other than macvim) from your system, but you should NOT do it if you
> plan on reinstalling Vim (immediately or at some later time):
> 
> !#/bin/bash
> test -x /usr/local/bin/vim  && rm -v /usr/local/bin/vim
> test -x /usr/local/bin/gvim && rm -v /usr/local/bin/gvim
> # gvim could also be a softlink to macvim,
> # which we are not removing
> test -x /usr/local/bin/vi -o -L /usr/local/bin/vi \
> && rm -v /usr/local/bin/vi
> test -L /usr/local/bin/ex   && rm -v /usr/local/bin/ex
> test -L /usr/local/bin/exim && rm -v /usr/local/bin/exim
> # exim could also be an email routing program (unrelated to Vim), but
> # in that case it would not be a softlink in /usr/local/bin
> test -L /usr/local/bin/view && rm -v /usr/local/bin/view
> test -L /usr/local/bin/gex  && rm -v /usr/local/bin/gex
> test -L /usr/local/bin/gview&& rm -v /usr/local/bin/gview
> test -L /usr/local/bin/rvim && rm -v /usr/local/bin/fvim
> test -L /usr/local/bin/rview&& rm -v /usr/local/bin/rview
> test -L /usr/local/bin/rgview   && rm -v /usr/local/bin/rgview
> test -L /usr/local/bin/evim && rm -v /usr/local/bin/evim
> test -L /usr/local/bin/eview&& rm -v /usr/local/bin/eview
> test -L /usr/local/bin/vimdiff  && rm -v /usr/local/bin/vimdiff
> test -L /usr/local/bin/gvimdiff && rm -v /usr/local/bin/gvimdiff


Hi, Tony.

Thanks for that. The first rm -Rvf will work in this instance I think.
It was my first stab at Vim & I only built a console version. The
console version I use now has no links to it & is in a completely
different directory & the MacVim I built from source into the Apple
filesystem as per instructions I believe from Bjorn's README.

I'm using msmtp as replacement for sendmail so exim isn't involved but
to be on the safe side I'll run a `find / -name vim 2> /dev/null` to be
on the safe side.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPUf6QAAoJEKpMeDHWT5ADPWMH/3rt17tUQVnXBNndhtX5L4YU
ZBZbQDmhJX/PgqJfZ1er6Tkdw4vmvomb8D9aV4hJAqdcQKrtYdQKzewUWoy+pA/0
zwmvU8+VPaU3upbO9pitmAn1xMXNqihOLj6YBqNmbl4iXCAc5eEQLUA3qy6XLYGz
zO7yvQfnyYy5B+1fWCOOm8B2u4RXBsqkb2t5vc//KwPqwkDu29lK3KFL3fU0HlYB
CnKO0loJEk29F+3xSL8EtlobIVSdqKMCYzLOsEZWeGYGg6Eg66E/pfJ4znWshxGm
dks8OTa6ch7mIl+mC8is7GMc8xkqj0M8+f01xEmcTEgSsBwEE5bdvA3OpbjD4Hw=
=HDpH
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Dr Chip

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/03/2012 20:52, sc wrote:
> On Sat, Mar 03, 2012 at 01:27:10PM -0500, Charles E Campbell Jr wrote:
>> Benjamin R. Haskell wrote:
>>> On Fri, 2 Mar 2012, Kartik Agaram wrote:
>>>
 Holy crap, I just realized that Dr Chip's vim page is gone.

 http://mysite.verizon.net/astronaut/vim
 http://drchip.0sites.net/astronaut/vim

 Has anyone else noticed this? Is it moved somewhere new?
>>>
>>> Dr. Chip (Charles Campbell) posted on this list about the
>>> situation back in August:
>>>
>>> https://groups.google.com/d/topic/vim_use/OKue3zK9p3s/discussion
>>>
>>> There wasn't a resolution on-list, but I'm sure the site hasn't
>>> just vanished entirely.
>>>
>> Its a "new situation" -- I'd moved the website to drchip.0sites.net
>> -- but the new website host has apparently decided to fold.  There
>> was no warning that the website was going down, although some ftp
>> access to grab stuff is still present for a couple of weeks.  The
>> website as hosted is really a mirror, anyway, of what I have on my
>> own computer.
> 
>> So, I'm (again) in a process of finding a new webhost.
>> Unfortunately,  unlike before, I won't be able to put in redirects
>> (well, I suppose I could, but they wouldn't be allowed to work).
> 
> have you checked out github?  if you put an index.html there
> it'll be visible to the world -- i have yet to see a downside to
> using it -- it's where i moved when my isp stopped web hosting
> 
> ( http://toothpik.github.com ) -- layman's html but i had
> fun creating it
> 
> dang i just looked and i have lots of stuff out of date there --
> i better do some updates...


Or alternatively there are good deals to be had with a VPS nowadays if
you want complete root access to a box (configure your own mail server &
so forth) at realistically nearly the same price as shared hosting. I
personally use 6sync & find them great. I do not have any affiliation
with them or benefit from any referral to them either... just so you
know ;-)

Cheers,

  Phil.

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPUrnKAAoJEKpMeDHWT5ADp64H/1w+3zkNbhEh/cHSgzW85wa9
EmJVLKqpsBeKvWbGsIiyUXecKcL5xSdVKn2oq3aSGTLy59lJEpwa6svQGFaUxXlX
GyYSLUMiW3UMeHqc8U6yBnvus9/58jbPkcnSTpG3g/crhqexS8ibh3TWHewl1ZtY
aaQwySdrQXrtU4MYLcRzig0ns1LDHmavYqCk8sIsKJmB8dolVpPeSbaISuweJ59N
KTsm9SXsqrczLHkw+Qw4jojspQJVgqr3zqFlJjECG9B1XpGr5arVPuPrQO4U4TX2
aO8q7XcosY6GIujEQfM0D8rTKbGWlqI53nnMTzBmhdu2hMMAdM4WKDQOedoWU0k=
=vVSb
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: OT: hosting (was Re: Dr Chip)

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04/03/2012 01:04, Tim Chase wrote:
> On 03/03/12 18:39, Phil Dobbin wrote:
>> Or alternatively there are good deals to be had with a VPS
>> nowadays if you want complete root access to a box (configure
>> your own mail server& so forth) at realistically nearly the
>> same price as shared hosting. I personally use 6sync&  find
>> them great.
> 
> Getting a VPS is still pretty pricey.  The best I've been able to find
> for a lowest-end VPS is about $15-20/mo (both your suggested 6sync and
> Linode fall into this category).  For shared hosting, I've seen it as
> low as free (I wouldn't trust anything valuable to such a site as they
> often inject things into the output or reliability is an issue),
> frequently hovering around $3/mo for the lowest, $5/mo for what I'd
> consider reasonable reliability. That's a 3-5x price factor.
> 
> If all your site is static (like I seem to recall Dr. Chip's pages
> were), using something like github is a pretty tempting proposition: 
> stable, free, easy interface, and easy way to share and gather updates.


yeah, 6sync works out at around £110 p.a. for me whereas a good reliable
shared web host is about £75 p.a. (includes five domains, MySQL, Perl,
PHP, Ruby, etc). Bottom line is to me the VPS is about £2 a week. Spend
more on tea bags/cat food/toilet paper (sorry all my prices are GBP).

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPUsKjAAoJEKpMeDHWT5ADkkEIAM2B21maY10sJmxhNRDzGkoD
NyueW1HVOL3g55aq3jQ7ks8zhimaUoZvPxzYq1LGLCjBH7qPmfkB2fQGwn6Xkegh
1FS+yWACNwkVVbygUTbthnzZawb0939no2CNN+qqrV//Q2mFjrKF9VXHyjYaOOnd
BlEGL812IB379jc8IlcV5s3UxSB8KRBf9fkVjrkDcl0wn7aYnolOSBMwVR/1c2R1
MdYcX7YSWDL7dz/QpgwbD89r/JcN0sSCas2UTLhKiUasPc6F+MFcdkqBySTrjd9Z
quETQbx1aDPtY1M4JK3TsPfn441JJFmbOSsjZY4ZSbLH5kXzdHStvWzSEcEECZo=
=08le
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Exclude pattern in global command

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/03/2012 11:57, Tim Chase wrote:


> On 03/05/12 05:42, Jostein Berntsen wrote:
>> I would like to search all lines with "-->" in a file, but exclude all
>> these lines with "(X)" in them. Is this possible to do with the global
>> command?
> 
>  /\%(.*-->.*\&^\%(\%((X)\)\@!.\)*$\)
> 
> Using Dr. Chip's LogiPat.vim[1] makes generating these monstrosities
> pretty straightforward.
> 
>> Is it also possible to give a command to global that makes it go to
>> the end of the output list?
> 
> Just as in a buffer "G" seems to take me to the last line of output.
> 
> -tim
> 
> [1]
> http://www.vim.org/scripts/script.php?script_id=1290


On a somewhat related note, I tried installing Dr. Chip's above script &
it didn't play nicely. It had the effect of "bleaching" out the
appearance of the NERDTree so I pulled it from ~/.vim/plugin.

If Charles would like me to debug what is clashing with my $VIMRUNTIME
I'd be more than happy to.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPVMdbAAoJEKpMeDHWT5ADoiAH/0N7DXyWdz9HDuXXsTLXizHA
+k7C6pL+hBJqSzuHPW8BNOy/W3fwt1XvGeu1vkdSwu6oG1GIOqfzpqqYWfS6k/gu
ieTmlHKRUFIvQVf8pzKdUG6v1tZ5oPYlMCueVckPM8KRK3uMKXxyUh9wCMok9rWM
TjdX066c1+T16kjil4tPk/tikN7zA1D/GVUXAF+O7WppTVPl4P8L3T3y6rXsoVT6
CQpa9L9QsyzSQ6sKu3wSZcf66S8Y6Atzt8mi5hsOfXK9LWIDpn1o7I4vMeoyqQdT
gs9//jba6gyFvuuvxyGTA1p8RxeaWEuzmF9SYayjgwtdGcHcq3ccJAgroc0I9v8=
=dUHm
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Textpad to GVIM

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/03/2012 00:39, Michael Ludwig wrote:

> Dotan Cohen schrieb am 06.03.2012 um 00:10 (+0200):
> 
>> You will find GVIM frustrating at first, and you will hate it.
>> Once you get over that step, you will fall in love with it. Just
>> stick out those first few weeks.
> 
> Ah, come on, it's not that difficult … A reasonable working set of 
> movement and editing commands can be acquired and internalized
> fairly quickly. The tutorial does a good job of teaching you that
> base. It does take some practice, though.
> 
> The fact is that there's so much more than the base.
> 
> So some sort of frustration might ensue, after a while, if you're
> the kind of guy who wants to know *everything* about a bit of
> software. You'll notice that it's like striving to know everything
> about C++.
> 
> So when learning Vim, travel slowly and lightly, not burdening
> your brain with too many features at a time.

Good advice. Although I found trying learn to use Vim by only using
the home row from the off was too intimidating so I started with the
arrows keys until I discovered a mnemonic that worked for me: pinkie =
right, ring finger = up (ring up) index finger = down (put down)
forefinger = left.

I then found a desktop wallpaper cheat sheet that had the basic
movements, started reading :help a lot, used lots of scripts (Perl,
bash, etc) I'd got to navigate as if I was going to correct the
spelling mistakes & finally arrived at vimtutor. Circuitous but fruitful.

Needless to say Vim's extensibility is pretty much unsurpassed (never
tried The Other Editor so can't comment) & the community is great as well.

Have fun...

  Phil.


- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPVXOLAAoJEKpMeDHWT5ADouYH/A85rdlSOovVtbm9e/L+VcWq
hVVlri2+TCQ/AWuUNR+8lghnAFEMzWTII8AOzST6XbVYrcIN18gPUSC03ivWDGGx
sZloAIxvjC2cFE+QMoiVZsAOqGsOOQ4j//ohkyoY3jeMgifgrtY8pszRxDCwj+m2
3leug8VAxnpTATaq4uY2JheSfAczipzS3H2PffiVOYMucClaOGlGSHyYBgwJsxaa
xLQDOmcfajrGsN9TKdi1Hl5FdJPj0qMQGfV0WwQP6LPWUe2u0QYBYv6PGu2huipt
gsCSebK8sJUEu8vTHgNGivaz/vd9MHHp8iFYay9yEKQQ2mDrZ3mvweFJ/2UA08c=
=ulzI
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Control characters

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

I quite often send various man pages & the like to Vim like so:

`$ man foo | ul -i | vim -`

which works great but it tends to bring with it some non-ASCII, control
& null (ASCII0) characters with it. When doing this on OS X I've been
sending the file to BBEdit which has a Zaps Gremlins command which rids
me of the offending characters so then I can use :harcopy in MacVim to
save the resultant file as a PDF.

Is there anyway I can zap these gremlins from inside Vim & therefore
negate the BBEdit part of the workflow? It'll also free me up to do it
on my Linux boxes too.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPWlSSAAoJEKpMeDHWT5ADOJMH/RT6Is7LpL+JbJ8mv/WCk7G0
92hu3m9ADGaq1W9qdQDkLJa9CrCPk/ERT707NrBnpcPm4B4R4tvaaEjlWS5R0ncp
H7Ci4qxDHym6OO5Sial3Ah/gIJABTuYeG7kZe3mTMR2OCwAHO9TzLegK+xtyqaqE
SlZ9kHxUpnrb8sM+FB4goNiqTcCofHRk5JUKCI7kV+51lKM1oC0wUEgxDLsdWBzC
VZOTrGivcrDzHqtTvKH23959MohDzRsM0RgKkAN0nI0de+cgeSIm9UMhmpOSvEn9
Zq7uJuqzKbKgz4E9hism9JWEZNrGxQtRFG4pOq8R7ScCC4rSLb3f10J12ERnb7s=
=H10s
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Control characters

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/03/2012 19:33, sc wrote:
> On Fri, Mar 09, 2012 at 07:05:58PM +0000, Phil Dobbin wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> 
>> Hi, all.
> 
>> I quite often send various man pages & the like to Vim like so:
> 
>> `$ man foo | ul -i | vim -`
> 
>> which works great but it tends to bring with it some non-ASCII,
>> control & null (ASCII0) characters with it. When doing this on OS
>> X I've been sending the file to BBEdit which has a Zaps Gremlins
>> command which rids me of the offending characters so then I can
>> use :harcopy in MacVim to save the resultant file as a PDF.
> 
>> Is there anyway I can zap these gremlins from inside Vim &
>> therefore negate the BBEdit part of the workflow? It'll also free
>> me up to do it on my Linux boxes too.
> 
> you can put the following in your ~/.bashrc:
> 
> function vman() { man "$@" 2>&1 | col -bx | iconv -c | vim -c 'set
> ft=man nomod nolist' -c 'call Hideme()' -; }
> 
> (all one line)
> 
> where Hideme() is defined in your .vimrc as
> 
> function! Hideme() setlocal noswapfile setlocal buftype=nofile 
> setlocal bufhidden=hide endfunction
> 
> i use it a lot and never see any gremlins, with the added benefit
> of syntax highlighting on the man page


It doesn't work on my OS X box (I haven't checked it yet in Fedora or
Debian). The gremlins are still present & there's no syntax
highlighting in the man pages.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPWmrnAAoJEKpMeDHWT5ADy10IAMq9Z1BJMa4bdPAFBTJLx+YD
/lTPySJR7DRuWpX1A6Sj6A7l9+xEjlLsZeNmBjQ1UFxeAr1hGxuMInb91MIjt1TM
PoUluZDt6yxNZtJfmw0YQKhUqcLzEKuS83D+IAM6YKrJLmCAbItoPNCZ1p9EeBl1
Vd9WtqduuK5MZDMmcA7WSP2M4qy6V4a6exn+8UfsTctlBaHs7dZlMO18YAF1N2ey
HwoeziILpxVpMK6XWxK5jRboHKKXy0JG0GPe6WjNXl69eKglLiR8gLE9u6hyGDG8
ABAuaBIP/b+1QuWcodbeQ70OSvQdNPQfHK4nxVOlmO3TPUR54ymncU67UbIuiqs=
=zSXv
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Control characters

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 13/03/2012 07:05, Tony Mechelynck wrote:
> On 09/03/12 21:41, Phil Dobbin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 09/03/2012 19:33, sc wrote:
>>> On Fri, Mar 09, 2012 at 07:05:58PM +, Phil Dobbin wrote:
>>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>>
>>>> Hi, all.
>>>
>>>> I quite often send various man pages & the like to Vim like so:
>>>
>>>> `$ man foo | ul -i | vim -`
>>>
>>>> which works great but it tends to bring with it some non-ASCII,
>>>> control & null (ASCII0) characters with it. When doing this on OS
>>>> X I've been sending the file to BBEdit which has a Zaps Gremlins
>>>> command which rids me of the offending characters so then I can
>>>> use :harcopy in MacVim to save the resultant file as a PDF.
>>>
>>>> Is there anyway I can zap these gremlins from inside Vim &
>>>> therefore negate the BBEdit part of the workflow? It'll also free
>>>> me up to do it on my Linux boxes too.
>>>
>>> you can put the following in your ~/.bashrc:
>>>
>>> function vman() { man "$@" 2>&1 | col -bx | iconv -c | vim -c 'set
>>> ft=man nomod nolist' -c 'call Hideme()' -; }
>>>
>>> (all one line)
>>>
>>> where Hideme() is defined in your .vimrc as
>>>
>>> function! Hideme() setlocal noswapfile setlocal buftype=nofile
>>> setlocal bufhidden=hide endfunction
>>>
>>> i use it a lot and never see any gremlins, with the added benefit
>>> of syntax highlighting on the man page
>>
>>
>> It doesn't work on my OS X box (I haven't checked it yet in Fedora or
>> Debian). The gremlins are still present & there's no syntax
>> highlighting in the man pages.
>>
>> Cheers,
>>
>>Phil...
> 
> It assumes that you are using a Vim version compiled with +syntax and
> +quickfix, which usually means a Normal version or better (check near
> the top of the output of the :version command). In addition, in order to
> see syntax highlighting you have to enable it, by means of one (any one)
> of the following lines in your vimrc:
> 
> syntax on
> or
> source $VIMRUNTIME/vimrc_example.vim
> or
> runtime vimrc_example.vim

Hi, Tony.

The console Vim on my OS X box I compiled features=huge & no gui so it
has +syntax +quickfix & in my ~/.vimrc syntax is on.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPXxN9AAoJEKpMeDHWT5AD8KkH/0Z0WQCdGytpUsEHvimpSAPj
PhwdG186QoTNWMgvDq47sv5c8W1a9c0aXk1iD5sTf6ZNpXwTRXVfaSQ6qzuY0eTF
aABt8U1AJ/843wUDXsYALeFKowhADheysdyvhyIgEtJH+Kn5K/JoXCceeWptMoZk
+bcoCJQGE/R0puvjRwOZJNx56S87+TbqMCGFr/tz2ZR7zCK65acHKPfg16ANq74i
fV1pTR2HJeUW3awp4PjUTh1Y4lIUWVc0lsB3KCN6r/i87k/3UmRyFFbBeHnv1zRG
P8KttGeMh4yB0SAWRJstdy841rDbrbyjGKVswog+Rbcbjp/WXyxMN8Ax+6ZbMsY=
=IVk4
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Control characters

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 13/03/2012 10:52, Thor Andreassen wrote:
> On Fri, Mar 09, 2012 at 07:05:58PM +0000, Phil Dobbin wrote:
>> Hi, all.
>>
>> I quite often send various man pages & the like to Vim like so:
>>
>> `$ man foo | ul -i | vim -`
> 
> Not exactly what you asked for, but here is how I do it. In my .vimrc
> I've got:
> 
> source $VIMRUNTIME/ftplugin/man.vim
> 
> which makes the Man command available. In my shell startup file I define
> a function that will open the man page in vim, something like this:
> 
> manvim() { vim -c "Man $1" -c 'silent! only'; }

Hi, Thor.

This is getting curiouser & curiouser; that won't work for me either.

I've appended the first line into my ~/.vimrc & the second to my
~/.bashrc (this on Linux).

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPXzSuAAoJEKpMeDHWT5ADUaoIAJc1Pl9WmSGxIM2GR52F+4TB
eDJtbjdEhm0KyPEuu1hVcj0rJgU1Yl0FnZpx1h1NLh0Gb1UPw7UkDmBl5yWWNWHo
kvk9ulXNmLoiTO+SJqyZMwlZpVb9OkbOWsE3b0Ifk3i/JGroc9W0XlcPnYSjS0Cl
hsysF00AoPtCzqfO7sI/vh1HKOrnGirU5unLIq2wegRGwYqfF3rsrEKxNb9rDKvY
g+Ux3Wp4G1VaglhnHSiVWtrXz2hm3kI7yfttwW7u8TxUj5xaqKI8241Visz6kYVs
OcJPZ0o4YVO8p9fGF9O/IEqb2T1trVCyxWvepLYF41Pw7GXGsuUIjMJgN47lmVI=
=tquT
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Control characters

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 13/03/2012 13:28, Thor Andreassen wrote:
> On Tue, Mar 13, 2012 at 11:51:13AM +0000, Phil Dobbin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 13/03/2012 10:52, Thor Andreassen wrote:
>>> On Fri, Mar 09, 2012 at 07:05:58PM +, Phil Dobbin wrote:
>>>> Hi, all.
>>>>
>>>> I quite often send various man pages & the like to Vim like so:
>>>>
>>>> `$ man foo | ul -i | vim -`
>>>
>>> Not exactly what you asked for, but here is how I do it. In my .vimrc
>>> I've got:
>>>
>>> source $VIMRUNTIME/ftplugin/man.vim
>>>
>>> which makes the Man command available. In my shell startup file I define
>>> a function that will open the man page in vim, something like this:
>>>
>>> manvim() { vim -c "Man $1" -c 'silent! only'; }
>>
>> Hi, Thor.
>>
>> This is getting curiouser & curiouser; that won't work for me either.
>>
>> I've appended the first line into my ~/.vimrc & the second to my
>> ~/.bashrc (this on Linux).
> 
> You mean running eg.
> 
> manvim ls
> 
> doesn't work?
> 
> What error do you get?

Apologies, I was being dense.

I copied parrot fashion the lines you posted to both rc files without
reading what was actually written.

Issuing `manvim` works correctly

Thanks for the help,

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPX1tSAAoJEKpMeDHWT5ADXusIAKnNiByHW5kyJ4vt2TufsdmS
fbATu4RFPmO8I1l+uHGhlZcrdbbMP/DzqqomkP7Iok7CJGRUGdG2DDMpivbq4Q1L
AXc1XiKBEAUYWJg53qmCEnjATUCIyIJvz7MxFx5Vh7oWwtamJ8J+lB6+LQ2DApER
dRlIm2y15aesUBA+jpumsY3i86fZEgV2Bwdf9timyyCvfOTI92XpdJrgmKl3/8Vq
d7uxOsP64X+VYhJtczFFeryX8oENcl9BJ4vilqqwHwI8a8y38iv3T1Bnf/Re0j0H
4K/dUlcW563hUmwxLctHCK0Dtl3wFbHqVgjH/gtEkEMk8TghVdihXCYb2Ir1s8E=
=+cMw
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: find a script to capitalize SQL keyword automatically

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 17/03/2012 15:33, stardiviner wrote:
> 
> I want a vim script to convert SQL keyword(statement, clause, those highlig=
> ht group in file) to be
> converted to *uppercase* when I type command `:w` to save file.
> And another way is when I am typing: `select`, then vim automatically chang=
> e to `SELECT`. (this can
> be done with abbreviate).
> 
> Use uppercase SQL keyword will improve the readability of sql code. That's =
> why I want this script.
> 
> If you know a script can do this, or you will create a new script to do thi=
> s, please tell me.
> (I do not know Vimscript, so I ask this script here).

In Visual mode `U` will change case of the selected word.

See `:help case` for further options.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPZLUfAAoJEKpMeDHWT5ADWCIIALyXgahfAnnXmqe/W5aVl3j4
kDZXpYGGz0MllTHSX1cihl3KInBoKh0KqeZCBovI4iJGp91T6S881JOtJkrrc/pe
E+UD8Ymkc3gbq2EuRqXN/y1AxUotIk0EuMfYUsf5ukbRb6lpu8o1JPBQPYkHjQYr
kT2hR+EhMrTkOvkouwoIx8cYLuYOXj3OZ7ZNHRX1RldOIm2IwSLkblLM5OKO8ao7
6ToJLMXlmz+ZfpTrFXNl9GqnbuwGXnawh6FYxzoSAM/suT9gnELmrsf46kJyW2s6
VjopuUEvRhrZ05kY0XPCvL0O2P3KlKWITJAGaA06jCPhH5xOMB1M8+YGaqC1/Pc=
=VUrC
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Checkered background in terminal mode

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 19/03/2012 23:07, Michael Ludwig wrote:
> I started using the Solarized colorscheme yesterday. It looks
> great, especially in GUI mode on Windows.
> 
> I have configured Solarized on two Windows 7 computers. Both
> have Cygwin and MinTTY (a terminal). There's a special Solarized
> configuration for MinTTY.
> 
> On one of the two computers I work on, vim with Solarized now shows
> a checkered background; it looks like a mixture between Solarized
> and plain black colorscheme. Take a look:
> 
> http://snag.gy/0fZcU.jpg
> 
> I would expect the background to be either blue-greenish as
> configured by Solarized or plain black. Both are okay, but the
> mixture is confusing.
> 
> On the other computer, Mutt (a terminal mailer) shows a similarly
> checkered background.
> 
> I think it's not specific to Vim or solarized. I mentioned the
> problem showed up in Mutt as well, and also before in Vim with
> another color scheme.
> 
> Has anyone encountered this oddity before? Do you know what things
> I'd have to look at to find out what causes this bad display?


FWIW, I had the same issue with Solarized in console Vim on OS X (looked
great in MacVim however).

I was running 256 colours in my terminal with it & I suspect that using
88 colours would have solved it but I just switched to Molokai & didn't
bother investigating further.

There is a repository for the Solarized colourscheme at GitHub. Maybe
you could check them out (or read the issues) but I'm sure somebody here
on the list will be able to help.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPZ8F/AAoJEKpMeDHWT5ADaa8IAIsVnfviSWUPYj9fp2ArAtxk
2a5qRkoEBDwYfmdOhbkD+ah1Mfk8SHiO+pwdKoi0EEUYZ6Ui0PpaGEa6c2unXBF0
mcjmhwSWGDMfThuoNNApVkQWtDjqek06F0Yhe7NUEyzrqzvkQ01mJtfhCyFLQffc
f+Seo+aoIIAWO+vt99mRUYZh+JgiHDZYrO8owW6v9pTL7eWRrovqMbLk/H8cHWFF
Mb8NkgDeZCckK1xiwWbDN9L5n4HmGE0fC9+dnzlnVEMhXk/178ZpER6q3zxINykc
cnv956Sa7XlWT9K1zXzprK7gv5HLqZjcEcTSAf4ctOXNJSQVZypwqlNutSZbm+8=
=+Ubf
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Compiling Vim and gVim on Debian

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/03/2012 20:52, John Degen wrote:
> I'm trying to compile a huge version of Vim, including gVim, using Mercurial. 
> I've only managed to install console Vim, and that's a normal version, 
> without Python and Perl interface. I followed the instructions and issued 
> these commands:
> 
> hg clone https://vim.googlecode.com/hg/ vim
> ./configure
> make install
> 
> Am I still missing packages? The Debian package (Vim 7.2.445) installs 
> without problems and offers a huge version.
> 
> System info:
> Debian 6.0.4
> uname -a 
> Linux xeon 2.6.32-5-amd64 #1 SMP Mon Jan 16 16:22:28 UTC 2012 x86_64 GNU/Linux


These are the configure flags I passed to the build:

`./configure --with-features=huge --enable-perlinterp
- --enable-rubyinterp --enable-tclinterp --enable-pythoninterp
- --with-python-config-dir=/usr/lib/python2.6/config`

when I built on Debian Squeeze. The python version you have will have to
altered to the one present on your machine & remember to leave the
trailing slash off the end of config.

If you need the gui pass `enable-gui=gtk2` flag also (if gtk2) & also
point to the header files as configure won't find them otherwise.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPaRGKAAoJEKpMeDHWT5ADIX8H/18XY1aJHTfv77wKgw83Xr8z
FVsnZqqSJOYwLAioiwwdkcsmt+ZqNlNJzDpgzychfbFBbo0ziABNgLt6XtiSoiKA
KwizgM2F4m3N8BYOfjltCeX6gLE+5iaAb7ADoMUuvjvGSR0qeIMTm+wH3trjtueh
Pr1CD13Mw1jREv71zf1VXshXGUQiBkZOrUs444iL3V51F85eWQxiHv2LRwLx6Srb
ageGJB7ROE3v68KW1C448ygTR4JZyVPDrb4qb0lc8IGNx8Hdy11HDi9aATuBCMz4
CYzM6wqCiOEPA8IcPBmSopvGXiyzQVcRav3+aSGRvLNp/8bObfypN3TBmWaPIqY=
=A3QH
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Compiling Vim and gVim on Debian

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21/03/2012 02:11, pansz wrote:
> On Wed, Mar 21, 2012 at 4:52 AM, John Degen  wrote:
>> Am I still missing packages? The Debian package (Vim 7.2.445) installs 
>> without problems and offers a huge version.
> 
> sudo apt-get build-dep vim
> 
> this is all you need to compile vim huge version.

Whilst we're on the subject, when I compiled Vim on Debian, I only
required a console version & later on I came across a hyperlink that
described the whereabouts of the package needed for the header/dev files
for gtk2 in order to build the GUI version.

I've subsequently mis-placed that link it seems so I wondered if anybody
knew where I could find the relevant information (my Debian box is
getting retired at Squeeze & will not be upgraded to Wheezey & the GUI
version supplied by the Squeeze repos is Vim 7.2.445)?

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPaYLcAAoJEKpMeDHWT5ADIW8IANVZASztNPwVhcBwRc9j/iqH
n/1KV69tZ4N/GHg+487WsgDz7iPlZ9K9Wf5pxNvSObzsJSI8T/9Cu8Nec8hJcMqX
CIiIa0mI0ldUeiKgzSFn27+2LKQ/DJLnNK3me/KLw6Jif6vyUldRYhrfsK8wi65p
D3LKnxEUqFY0mozEa134go2pldUtpe8bqil/KtO2V1q7p/X4xXdm7zgjX3bVm4JS
Le4yO/w25dbRNxWbpzyKXVpWyKFdmBBjk49DpBHrsCm0FmylsxzUfRqXt9XpWyvR
Rlt94VdCq/py9nqdhNQM6y+47iOBXUvFPv7LsxAi+lKpVm/gON6dXCUNzPcaC5M=
=hy7c
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Compiling Vim and gVim on Debian

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21/03/2012 07:37, Christian Brabandt wrote:
> Hi John!
> 
> On Di, 20 Mär 2012, John Degen wrote:
> 
>> I'm trying to compile a huge version of Vim, including gVim, using 
>> Mercurial. I've only managed to install console Vim, and that's a normal 
>> version, without Python and Perl interface. I followed the instructions and 
>> issued these commands:
>>
>> hg clone https://vim.googlecode.com/hg/ vim
>> ./configure
>> make install
>>
>> Am I still missing packages? The Debian package (Vim 7.2.445) installs 
>> without problems and offers a huge version.
> 
> See the faq:
> http://vimhelp.appspot.com/vim_faq.txt.html#faq-35.10


Unfortunately running:

`# apt-get build-dep vim-gtk` apt returns:

`using vim instead of vim-gtk`

so it seems that option is no longer open on Squeeze 6.0.4 at any rate
(I do have deb.src in /etc/apt/sources.list).

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPaYxzAAoJEKpMeDHWT5ADjGkH/R+MSiP6Hj7/LGSpsrMu4Vvg
Hq5xSQgrwuhQ+UxZcErsLMCKcVKd+B1jSqF2AF7HYKmVMr4x3htscYVDzlEfMvXh
WtGHPWXfJfSQGmosnPmqz9fLKlh43ubdGnoD/tRftl/DUrYXY0Lxb5sb5PwabonP
tM8TXxcZbygy5Yuu5O++mx24yDWJ8B28UA6wDLtkbHKVvgUUvR4BfjXsChYBMwxO
vzjgBTibm7Wv2oi+B6+FGko1T0l8w03Hukmj8NA7b1DalzQCtrNVZyM6sOLXZymV
wCgmvJfsQ6ogALraNUvS1OXIDh4S0MSeWhbzfrOOXQjyjsFXBYgHP68pmYwNeTg=
=/HKU
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Compiling Vim and gVim on Debian

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21/03/2012 08:11, Christian Brabandt wrote:
> Hi Phil!
> 
> On Mi, 21 Mär 2012, Phil Dobbin wrote:
> 
>> On 21/03/2012 07:37, Christian Brabandt wrote:
>>> Hi John!
>>>
>>> On Di, 20 Mär 2012, John Degen wrote:
>>>
>>>> I'm trying to compile a huge version of Vim, including gVim, using 
>>>> Mercurial. I've only managed to install console Vim, and that's a normal 
>>>> version, without Python and Perl interface. I followed the instructions 
>>>> and issued these commands:
>>>>
>>>> hg clone https://vim.googlecode.com/hg/ vim
>>>> ./configure
>>>> make install
>>>>
>>>> Am I still missing packages? The Debian package (Vim 7.2.445) installs 
>>>> without problems and offers a huge version.
>>>
>>> See the faq:
>>> http://vimhelp.appspot.com/vim_faq.txt.html#faq-35.10
>>
>>
>> Unfortunately running:
>>
>> `# apt-get build-dep vim-gtk` apt returns:
>>
>> `using vim instead of vim-gtk`
>>
>> so it seems that option is no longer open on Squeeze 6.0.4 at any rate
>> (I do have deb.src in /etc/apt/sources.list).
> 
> I think, this only means, apt fetches the source for vim-gtk which 
> happens to be vim.


Hi, Christian.

This is actually what apt fetched:

`lesstif2-dev libacl1-dev libart-2.0-dev libattr1-dev libbonoboui2-dev
libgail-dev libgnome-keyring-dev libgnomecanvas2-dev libgnomeui-dev libg
pm-dev2   libgpmg1-dev libperl-dev libxp-dev tcl-dev tcl8.4-dev
x11proto-print-dev`

so these indeed may be the required header files. I'll run ./configure
against them & see.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPaZANAAoJEKpMeDHWT5ADy+wH/00+dT7XsvXxTBxef2d1Dg34
uqnFUuBoIaOf/Uac+CZQ+8EbxtNOTQeX8cpmF4NgTEEDg+dryFFlAWdx/L1D52U4
LFmCg5cMpqnUDgLv1AMSLFBniUUiBpvdYCwC2dLfgFDJQW8HnAQF2xPvi7DWR1GG
ivshjh5yYZU7sJ7KOweeKpWrfT+rqPaOqr+YBbmAy4h+xsl6vc9/KE8TygNiMs1N
62vgUaqJ0r4tm0cKPSYJ4pyfl64FQ6uYG6FwwWhBGq1LiTO3x7rYV2xUrL5FX4fT
fPcBhLXW4T2t1Y4QmZ6ATrbl6Q7Cm7I+kYYHpFPccsFyGxBiJzTdS5kvGSdXWsI=
=17fw
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Compiling Vim and gVim on Debian

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21/03/2012 08:23, Phil Dobbin wrote:
> On 21/03/2012 08:11, Christian Brabandt wrote:
>> Hi Phil!
> 
>> On Mi, 21 Mär 2012, Phil Dobbin wrote:
> 
>>> On 21/03/2012 07:37, Christian Brabandt wrote:
>>>> Hi John!
>>>>
>>>> On Di, 20 Mär 2012, John Degen wrote:
>>>>
>>>>> I'm trying to compile a huge version of Vim, including gVim, using 
>>>>> Mercurial. I've only managed to install console Vim, and that's a normal 
>>>>> version, without Python and Perl interface. I followed the instructions 
>>>>> and issued these commands:
>>>>>
>>>>> hg clone https://vim.googlecode.com/hg/ vim
>>>>> ./configure
>>>>> make install
>>>>>
>>>>> Am I still missing packages? The Debian package (Vim 7.2.445) installs 
>>>>> without problems and offers a huge version.
>>>>
>>>> See the faq:
>>>> http://vimhelp.appspot.com/vim_faq.txt.html#faq-35.10
>>>
>>>
>>> Unfortunately running:
>>>
>>> `# apt-get build-dep vim-gtk` apt returns:
>>>
>>> `using vim instead of vim-gtk`
>>>
>>> so it seems that option is no longer open on Squeeze 6.0.4 at any rate
>>> (I do have deb.src in /etc/apt/sources.list).
> 
>> I think, this only means, apt fetches the source for vim-gtk which 
>> happens to be vim.
> 
> 
> Hi, Christian.
> 
> This is actually what apt fetched:
> 
> `lesstif2-dev libacl1-dev libart-2.0-dev libattr1-dev libbonoboui2-dev
> libgail-dev libgnome-keyring-dev libgnomecanvas2-dev libgnomeui-dev libg
> pm-dev2   libgpmg1-dev libperl-dev libxp-dev tcl-dev tcl8.4-dev
> x11proto-print-dev`
> 
> so these indeed may be the required header files. I'll run ./configure
> against them & see.


No need to in the end. They're located at `/usr/include/gtk-2.0/gtk/`
which if missing can be installed with:

`sudo apt-get install libgtk2.0-dev`

Just need to pass a flag to configure to point it at the relevant directory.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: Ā§auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPaZQaAAoJEKpMeDHWT5ADqOgIAJxIQCgOEQ5xr+hsrjegtbWY
NXT6qs3aPo/9pw+wGQ7TA/YcYshOsvYOuBP0tJkdT5eg4GG94svWj92qiXEFAPD6
Qa7Ljdg9dPcbRWf7pXEF/Hz5fhnQjdEYoWFcHjzox89d7wSpJeh3tPA64Dw+YF/g
a9je2VNHVgd5ZgJ9PiJ+pJmfthubyw9MTluCXpeQXUjuATzgOdTCw57fAZzvls3q
42eGfC8vnZ53mOgacWthXl2+gUlfnC+DqNwno9wVDabfnkgcSD61Y3+LPrj4D2Lt
SN47+z/n7O1CvMNkC8mLDXwUdTn7MhcKW0N3UwZLcYH/BLRn/y/b7T08P2KCaoA=
=bwWV
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Present output of external script in dropdown

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/03/2012 06:17, Christian Brabandt wrote:
> On Thu, March 22, 2012 10:42, Jostein Gogstad wrote:
>> I'm using Vim as my default text editor for writing e-mail. I
>> have an external perl script that does LDAP-lookup and outputs a
>> list of names matching the search query. Is it possible to
>> present this list in Vim?  Preferably in a dropdown like the one
>> you get on keyword completion (default Ctrl+N).
>> 
>> Ideal scenario: 1. Start writing Paul 2. Hit ^T (or something) 3.
>> Vim executes perl script with the word under the cursor and
>> displays the result in a keywordcompletion-style dropdown.
> 
> I use something similar. Basically, for looking up e-mail
> contacts, I use The little Brother's Database lbdbน together with
> mutt and Vim. Additionally Vim Script 1757ฒ plus a custom complete
> script that I found online somewhere, but don't find it anymore (so
> I attach it here)
> 
> The lbdb comes with a little script lbdbq that can query different 
> sources, e.g. mutt alias file, abook file, OS X adressbook, ldap 
> server, etc. to query for contacts so in theory it should be able
> to query your own ldap server, but if that does not work for you,
> it should at least give you an starter how to write your own 
> script.
> 
> น)http://www.spinnaker.de/lbdb/ 
> ฒ)http://www.vim.org/scripts/script.php?script_id=1757


There is also a link I found which is primarily for mutt & Vim made by
its author for OS X but can be adjusted that as well as incorporating
lbdb, uses several other utilities (urlview, Mairix & Mailcap) to
handle grabbing urls & sending them to mutt, a search tool & the
handling of attachments all using Vim as the editor (well, in my case ;-)

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: ยงauto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPbDVAAAoJEKpMeDHWT5ADtK0H/03gD4sEhCPX0AEYlSn3IN1c
qvjUIVgSbfV/lt1j7yN8mGA3CFW9IpHiijwkRYfEQsJnjuSUhCPQQ+C8k6kfqD1w
tU2KZxWW9TX8urVp0FipRA6Br941TXvI5meeVqSsrYR9occ0KY2Zz2XcDZEmBdd1
nOoc1UOrJtLZVHjjtDTu1a6fHHOJiY6iLkTUyi0pmlWo8EPrXVtbiKFPeScNLELN
lipSExgDG3mruCgSeorwEyppdpN5NPsCl/F7n8/yCXM/FlRX9nrg8V5kk7dIacyv
Uk22/BLhFZfNRb0tTrCQL1Jzq+vASiy78NDC9xTxnbWsS5aL7YDvJP4q05zgrUo=
=26zV
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Present output of external script in dropdown

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/03/2012 08:41, Christian Brabandt wrote:
> On Fri, March 23, 2012 09:33, Phil Dobbin wrote:
>> There is also a link I found which is primarily for mutt & Vim
>> made by its author for OS X but can be adjusted that as well as
>> incorporating lbdb, uses several other utilities (urlview, Mairix
>> & Mailcap) to handle grabbing urls & sending them to mutt, a
>> search tool & the
> 
> What link?
> 
>> handling of attachments all using Vim as the editor (well, in my
>> case ;-)
> 
> I did something like this as well: 
> http://www.vim.org/scripts/script.php?script_id=2796

Apologies:

<http://linsec.ca/Using_mutt_on_OS_X>

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPbEn3AAoJEKpMeDHWT5ADOZ4IAMRF/Gevc3heiDuzTabijCeT
WXaT922N5nbOlzOzdnFHuARW03fGGmnXcsYs7BPGUWzQmbg2oW16BQay4e+kUscy
IEjOkS4+Q9po2/QPJaSMpu0VCZ3SkaQrEI7XNKtMWBZzPQi730j04+PEEOf2xG9H
BT1Lgz3MVY3kiQYeQQEY45K8ZMqCiDqg1PdzM4VOGaA3xkw3XggQQ1ZL3K5o34wP
7xkDzk18mJEjKnZP8j+IQabvwV/79F57+3U8qtlOWYko0XOmFZSi3L4zA0R0FpZp
zs9SVPi6wiyfmOymm2tl2PTKAos88lxKzosBaSS8XOzRmX/2FwrIBMiJvuBozcc=
=VLCR
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: vims source repository gone?

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 24/03/2012 00:25, meino.cra...@gmx.de wrote:
> Hi,
> 
> when pulling the newest vim source from the repository I get this:
> 
> hg pull
> pulling from https://vim.googlecode.com/hg/
> abort: HTTP Error 404: Not Found
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> 
> This is since version 7.3.471 (470 was the last working one).
> 
> Do I miss something?


`hg pull` is working for me. I tried it again just now & I pulled the
latest changes about four hours ago also.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPbR4DAAoJEKpMeDHWT5AD3pAIALoOgYcQNOA2t/tlaYdMfeDA
vUYjBOwb+oYkZIe0hdUYnnhN+kzNiYEh5wr4XCWKvbRwBATzI7WZ8WopwlLRNYyv
Txns9HhBlv39E0mPIF5Pvxk0d2DpNLP5NQ6mQ4XDKmz3y6rSal8woqQ7uoWsccgj
g0diBLgYt5R0XxLv1AxEzBKmZ1sD7gh1pRse0gvXPpwdacuuX77uS5FPkkU4YXYL
j7WTJV4RK533m2aHFScrsS1Ab/MK6GSdbXso6dFD4sWD2BAdC6zdvY7MfeSJB5UT
ETQotmXQctLFyjUE8lVFObzd4mCTEMn+rVSNl5GJrNTfdWPfOv01XeRpFmbwUDw=
=DtuT
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: googlegroups strips recipient delimiter

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25/03/2012 22:49, Jorge Luis wrote:
> Friends,
> 
> Unless I have procmail and/or mutt misconfigured, I've run across a
> problem with the vim mailing lists in particular and possibly
> googlegroups in general.
> 
> It seems that googlegroups strips any recipient delimiter from an
> address when crafting any message destined as a reply.
> 
> For example, I registered for vim_use with the address,
> .  Replies--or any post, in fact--from the mailing
> list are addressed to .
> 
> Not a big deal, perhaps, but I use the "+" recipient delimiter and the
> following extension to filter incoming mailing list messages and route
> them to a specific mailfolder and/or a forwarding address.
> 
> The deletion of the recipient delimiter and its extension appears to
> extend to all relevant headers in mailing list postings.
> 
> It's a little odd because the googlegroups subscription interface
> relies on a recipient delimiters to distinguish subscription requests
> from other administrivia.
> 
> Has anyone else noticed this behavior and perhaps devised some means
> of retaining the recipient delimiter and its extension in any of the
> standard googlegroups headers?  X-Original_To:, To:, or any other
> header?

FWIW, your message dropped in my inbox getting missed by my filters as
you seem to use:



instead of:



Whether this is relevant at all, I'm not sure.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPb8NjAAoJEKpMeDHWT5AD8mIIAItkVusUleZBhu7N1l2fehmi
8j5WhZ4vJLX6blnZ6vvvDk/c/3RRC3lF4FZyVUNVdrJdK2/DyxXS2j/1zv5jjHnT
PuSyYVbyJoipV2EM9vLerRlSPSHO7xSv0IhgEdM0/yiafKdxRqL7KK2YTRwrUgjf
nL4zaORtCcmf1t3C+L4/BGyNbFAHi12Pnbw4sDu3t2oUvrn+A0Q/4beaIpOVt7X1
bstnEb6m7AJMeQWEjdN7x4DYIDTo2GihDJ8hRnH6ZDLHntw+9By+99A0OIbw+7Dg
WPanvPN5kCkQ0jpudnu0zkYTHPfax3qW68MOBslV+wwYMejopDm7X5hv8kGI0fo=
=7E0b
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Cool error message

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

Great error message in the Download section of 

`Service Unavailable
Guru Meditation:

XID: 1794358973

Varnish cache server`

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPdHLxAAoJEKpMeDHWT5ADSOgH/i6TMpCrfJ6CmUhSUZ4coTi5
dV5AMrN/CyRCvXSgwPUTHZu1eCYEEcxauE65THEQ3vKWrgyOtXtA0CJd3Lo2IFUR
VPzrLeYUISXPpogD9bncfdUYfSRsWlkrlnMENG/nFwHLpGCW9rbvjTu6MgUomz0G
8GpWag1S9x3oUnapx09Xk1mkClrObETR0Gvl9xF6OS0kUBX0VdHhsIaZbOSpCFeK
HYA6fJmIFa1kKdO6B4scLHVNlCwn6HpkNdLL/T9K5KMwOYNI+3MHgvzoUo+yQKIJ
VWMuKW06Ut/10uKgX++JGir1TIqi8UkJb+FFTKEHZa1pyegPWy70OgM7MoCsdXE=
=8Rpx
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Cool error message

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 29/03/2012 17:02, Magnus Woldrich wrote:

>> Guru Meditation:
> 
> Good old Amiga... :-)

Ah, I see :-)

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPdIh5AAoJEKpMeDHWT5ADN5sH/0w0bY3myjiJxc34vtISpcVY
DMNiBMWsAr0f2GAs3RTELjZY/1ZAR9A1M0YKXBXnsEJFeFJhR2LOUDYR2zNGGZug
RqueLa1AKrmSH2ApYw+cBFeRW+0O8Jj9lNYDWcjt6tCngaqX7l1zCGEO6imG1MbJ
fNNBLhOXDyZU5LE/NCroygaaoT+zjhZBg3pdbbVaJBo9l0/7VeQ57VpCkwWj2KYQ
6NsrvW0Srh3RZRwzwIXxhM85GbFuhfJEcYrNGyfNv+LbjB0VWS6amMVaB8NIoMkZ
DqfaLQ/M7lDkXIsUki+U/OH5JsHhPvJy/otrNJ+QkZZx/8UDAWIweonobnWZQ40=
=lo7A
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: :help WITHOUT split screen

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 30/03/2012 13:39, Guido Van Hoecke wrote:

> On Fri, Mar 30, 2012 at 13:51, Tarlika Elisabeth Schmitz
>  wrote:
>> This is one of my biggest bug bears and it drives me absolutely nuts:
>>
>> Is there a way to prevent :help from splitting the window?!
>> I never, ever want a horizontal split. I'd just like to see the help
>> text in a new tab.
> 
> Same here
> 
>>
>>
>> I mostly use gvim, sometimes vim. So I need a solution that works in
>> both cases.
>>
> 
> I have this command abbreviation:
> 
> " h open help in new tab
> cabbrev h tab help
> 
> So whenever I ask help with ':h' it just opens a new tab with it.

Maybe it's just me but if I type:

`:tab help topic` that works but the above abbreviation doesn't do anything.

Vim 7.2.445 huge with GTK2 GUI & the same console version on Debian
Squeeze + Vim 7.3.462 huge no GUI & MacVim 7.3.353 huge with MacVim GUI
on OS X.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPdbCIAAoJEKpMeDHWT5ADxAsH/iPqXFjeRiJMGRHRLhw6EdEB
n3seaTxR1wxgVOk3FGoZb7x+erPeq+ygHtu6FqdTP+eMvnYBGNlKSOtcRIDn/I8S
wHfsOiWz2PTPf3WFZDc772i/RwlU0ASnlgGj7KniRZY3AO4CnKc6EjJglyIX1FJK
Jgp9X0xvYRVmFDCU7DcSenspU41IoncbA/MZMDd/tTW0VX7pzvngd4JU8TQWYPbA
yCgIeNTp187I+sO/tZmXjVGlDpVnfb67w7uCan44vEOadwKm0m6U7LUURqXcsSyp
+PxQG0VGH2K3NyXRnkzFcXTJSSo/F4sHARyK8Pdz2e/j1vkwsGKIUaH8BzqRW20=
=4SIZ
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: :help WITHOUT split screen

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 30/03/2012 14:35, Tarlika Elisabeth Schmitz wrote:

> On Fri, 30 Mar 2012 14:39:33 +0200 Guido Van Hoecke
>  wrote:
> 
>>> Is there a way to prevent :help from splitting the window?!
>> cabbrev h tab help
> 
> Many thanks - works fine here.
> 
> I've covered all options in .vimrc now:
> 
> " always open help in new tab cabbrev help tab help cabbrev he tab
> help cabbrev h tab help

Very odd. Never mind, `:tab h topic` it is then...

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPdbt8AAoJEKpMeDHWT5AD45EIAMtDgRTtTIaIA7ts6POay+5y
v8Oihnta51JJ/S+y6mDSjWE8vDSmr10+nl0SDioEx6Fs+hbEmnlyhco4xkci33hr
wcbGyerCTBJIgvW9ykf88mKU94dmmfXb2btBFl6JOMMgqkvvE2Z39Tjze3lvBWrh
+NigFm8Vdwss9hLhsFfl/iW4oY2Ou6etjwgcJ3mkt/7ZzRQjMQfp96EFZ8ktOtI8
jx77IZEjplplLTy61pN8u1cYAX3ip2vEd55cIaqMr27gIZOG8GiVzbSIB1OVoXlT
M3+GLivEhr1CtKVB2FxG0M/IFdmHhfltyt6QEvS2I57SjtF5HEX2BTBl8XzAiC0=
=7Sv7
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

E365 hardcopy

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

Out of the blue this morning my Debian Squeeze Vim (7.2.445 console=huge
GUI=gtk2+huge) has started throwing the hardcopy error:

`E365: Failed to print Postscript file`

this is on both the GUI & console Debian supplied Vims.

Apt hasn't downloaded & installed any print updates recently & I can
print the same test files from gedit, etc.

Last time I had this on setting up Vim on Fedora it was a print
preferences error (different name for the printer than specified in my
vimrc) but this is not the case in this instance.

I printed from this Vim on this machine a couple of days ago no problem
& I haven't altered my runtime or machine settings in the meantime.

Any help appreciated,

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPduylAAoJEKpMeDHWT5ADxyUH+wUK7GfuaNtOmpeZ++bu+ezJ
qNuEQs8HWSDLdSUW34rfpjIcU/a/B/6er1DskU8LRFf/it4omAwk4RbxWyHELwtV
mJCeOO4dAnPwYdJRqPq4q70Ww85keSiGaKPfNCcWOCupstmdDSCMZUYTP/d3G0Jo
DIHQ9sApgsijcOcgxFBv7M7i/OvcC2E+wIkKfAZVmnP0OiFkWvnUHhVwGrfy963C
jCiLkFCCu7AJvg1u+wwa2LBQSrdmysOFIeac8Q06ZRAMcBWNNLErjEU0qu6hw+5a
Ylo+f+Ne0DJvw5AsruqZGIQjFcbaujbNW9w4Ohyk6UqzGyOMILePeyAt6SZNBa0=
=dCxs
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: E365 hardcopy

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 31/03/2012 14:23, Tony Mechelynck wrote:

> On 31/03/12 13:38, Phil Dobbin wrote:

>> Out of the blue this morning my Debian Squeeze Vim (7.2.445 console=huge
>> GUI=gtk2+huge) has started throwing the hardcopy error:
>>
>> `E365: Failed to print Postscript file`
>>
>> this is on both the GUI & console Debian supplied Vims.
>>
>> Apt hasn't downloaded & installed any print updates recently & I can
>> print the same test files from gedit, etc.
>>
>> Last time I had this on setting up Vim on Fedora it was a print
>> preferences error (different name for the printer than specified in my
>> vimrc) but this is not the case in this instance.
>>
>> I printed from this Vim on this machine a couple of days ago no problem
>> & I haven't altered my runtime or machine settings in the meantime.

> - Any recent changes in the PostScript / groff / other related… packages
> on your system?
> - See also ":help print.txt" and in particular:
>   - :help print-intro
>   - :help print-options


Hi, Tony.

No, nothing has changed on the system (only nagios has been installed &
that came without the print monitor option) & I've read & re-read the
above help files several times but nothing in there seems to be relevant.

`h: E365` isn't much help either I find, so I'm stumped. I have exactly
the same runtime files on my Vim in OS X & that's OK so that probably
excludes a plugin problem.

I'll have to run `dpkg -l` & sift through that to see if I can spot
anything blindingly obvious but I'd've thought if that was the case all
the other apps that I can print from would suffer too (lpr can print
from the command line too).

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPdyrVAAoJEKpMeDHWT5ADz+sIALb6N7cSOuUKFXLcNgtQGGj/
OC8tGt6+LSBpZakg9I72tFcRaQk0qrjPyacEaLui1np3wtU9BPSbCMEj97+eNo04
J7cqwOY26Jj3O1zb7rjYb7v1NfURGlB2eRC8FpV3ZW6K6oibMryaUYxZkgRA/y+O
vk/IMbRaMG/K3ZYxesSbM63ylhlyPniURPyuioKknZ6liAaviV9H014CQY463jUe
glw07yE0tY/dXfI6lhCkEdLEgtRODrazrAh1t1uTFgkfz4bxvVnOAbaJaDR/R0ZC
O9OaKhw8vmagKVB/4DZf15NuB1R9YHw5W1UfKOI3+BjTQrClWC/G6eA1aWO/QpI=
=ufzp
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: E365 hardcopy

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 31/03/2012 17:03, Phil Dobbin wrote:

> On 31/03/2012 14:23, Tony Mechelynck wrote:
> 
>> On 31/03/12 13:38, Phil Dobbin wrote:
> 
>>> Out of the blue this morning my Debian Squeeze Vim (7.2.445
>>> console=huge GUI=gtk2+huge) has started throwing the hardcopy
>>> error:
>>> 
>>> `E365: Failed to print Postscript file`
>>> 
>>> this is on both the GUI & console Debian supplied Vims.
>>> 
>>> Apt hasn't downloaded & installed any print updates recently &
>>> I can print the same test files from gedit, etc.
>>> 
>>> Last time I had this on setting up Vim on Fedora it was a
>>> print preferences error (different name for the printer than
>>> specified in my vimrc) but this is not the case in this
>>> instance.
>>> 
>>> I printed from this Vim on this machine a couple of days ago no
>>> problem & I haven't altered my runtime or machine settings in
>>> the meantime.
> 
>> - Any recent changes in the PostScript / groff / other related…
>> packages on your system? - See also ":help print.txt" and in
>> particular: - :help print-intro - :help print-options

> No, nothing has changed on the system (only nagios has been
> installed & that came without the print monitor option) & I've read
> & re-read the above help files several times but nothing in there
> seems to be relevant.
> 
> `h: E365` isn't much help either I find, so I'm stumped. I have
> exactly the same runtime files on my Vim in OS X & that's OK so
> that probably excludes a plugin problem.
> 
> I'll have to run `dpkg -l` & sift through that to see if I can
> spot anything blindingly obvious but I'd've thought if that was the
> case all the other apps that I can print from would suffer too (lpr
> can print from the command line too).


I solved the hardcopy problem by commenting out the `pdev` line in my
vimrc. Why Vim decided it was no longer correct is a mystery. It
hadn't changed for months. I can only surmise that a fractional change
in something somewhere caused this but I haven't been able to trace it.

Before, Vim wouldn't print without it, now it won't print with it.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPd5b5AAoJEKpMeDHWT5ADxO4IAIRf2K1GfTxl/xdKbD2Sklml
/wqZjzv0Hz2mOQzGKzyEQ438aB5nDH3TfgjW9T5bTlIkOepvkjA/B7F8++1twGr1
GliU35r+3KzazkqkZW3comHDbwct9t9XTXyRVKkZ0z4GZLOq3m1R8xDpemiKwojn
jAPxjuZPTaX2VQw9dUUyDDLIyO4+ilYWrrYKK93LHqMusU7zhmWrUa7e+HC41Qr/
MOsNjrne02msXY5Kf6SMvO9LDcWSfa3O4aaJ5OdnrC4+1xgGF27A7ibGSbMjkK93
oN5nK2Q7rcoNnujclJXHhXzkYJnLglRUd4LQL9Nbiua7g7XZQ9Pofb5/6ULC1nk=
=eup8
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Switch to unicode.

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/04/2012 15:55, john Culleton wrote:

> I am having a problem with Vim line returns being interpreted as
> end of paragraph markers in Scribus. Unicode may solve this
> problem. What string do I need in .vimrc to switch to unicode?
> 

`set encoding=utf-8`

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPeG3VAAoJEKpMeDHWT5ADnt0H/jhNeMP4PMshOpOQGTjtRNlo
W04LeZ5zYqzLr7C1EVWd0h6SsIqOvKJ6G4YMKTIMW7Kd/yWPM7F/+H/qoYaozVr7
L/UAAuqU1jxoxTaOXFUGqw5uanb1xO5+/RPk+gs42/pZDc3q3spkSnkzFkdbmu6n
VtKhv5fmtaIbyH5Psztl+oCtMWGccpVS0RcfdqGUXDdftmnZOZU+y3pyt3ORBklt
mjXaSCgH/qL0CYNp0YzWIMaL/BQiSqkqbojxhAez68lnfz7SjxKuDiuJXXbaM300
H5UhdBxkqWPHd7mAF8f2A6gvmgbnmotaq7+rvHXm5n6O9t8S5DT+blqKdFjpJRY=
=Vw5C
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

I downloaded a jolly good pdf of the Vim :help manual:



the other day & the thought struck me that, to my knowledge, no hardcopy
of same is in existence.

Has this idea ever been mooted? In my opinion, it would be excellent to
have the reference manual on my desk & it would have the added benefit
that some of the proceeds of the sale could be used towards the ICCF
Holland foundation too.

The recent thread about reading the help pages in tabs & so forth
highlighted the need for one to me & there is certain documentation that
always merits being committed to paper.

Just a thought.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPecdWAAoJEKpMeDHWT5ADmzQH/3dgN2shHK1CB0ZPxe+VgmA3
rIv+a67N0hCq7IDvx/m3AUdnHq8ReAoZyq9NQmAId1A4vvKQvfkVSfquQtO86EIV
wDxU42zkp+TFURyR6eP+5GQZQkB7srnScaBUod0HmvB9/cMkN1nC37MUIE8L4eF1
US1uHZHWAm2zO35eqLArX//NVHNfqXxMDR1t42M6X0mj6KVXyZhfMSkX39VDOM2L
SiMzx8Jo02zSJO2SccIIrXyGV9Oz5VApILajh8Ar1/74YsQ82d5W0+vV46eQf6Db
92aeUhJhFHJ2IN+UaIWG0aQfQts0E0N/L5RQvHXqqCRcv9fUoLukYb8DbnsvbBE=
=H1mZ
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: syntax highlight and indent awk code embedded in bash script?

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04/04/2012 22:02, Peng Yu wrote:

> On Wed, Apr 4, 2012 at 3:56 PM, Gary Johnson  wrote:
>> On 2012-04-04, Gary Johnson wrote:
>>> On 2012-04-04, Peng Yu wrote:
> :h sh-awk
>
> this is only for syntax highlighting. I am not sure, if this is possible
> for indentation scripts.

 Hi Christian,

 The above help page is not found in my vim. Is it available from some 
 plugin?
>>>
>>> It's in the $VIMRUNTIME/doc/syntax.txt file for 7.3.187.  I don't
>>> know when it was added.
>>
>> s/187/487/

> This is my vim version number. I'm not sure where is the number after
> 7.3 is. Is it 462?
> 
> $ vim --version
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Mar  4 2012 01:03:54)
> MacOS X (unix) version
> Included patches: 1-244, 246-462
> Compiled by root@peng-yus-macbook-pro.local
> Normal version without GUI.  Features included (+) or not (-):

[snip]

That's odd. I have virtually the same OS X console Vim (7.3.462) & I too
have no help for sh-awk. However, MacVim (snapshot 54) on the same
machine does.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPfLo4AAoJEKpMeDHWT5ADu8EH/20Ztrr7w/dcO9GmiUSPdnV1
J3HmueVg53xw+TO8596Wx6YBiBYh17e/NYG9wmXGOXq9ojrKO9Wxs00lRndJoQLu
y6eaFLDxfPF5e2vxaFAkYuWPcwVN1q19gKVpfNjxKthblxodVhD0vBfTwedE+TdX
gbRW9k/VO9Uv9+r15J76jcLzbFpHdlCUhShx4b83jD532DjICCKTi0d6kfGtXGPm
WzQ+T2TdnXRO37IlGMTSCoz+J7DsmjzrRceOmY05mp2GkPfJ14RJAEyWbpa0CdgT
W9xNjChvITUj5BpJ8GGWJKUEntGRhIf2Y9uYihyUXY9FStZlUgrTwasPrlbNpdc=
=hb/Q
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/04/2012 21:14, Boyko Bantchev wrote:

> On 5 April 2012 22:17, Sujith Abraham  wrote:
>> In this respect Emacs wins. They have a much more beautifully rendered PDF 
>> manual. In comparison, vim manual in PDF look amateurish.
> 
> The Emacs manual is written as a book and typeset with TeX (TexInfo).
> Vim manual is just an aggregation of the help files -- no wonder it
> isn't a masterpiece of the typesetting craft.  But Vim manual is also
> about three times shorter, which is an excellent advantage.  Let
> alone Vim is the much better editor :)

When I posted my query as to why there was no existing hardcopy manual &
Bram responded with a link to lulu.com, I looked at the site & it seems
to be a viable option to get the book printed.

There doesn't seem to have been much of a positive response however to
the idea in general so taking that into account if the vim list is
ambivalent towards it, I'm not so sure it'll pan out with anyone else.

It wouldn't take an Everest type effort to typeset it to a degree (Lulu
accept pdf files) & it should, of course, look as well set as possible.

I noticed the Pragmatic Programmers series of books are releasing a Vim
book in beta form on the 18th of this month which I think will do well &
judging from the burgeoning social networking circles (twitter, gklist,
etc) a great many programmers in what was used to be called Web 2 are
using Vim/gVim/MacVim.

As for emacs, I just tried it for the first time. Gave up at `C-u 8 C-v` :-)

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPfg9QAAoJEKpMeDHWT5AD3HQH/24fbNDLtmXCbtSX7x9GpUyN
A8E5cLuIkczlxRpp8/wVz76kxI571/h7s+PJslePmzI8Wkqscg2B7aY1MKDuOlc0
PtTNqdXkz/tuyr/pZsNr2kHa/EovdHDzcab1dbA9AllODJtL+riPiCvFbVeDVEEI
C+rszUqMplsT4k5U4qgZqOgQdEybxKHIH12O25nDfsRHMNx0zGf0DtfCArdewFOh
aSxNutaHf914CmwamwD/lXkxDN4Lqp47Xm1dhFVRbWG+il8YdZIRvUfGroZ6Djd0
OqflO956ITJquzpDRGJ9j6+H01glBpHIBCQHrIvzOh9IBHebLvTbZtoDcDleB60=
=qXor
-END PGP SIGNATURE-

-- 
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 information, visit http://www.vim.org/maillist.php

Re: Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/04/2012 16:59, Andre Majorel wrote:

> On 2012-04-05 22:32 +0100, Phil Dobbin wrote:
> 
>> There doesn't seem to have been much of a positive response however to
>> the idea in general so taking that into account if the vim list is
>> ambivalent towards it, I'm not so sure it'll pan out with anyone else.
>>
>> It wouldn't take an Everest type effort to typeset it to a degree (Lulu
>> accept pdf files) & it should, of course, look as well set as possible.
> 
> A straight conversion to PostScript of the help files would not
> be very difficult but it wouldn't be very good either.
> 
> I've written a hack that darkens the colours and replaces the
> default font by something less rotten than courier (my beef is
> not with the fixed spacing, it is with that particular font).
> 
> psbind -2 to print 2-up (4 pages per sheet).
> 
> To do : a form-feed per chapter, global page numbering and
> everything else I'm forgetting. Maybe a page number after each
> link but that would mean reflowing.
> 
> The manual is not very useful without the reference, IMO.
> 

I've also been looking at Pandoc (been pretty busy of late so haven't
had much time).

I'm still very keen on the idea however so if you want maybe we can pool
resources (along with anybody else of course)?

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPhGGbAAoJEKpMeDHWT5ADcJQH/1txoH3bveWjzqf1zV0gwl9x
gvOjKVtlR6Xj1cEjKQD77+ZCMYR6MwcTdCgEmZA7TnIxzjf9UYkgBvSXkUhzF3xe
0EUINaz2KtBWVrhFa0apjoSKa265GgUhb1WDJyiqshAafmOvyMKmdnUu4B5YAbW+
EcQ9kmr8nevPkZpquvwSh3voOgnIMQd4T4zNQhzFWhCz7uQiLi+NgF1mDfHweq7L
yHW/x5rRA6WMqOVHrIfFDwi7T5zMHKhDrFaD5kZpXxqmkG5tbD/ELZ9CwSgO1dip
PSuRxux2XINzcjV2mbixtV0SlQtBeAUE/IeEOYOpo4U7hr1fCSWDTriJhmUiMKs=
=olUF
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/04/2012 18:12, shawn wilson wrote:

> I think beautifying vimdoc would be a good thing (though I don't really
> dig the dead tree version). I think maybe even expanding it so that it's
> more book like (maybe with examples from the list / web) might even be a
> good thing.
> 
> I think a starting point would be to decide on a document format (tex
> probably?) and a conversion process so that the book is easily updated
> with the upstream? ... and a git for this to live (someone's github
> probably).
> 
> I worry about the process of design by committee though... if I have a
> pull request where I use some font, who decides if its good or not?

I have four github accounts so that's no problem. One is actually unused
with a name that is non-specific to me. If it was to be made into a
Vimdoc repo & named as such specific to say this list, it could be extra
work handling pull requests although I think that that may be a good
thing as that would help with the adding of examples & such if that idea
was decided upon & better in general for the building of the book.

I think the design by committee wouldn't be a problem. Input is good,
natural & healthy & I think Bram should be the final arbiter after all.

Putting the documents (manual & reference) into tex I think is the best
way to go & will result in a much better looking final PDF from which to
print.

Cheers,

  Phil...

> On Apr 10, 2012 12:36 PM, "Phil Dobbin"  <mailto:phildob...@gmail.com>> wrote:
> 
> On 10/04/2012 16:59, Andre Majorel wrote:
> 
>> On 2012-04-05 22:32 +0100, Phil Dobbin wrote:
> 
>>> There doesn't seem to have been much of a positive response
> however to
>>> the idea in general so taking that into account if the vim list is
>>> ambivalent towards it, I'm not so sure it'll pan out with anyone
> else.
>>>
>>> It wouldn't take an Everest type effort to typeset it to a degree
> (Lulu
>>> accept pdf files) & it should, of course, look as well set as
> possible.
> 
>> A straight conversion to PostScript of the help files would not
>> be very difficult but it wouldn't be very good either.
> 
>> I've written a hack that darkens the colours and replaces the
>> default font by something less rotten than courier (my beef is
>> not with the fixed spacing, it is with that particular font).
> 
>> psbind -2 to print 2-up (4 pages per sheet).
> 
>> To do : a form-feed per chapter, global page numbering and
>> everything else I'm forgetting. Maybe a page number after each
>> link but that would mean reflowing.
> 
>> The manual is not very useful without the reference, IMO.
> 
> 
> I've also been looking at Pandoc (been pretty busy of late so haven't
> had much time).
> 
> I'm still very keen on the idea however so if you want maybe we can pool
> resources (along with anybody else of course)?
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPhG+/AAoJEKpMeDHWT5ADg5oH/0kBEtwrySExCsoLaiTvpKkE
YIc0ws4/ljQ62C5hw5/g8WzWuHpE/jdjBMQQtk3bbUJGiOcs8PMjXxjH+GACuThE
paQ9B8Mzvp7wsMOiYTJUBM3nQPSKD+owmWoGKWJXMvh13h4bWN9FEJHMECfjf/oa
T19pJOntCxMX6j6ESf9KsNaO4ukfyUl/BjqwDUkoc2Cl0OfA3p5FdwtCudo7fMQg
K7/7KX2xXsR/HEm9cKxmUX0NY/P/w9vJh7RRaVvSwsWszQyDQQPw32GLmdKp+4KV
UjGu2u+S9PlZHR6bArG+9dlz4Jcx5F3QXS20x7V8/+FNbG3DRx8Rkfbz2vv/vyU=
=Yycf
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/04/2012 22:01, Andre Majorel wrote:

> On 2012-04-10 18:37 +0100, Phil Dobbin wrote:
> 
>> Putting the documents (manual & reference) into tex I think is 
>> the best way to go & will result in a much better looking final 
>> PDF from which to print.
> 
> What do you have in mind ?
> 
> If you just put all the text in a giant monospace verbatim, it 
> won't be much better (or worse) that the output of vimpspp. Page 
> breaks and page numbering may be easier, though.
> 
> If you intend to reflow the text, there is much to gain. But then 
> you need to know what is, in HTML parlance, , what is  
> and what is neither. Dunno how easy/hard that is.
> 
> In any case, it's essential that the process be as automated as 
> possible. EG, program reads /usr/share/vim/vim*/doc/ and spits out 
> {man,ref}.ps. Otherwise, the files will always lag behind.


Well, I have this crazy idea of taking the plain text files, flowing
them into markdown, then converting them into tex to be typeset & then
generating a PDF ready for print.

All perfectly possible using Pandoc, Vim & Lulu, just a question of
how viable it is.

Any thoughts appreciated.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPhc5xAAoJEKpMeDHWT5ADNiQH/jNcpvoVag3TWuA1NQF9M1Xy
JcGlKCIugh13fAUOorVvjZqerQeH0cYhuONbthwxWGb/4tRrw1b4JIvFRNI9NAFV
vg3G8VFLfnAT9DZhIiUJ4MNUYqkoJh6AD90ynEg9aiecW9vuu6tz61pvl7qYGxS9
aSx04+Q0GIkfNLE+RtjtmGLbtnPFjxnOg41BEcQcxXcpSRUtctSnQLziwJZXRZgA
QpIT+H4dco3VES0KBkVKrIATCdQo5YasojFF6KGtzmwtMf2YZPJHiH2o0t0/0SHt
24aCG2JwfZIWnGXSSpo9o5WbNaVim36rph0+a3FA9zVulpZsKr10icOlyVbdFc0=
=G1hG
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Current Vim Versions [was: Re: How to search in digraphs?]

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/04/2012 18:00, Benjamin R. Haskell wrote:

> On Thu, 12 Apr 2012, Boyko Bantchev wrote:
> 
 Your version of digraph.txt is not in the compiled versions
 of Vim distributed from vim.org.  It is not even in the
 source packages for those who would compile Vim themselves.
>>> 
>>> It is. I provided the patch and Bram committed it to the
>>> runtime files
>> 
>> No it isn't, effectively.  It is nowhere in the exe or src
>> packages on http://www.vim.org/download.php or
>> http://www.vim.org/sources.php, which are what almost all users
>> of Vim use.
> 
> [This comes off as more argumentative than I'd intended.  The
> points that matter are the questions at the end.]
> 
> I'd argue that those are not "what almost all users of Vim use". 
> Definitely not those sources.  If you're compiling from source,
> rather than using http://www.vim.org/sources.php, current
> development uses Mercurial (See: http://www.vim.org/mercurial.php
> ).
> 
> If you're not compiling from source, most O/S distributions add to
> those versions the patches that have been released since those were
> packaged.
> 
> E.g. the source package from your second link is for Vim 7.3 (with
> no patches).  O/S'es that are actively maintained usually have
> something much later than that.  Gentoo is at >= 7.3.266, OpenSUSE
> is at >= 7.3.322, MacVIM is currently at 7.3.390 (despite being
> called "snapshot 64"?), Ubuntu 11.10 has 7.3.154.

[snip]

Just to add the latest Vim from current Debian (Squeeze 6.0.4) repos
is 7.2.445

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPhw+mAAoJEKpMeDHWT5ADlmgIANSacoscA6hODzuxHLjtYVfq
bAZ5/LrLpHg/04+wfJdvDbYw6se5v0CPwt+rnZOBvTEwXguJWvwbaQUN3gpkY3tt
9C4D0/0y+FcCH6ykw7G5PXN7XvWwe5p30Jhhl37v5V9MMSbfpH1Ph/l8MeAKXXFK
Ygq2fDHqeuZ9f7RlL2vtplU01VP9o1/zlNl7He8pLt4CKw0rgMFGMETAmdLZcL3f
etqXaUoRvjHFWqQGjrrSm9kE4dt+1+G9i3sFmG3WiVwIKl7Ud38TFH4LRAI50fR6
5WJ7M/dA2plyJpOXTHCa/Tm5fR36hrgsd4XZamx/7x2NvcUTuM0h8wc844nVPJE=
=zcC5
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/04/2012 06:17, Paul Isambert wrote:

> Phil Dobbin  a écrit:

>> On 10/04/2012 22:01, Andre Majorel wrote:
>> 
>>> On 2012-04-10 18:37 +0100, Phil Dobbin wrote:
>>> 
>>>> Putting the documents (manual & reference) into tex I think
>>>> is the best way to go & will result in a much better looking
>>>> final PDF from which to print.
>>> 
>>> What do you have in mind ?
>>> 
>>> If you just put all the text in a giant monospace verbatim, it
>>>  won't be much better (or worse) that the output of vimpspp.
>>> Page breaks and page numbering may be easier, though.
>>> 
>>> If you intend to reflow the text, there is much to gain. But
>>> then you need to know what is, in HTML parlance, , what is
>>>  and what is neither. Dunno how easy/hard that is.
>>> 
>>> In any case, it's essential that the process be as automated as
>>>  possible. EG, program reads /usr/share/vim/vim*/doc/ and spits
>>> out {man,ref}.ps. Otherwise, the files will always lag behind.
>> 
>> 
>> Well, I have this crazy idea of taking the plain text files,
>> flowing them into markdown, then converting them into tex to be
>> typeset & then generating a PDF ready for print.
>> 
>> All perfectly possible using Pandoc, Vim & Lulu, just a question
>> of how viable it is.
>> 
>> Any thoughts appreciated.
> 
> If you're willing to use the latest engine LuaTeX instead of TeX,
> I have written a package called Interpreter whose job is to
> translate input files on the fly before TeX reads them (but during
> the TeX compilation, it is not a preprocessor, LuaTeX lets you do
> that). The obvious application (and actually, my motivation) is to
> be able to write source files without TeX's \commands and
> \what{ever} (I haven't used those for quite some time now); feeding
> the Vim's manual directly to TeX that way is something I'd been
> thinking about, but never done. The problem I fear is that the
> syntax isn't unambiguous, but it'd be worth giving it a try.


Hi, Paul.

Yes, I'd be very interested in trying that. I have LuaTex installed
alongside Tex & texlive on both my production & development boxes
(Debian for Prod, OS X for devel).

I don't know everybody else's opinions on the subject but we could
set-up a GitHub repository maybe to try the ideas out. I'm amenable to
any suggestions.

Let me know what you think.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPhxn4AAoJEKpMeDHWT5ADIu8H/1BxgvkG2WZKbbzdyolwoSho
g0awDBQUrCi+BF1fK02W/re0j71TyBrnTvQE/9c6dZqlOQz+k5kqPk6HfdMk4kV1
0a0fafR8c6J/W6ekS99Vp0ZAdfFcXjFhniqBzuhbgno2l58ptfnoLkhWNtlGVOvY
SvAZLz9Ua3ei+OpzhCJ6FTtV3Qf15K04qk24oiWG72pT35RZM9WlOcxHfdZ5pHuv
IRhFO+sg8zCa4NDUxuJf+OW+uy/juRmU7/w1qKTBTKBF7p9Etvgz93GCBDgHh+c7
r1nDTF8x133wrMw+i3x5fPAKWRHN0qtKiKSQ53niZE4yv5tqFB9j7HS1vhTj9Og=
=cDHi
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Vim manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 13/04/2012 06:56, Paul Isambert wrote:

>> On 12/04/2012 06:17, Paul Isambert wrote:
>>
>>> Phil Dobbin  a écrit:
>>
>>>> On 10/04/2012 22:01, Andre Majorel wrote:
>>>>
>>>>> On 2012-04-10 18:37 +0100, Phil Dobbin wrote:
>>>>>
>>>>>> Putting the documents (manual & reference) into tex I think
>>>>>> is the best way to go & will result in a much better looking
>>>>>> final PDF from which to print.
>>>>>
>>>>> What do you have in mind ?
>>>>>
>>>>> If you just put all the text in a giant monospace verbatim, it
>>>>>  won't be much better (or worse) that the output of vimpspp.
>>>>> Page breaks and page numbering may be easier, though.
>>>>>
>>>>> If you intend to reflow the text, there is much to gain. But
>>>>> then you need to know what is, in HTML parlance, , what is
>>>>>  and what is neither. Dunno how easy/hard that is.
>>>>>
>>>>> In any case, it's essential that the process be as automated as
>>>>>  possible. EG, program reads /usr/share/vim/vim*/doc/ and spits
>>>>> out {man,ref}.ps. Otherwise, the files will always lag behind.
>>>>
>>>>
>>>> Well, I have this crazy idea of taking the plain text files,
>>>> flowing them into markdown, then converting them into tex to be
>>>> typeset & then generating a PDF ready for print.
>>>>
>>>> All perfectly possible using Pandoc, Vim & Lulu, just a question
>>>> of how viable it is.
>>>>
>>>> Any thoughts appreciated.
>>>
>>> If you're willing to use the latest engine LuaTeX instead of TeX,
>>> I have written a package called Interpreter whose job is to
>>> translate input files on the fly before TeX reads them (but during
>>> the TeX compilation, it is not a preprocessor, LuaTeX lets you do
>>> that). The obvious application (and actually, my motivation) is to
>>> be able to write source files without TeX's \commands and
>>> \what{ever} (I haven't used those for quite some time now); feeding
>>> the Vim's manual directly to TeX that way is something I'd been
>>> thinking about, but never done. The problem I fear is that the
>>> syntax isn't unambiguous, but it'd be worth giving it a try.
>>
>>
>> Hi, Paul.
>>
>> Yes, I'd be very interested in trying that. I have LuaTex installed
>> alongside Tex & texlive on both my production & development boxes
>> (Debian for Prod, OS X for devel).
>>
>> I don't know everybody else's opinions on the subject but we could
>> set-up a GitHub repository maybe to try the ideas out. I'm amenable to
>> any suggestions.
>>
>> Let me know what you think.
> 
> For the GitHub repository, I have absolutely no experience in that, so I
> have no idea either. Otherwise, if we're going to use Interpreter, then
> the first step would be a description of the syntax of the Vim manual,
> so that I can start writing an ``interpretation file'' (which gives the
> translation between the input and the TeX output) as required by the
> package.

- From the Wikipedia entry for GitHub:

'Git is a version control tool. Github is a "web-based hosting service
for projects that use the Git revision control system"'.

It has many similarities to SourceForge & similar operations. It's
greatest benefit is that not only can you check in your code to version
control but you can then have a mirror of your local repository at
GitHub so that other collaborators on a project can also "pull" code &
"push" code to the project thereby obviating the need to send emails
with attachments back & forth & so on.

There are two types of repo available: free which read & write enabled
for everybody but in order to make changes to the repo they have to send
a pull request to its owners or paid which is read only but pull
requests can still be sent.

Either way virtually all repos on GitHub can be obtained by using "git
clone".

Git itself is very to install (they do packages that are binaries if you
so wish) & it is available from most all package managers/distros.

As for a description of the syntax, do you mean as in a SOL (Simple
Object Language) description or something along those lines?

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPh9v4AAoJEKpMeDHWT5AD8KIH/2u6p1Pa5wdwVw8X+9y7fqsP
er5vyK/Ddk+iwxWZSc85KUh6Vf72wh4Z6jEJOAT1nZw9UHQdPQMfF37B7e9UYChc
L3cSwYKOg1/chkA9JiZG3WXwMi+Pjkn64lShG0csl0ZfPpPa4fmvkbuf8h0UB/Vp
9WPw0HoIRNQUncz84lYI9XREOxYqkKPJVKPswIPGsgIFfF+EmYeuIKo0CCBBvNgn
7XwTPzR0AaI9j2A4n+WdNbSGMJa3pZveyYc+7tnAsOn0suWmQEZU1XQ7hXPyvcdm
rexxflTfxWVujLMpUW6mCqZWHTxjX0eB998VsQerIxY3LtaNhRIHZavrpJbpXQI=
=FRrn
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Vim User Manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, all.

I posted several weeks back postulating about producing a hard copy
(or dead tree if you so wish) version of the Vim User & Reference manual.

I'm very pleased to announce that Paul Isambert & I have agreed to
embark upon this project. Our aim, aside from producing the manual, is
to collect all revenues from the sale of the book & direct them to
Bram's Ugandan charity, ICCF Holland.

Paul & I have just finalised an initial production cycle & work will
commence shortly. Should anybody be interested in helping in any way,
we would be delighted to welcome them on board. Please feel free to
contact me directly if this is the case.

I will endeavour to keep the list posted with any updates as they occur.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPjwQeAAoJEKpMeDHWT5AD5qQH/0uF9u7KpalSFmnCEoiDdJZx
ZOpejBeUFe3UsX5df/FkMQ2R/k8X8wt66H1Ob9jYweiJ/JHq9vfQOr1OiVF2Mtuc
YCrxm5oXhDmXIM4XaP1zfFLq3smOHlFMF/+Hzr+AEpK6W/9FEBVT56pZ7cSkU/gI
qRs6M8A0trENVQb3r2GaIDFtWxfnPOAsRSw4vscLe1Bp8aqipg0wYQwbdUu/4MLQ
vsBPtfn1rTprbA5Q9gZcnJ6HugoqQkfiDXArhd5teN2js454KsALNY0LAICDMkzb
sQkTHro3poNT+kGT0N1/1yziH9Z8vGYyatTCpcVWVIAuKtTwm+TptZIiDR9Bozc=
=m4D5
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Vim User Manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 18/04/2012 21:56, Bram Moolenaar wrote:

> Phil Dobbin wrote:
> 
>> I posted several weeks back postulating about producing a hard
>> copy (or dead tree if you so wish) version of the Vim User &
>> Reference manual.
>> 
>> 
>> I'm very pleased to announce that Paul Isambert & I have agreed
>> to embark upon this project. Our aim, aside from producing the
>> manual, is to collect all revenues from the sale of the book &
>> direct them to Bram's Ugandan charity, ICCF Holland.
>> 
>> Paul & I have just finalised an initial production cycle & work
>> will commence shortly. Should anybody be interested in helping in
>> any way, we would be delighted to welcome them on board. Please
>> feel free to contact me directly if this is the case.
>> 
>> I will endeavour to keep the list posted with any updates as they
>> occur.
> 
> That sounds great.  Thanks for taking the initiative.
> 
> I suppose you will need users to proof-read the result?  Perhaps
> we should start with one file that is not long but does contain
> some challenges.

Hi, Bram.

Yes, proof readers would be of great benefit.

Paul & I are working on a system of appropriate markup for the files
that can then be sent to the interpreter for conversion.

I've created a GitHub repository for use in the project & I suggest
when we have a test file ready to commit to it, people, if they so
wish, can clone a copy of the file in order to proof read it.

As soon as the first file is ready, we will advise my email & gladly
accept any help, advice, constructive criticism & so on.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPjy8YAAoJEKpMeDHWT5ADWDkH/0Wwp80w9UUhoiL0mbRgRhNS
kUKrxCpEyBoce6PDX/cDnJ/zfavGJbdtZUdX26yCzBYOzF/TZtJbG2kD7sr1i9h6
k8v/t9PeG/6RbJXKQBHttd5xleAvHHgtGg5hl2nZ4W2ODzJhAzxeiSxRWwphkVrF
yyl6EBBBX5XMQ43GKhU00uxQBshxz9z4sFJiYs+PNeReMnrMZKbJleFb1A8pb/B+
ZhZJyUBgI1pIrn8DuQjDsQn34VYuEXh8Sl1/MlFW2LqDTbtUFLntZ9cviwYqnqk2
R153L/jrCYBluMbeUOR2mUGuwWYToQrTumkUKBYmU61f6+/S3f9LE3hqv+3cvMM=
=xBXB
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Vim User Manual

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 19/04/2012 19:29, Charlie Kester wrote:

> On 04/18/2012 09:27 PM, Paul Isambert wrote:
>> Phil Dobbin  a écrit:
>>>
>>> On 18/04/2012 21:56, Bram Moolenaar wrote:
>>>
>>>> Phil Dobbin wrote:
>>>>
>>>>> I posted several weeks back postulating about producing a hard
>>>>> copy (or dead tree if you so wish) version of the Vim User&
>>>>> Reference manual.
>>>>
>>>> I suppose you will need users to proof-read the result?  Perhaps
>>>> we should start with one file that is not long but does contain
>>>> some challenges.
>>>
>>> Yes, proof readers would be of great benefit.
>>
>> Indeed. Actually, although proofreading at an early stage may be useful,
>> it's not there it's going to be crucial, I believe. The first file(s)
>> we'll probably check ourselves, if only because we'll be testing the
>> translation process. Now, when that process seems ok, and we start
>> translating files massively, then we'll definitely need people to read
>> the PDF's and make sure they're fine in themselves and with respect to
>> the
>> original text files.
> 
> Add me to the list of volunteers for proofreading.
> 
> Will you be sending the PDF's out as attachments to email, or is there a
> site where they can be fetched?

There is a GitHub repository where the files can be forked when we reach
the proofreading stage.

Also, thanks to all who have so far volunteered their services. It's
very much appreciated.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPkHLIAAoJEKpMeDHWT5ADePAIAJfLggCZWx+IHeR/aDG7+WNQ
AFSmL9TsGMst/IXDhsmLbk4DjBHBQFau0if+BEDWNA4/VqCnL81hhMKOY4ZaULE3
HjuPdhI9yWeCquNNR2EfglhmOGfTsyr2v858g6OejLcvKd9xwxriv3uGmC3wzS2w
2zFh1xvRrY7YbUdRLsQR2BRmuPrkbBaiqFFlzGNlBnJzvNxy8+ra3YagTfH3ljDw
xXDWZ9+YpsU9vKf4f6XOuo+cC29cVBoAqicIIUMWuaEYXK7Pv92I+qiERXpO+r8I
rX9f8KXe/uqcVwviC9PL1jGDiRSBU9RD5VQMNULXo6sfB2/wE5mcUjkFogI4tDY=
=/DV+
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: _vimrc

[Phil Dobbin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/04/2012 06:05, hilal Adam wrote:

> I an not sure if this an acceptable request or not. My apologies if not.
> Would experts like Ben Fritz, Marcin, Jurgen share their vimrc files
> with this forum?

If you go to GitHub & enter vimrc as a search term, you'll get quite a
lot of results.

Not sure how many of the regular contributors to this list commit/backup
their dotfiles and/or $VIMRUNTIME directories on GitHub but a lot of
well known Vimmers (Steve Losh, Tim Pope to name but two) do & they are
most instructive in their content.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPkQGkAAoJEKpMeDHWT5ADZk8IAKVxOkyX4pw6ZdjNInrPL9gS
rpaatAPordKVSPDJr1jNpAGpl6lOa3kbgrVcrMmnp+NynaaWbqiolXHo0ZMAte+J
UdRlaqE854/rhhrdmkKnnLT7j2LZ/a8gOletX+8rfwAtL6/ieh+lK1rL9VGu4x5u
/4xT/OuPJtOCMKCaWpQQMH2xi8YZ2FuSoEATbNdscieglwWBhiP+H2Kz00p0NdrT
tM5vLXlSAKlaLpWAoakK8fg4obOD2mWgORvh6RGxcMJaEBnevKYpBD0P6NP6Yq0+
HAH3ImL4OwpTZvDEi8cMG7PTaFnMsP9c24AbVCr3dIJmksRkenPLOLCC+gqVx9E=
=H+La
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature

Re: why is it so difficult to start using vim (may be just for me).

[Phil Dobbin]

Deepak adhikari wrote:
> I am trying to use this editor, searched stackoverflow.com
>  (didn't ask though) went to vim.org
>  but very complex operations are explained and found
> difficult to grasp.
> 
> just trying to know some basic commands like how to start, exit,
> save/writeout , delete some specific lines. Remove BOM form the utf-8
> file(going to the beginning and deleting this bit)
> 
> I seem to not find the basic structure of the commands
> 
> I could see
> 
> "vim [commands] file ..
> 
> 
> now in commands I am confused, what if I want to merge two commands
> together.
> 
> Lacking the information on how to load a file in buffer, as it talks a
> lot about it.
> How does it generally operates merging commands, writing out, deleting,
> combining these commands ,
> searching some texts from a file.
> 
> yesterday I wanted to use vim, and tried to learn it.
> 
> basically what I exactly wanted is>>
> 
> remove BOM from utf-8 encoded file, remove 2nd line of the text file
> which was imported from windows machine.
> 
> 
> thought it must be simple to use with such a famous/powerful editor but
> I am lost in the complexity of its features  talks about vim, Ex,
> vi, command line, visual, so many things to see just to get something done.
> 
> I would like to know if there are any start up guides, for users who
> came from nano or some other editors ...
> I am not used to editing texts from command line, but now is needed so
> wanted to learn.
> 
> hope some of you will not mind to reply me in more simplified manner ..
> with some examples ... and in detail ... from starting it to saving it,
> and exit (of course)
> I hope it is not too much to ask.

I personally recommend Practical Vim:



Cheers,

  Phil...

-- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing




signature.asc
Description: OpenPGP digital signature

Re: Strange issue with Pathogen

[Phil Dobbin]

Rostislav Svoboda wrote:

>> I'm having a strange issue with Pathogen. I'm trying to keep my Vim
>> configuration and plugins organised on several computers
>> so I decided to create a git repo for it.
> 
> I had the same problem and realized Vundle works for me better than pathogen

I second the suggestion to use Vundle.

I keep my vimrc in Github & then clone it to any machine I'm going to
use (after cloning Vundle, of course) & then run `:BundleInstall` &
there's my plugins.

I also keep my colors & syntax directories in Github & a couple of
plugins that don't really work via Vundle (i.e. toggle_width.vim for
NERDTree) & a very basic bashrc which adds full color to the terminal
for Powerline, etc.

I've used it on CentOS, Debian, Fedora, OS X & Ubuntu & they all work
but not Windows 'cause I don't use it so have never tried it, so I can't
comment.

If you want to see it, it's at
.

Cheers,

  Phil...

-- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing




signature.asc
Description: OpenPGP digital signature

Re: basic vim usage

[Phil Dobbin]

Fredrik Andersson wrote:
> 
> 
> On Thu, Nov 8, 2012 at 1:37 PM, vicky b  > wrote:
> 
> no  i dont want to use GUI , i want to use vim not gvim  how can
> copy and paste with ease in vim
> 
> 
> y for yank (copy)
> p for paste
> 
> Use the * register to yank/paste to/from the system clipboard.
> 
> This should be covered in the vimtutorial, run vimtutor if you have not
> done so yet.

Also, depending on which term you are using (this works in
gnome-terminal & konsole), you can select the text & then use
ctrl-shift-c to copy & ctrl-shift-p to paste if you get really stuck
and/or confused initially. And that works across all consoles you have
open, local & remote.

Cheers,

  Phil...


> On Thu, Nov 8, 2012 at 6:05 PM, Karthick Gururaj
> mailto:karthick.guru...@gmail.com>> wrote:
> 
> 
> On Thu, Nov 8, 2012 at 4:53 PM, vicky b  > wrote:
> 
> I have started to learn vim in this modern enviroment where
> gui takes prefers , one thing that still me back to other
> editors is the ease with which we can  copy and paste , can
> anybody help me out with safe effect in vim or any thing of
> that sort
> 
> If you are using gvim, you have the option of clicking on "Edit"
> -> "Copy" and "Edit" -> "Paste". You need to select some text
> first obviously, before copy. Selection can be done with mouse.
> Using CTRL-C and CTRL-V might also work for copy/paste - whether
> it does work or not depends on a few factors.
> 
> It that the answer you were looking for?
> 
> Also, if GUI is what you want to work with, vim may not be worth
> looking at. Just my opinion.

-- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing



signature.asc
Description: OpenPGP digital signature

Re: Is Vundle dead?

[Phil Dobbin]

On 11/24/2012 06:14 PM, Paul wrote:

> I am wondering just how often Vundle updates its list of scripts. I am
> aware that it’s FAQ says “multiple times per day from the RSS feed”¹,
> and the feed says it was last updated on 2012-11-09. tComment was
> updated recently to version 2.07², so I did a :BundleInstall! to see if
> it would update. It didn’t, so I looked on Vundle’s github mirror of it³
> only to see it’s on version 2.05, released well over a year ago! I
> checked the plugin it installed in my .vim/, and indeed it’s using 2.05.
> 
> So now I’m asking myself, “Is Vundle a dead project?”.
> 
> ¹ http://vim-scripts.org/vim/faq.html
> ² http://www.vim.org/scripts/script.php?script_id=1173#2.07
> ³ https://github.com/vim-scripts/tComment

I don't know if gmarik is actively supporting it any longer but I just
add my own plugins to its framework & it carries on being one of my
essential parts of Vim.

Can't imaging Vim without it anymore. It helps me to keep multiple
distros (I run about seven flavours of Linux & OS X) in sync really easily.

Have a look at his github repo & check the issues page out to see if
he's responding to user issues.

Cheers,

  Phil...







signature.asc
Description: OpenPGP digital signature

Re: Is Vundle dead?

[Phil Dobbin]

On 11/25/2012 05:55 PM, Marcin Szamotulski wrote:

> On 08:46 Sun 25 Nov , Chris Lott wrote:
>> On this topic-- is it difficult to move from Pathogen to VAM? Can I
>> keep my bundle directory of plugins but use VAM with it?

[snip for brevity]

As an aside, this topic is starting to generate spam originating from China.

It's not addressed to the list but delivered directly to my inbox (it
has the subject line of this post).

Cheers,

  Phil...





signature.asc
Description: OpenPGP digital signature

Re: Is Vundle dead?

[Phil Dobbin]

On 11/25/2012 06:50 PM, Marco wrote:

> 2012-11-25 Phil Dobbin:
> 
>> As an aside, this topic is starting to generate spam originating from China.
>>
>> It's not addressed to the list but delivered directly to my inbox (it
>> has the subject line of this post).
> 
> It's unrelated to this thread. Since several weeks, I have the same
> issues every time I send a mail to the vim list.


It's the first one I've received. I always check my bitbucket before
deleting & there has been no sign of anything before.

Cheers,

  Phil...






signature.asc
Description: OpenPGP digital signature

Re: email plugin

[Phil Dobbin]

On 11/30/2012 01:30 PM, Reid Thompson wrote:

> On Thu, 2012-11-29 at 17:07 -0800, Bee wrote:
>> If you are looking for an email client
>> that can use vim as the editor,
>> I am happy with Sylpheed,
>> Simple and fast.
>>
>> Bill
>>
> 
> you can configure evolution and thunderbird to use gvim as an external
> editor -  I'm using gvim with evolution to compose this email.

Is Thunderbird integration via a plugin as I can see nothing in
Thunderbird 16.0.2 on Linux to suggest it's natively integrated?

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical, OS
X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: email plugin

[Phil Dobbin]

On 11/30/2012 03:28 PM, Reid Thompson wrote:

> On Fri, 2012-11-30 at 15:12 +0000, Phil Dobbin wrote:
>> On 11/30/2012 01:30 PM, Reid Thompson wrote:
>>
>>> On Thu, 2012-11-29 at 17:07 -0800, Bee wrote:
>>>> If you are looking for an email client
>>>> that can use vim as the editor,
>>>> I am happy with Sylpheed,
>>>> Simple and fast.
>>>>
>>>> Bill
>>>>
>>>
>>> you can configure evolution and thunderbird to use gvim as an external
>>> editor -  I'm using gvim with evolution to compose this email.
>>
>> Is Thunderbird integration via a plugin as I can see nothing in
>> Thunderbird 16.0.2 on Linux to suggest it's natively integrated?

> search addons for 'external editor'

On Fedora 17 & TBird 16.0.2, all I get is 'Saved Passwords Editor' &
'External Email Alert'.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical, OS
X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: email plugin

[Phil Dobbin]

On 11/30/2012 04:01 PM, Reid Thompson wrote:

> On Fri, 2012-11-30 at 15:33 +0000, Phil Dobbin wrote:
>> On 11/30/2012 03:28 PM, Reid Thompson wrote:
>>
>>> On Fri, 2012-11-30 at 15:12 +, Phil Dobbin wrote:
>>>> On 11/30/2012 01:30 PM, Reid Thompson wrote:
>>>>
>>>>> On Thu, 2012-11-29 at 17:07 -0800, Bee wrote:
>>>>>> If you are looking for an email client
>>>>>> that can use vim as the editor,
>>>>>> I am happy with Sylpheed,
>>>>>> Simple and fast.
>>>>>>
>>>>>> Bill
>>>>>>
>>>>>
>>>>> you can configure evolution and thunderbird to use gvim as an external
>>>>> editor -  I'm using gvim with evolution to compose this email.
>>>>
>>>> Is Thunderbird integration via a plugin as I can see nothing in
>>>> Thunderbird 16.0.2 on Linux to suggest it's natively integrated?
>>
>>> search addons for 'external editor'
>>
>> On Fedora 17 & TBird 16.0.2, all I get is 'Saved Passwords Editor' &
>> 'External Email Alert'.
>>
>> Cheers,
>>
>>   Phil...
>>
> 
> go here http://globs.org/articles.php?lng=en&pg=2
> click on the download tab at the top
> select external editor
> download version 1.0.0
> install it using the tbird addons page
> restart
> go to the addons page and select the preferences button for external
> editor
> in the field, type
> gvim -f 
> click ok
> 
> click write to open an new composer window
> click on view/toolbars/customize
> drag the external editor button on to the toolbar
> click the 'Gvim' button
> compose
> :wq
> CTRL-E

Excellent. Thanks very much.

Cheers,

  Phil...

--
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical, OS
X Snow Leopard & Ubuntu Precise & Quantal



signature.asc
Description: OpenPGP digital signature

Re: email plugin

[Phil Dobbin]

On 11/30/2012 06:22 PM, Reid Thompson wrote:
> On Fri, 2012-11-30 at 13:00 -0500, ping wrote:
>> thanks. I'll test it out.
>> ...
>>
>> but I seems unlucky -- I can't even get it installed (ubuntu 64bit
>> 12.04)
>>
>> ping@640g-laptop:~$ sudo gem install vmail
>> [sudo] password for ping: 
>> Fetching: mime-types-1.19.gem (100%)
>> Successfully installed mime-types-1.19
>> Fetching: polyglot-0.3.3.gem (100%)
>> Successfully installed polyglot-0.3.3
>> Fetching: treetop-1.4.12.gem (100%)
>> Successfully installed treetop-1.4.12
>> Fetching: mail-2.5.2.gem (100%)
>> Successfully installed mail-2.5.2
>> Fetching: highline-1.6.15.gem (100%)
>> Successfully installed highline-1.6.15
>> Fetching: sequel-3.41.0.gem (100%)
>> Successfully installed sequel-3.41.0
>> Fetching: sqlite3-1.3.6.gem (100%)
>> Building native extensions.  This could take a while...
>> ERROR:  Error installing vmail:
>> ERROR: Failed to build gem native extension.
>>
>> /usr/bin/ruby1.8 extconf.rb
>> checking for sqlite3.h... no
>> sqlite3.h is missing. Try 'port install sqlite3 +universal'
>> or 'yum install sqlite-devel' and check your shared library search
>> path (the
>> location where your sqlite3 shared library is located).
>> *** extconf.rb failed ***
>> Could not create Makefile due to some reason, probably lack of
>> necessary libraries and/or headers.  Check the mkmf.log file for more
>> details.  You may need configuration options.
>>
>> Provided configuration options:
>> --with-opt-dir
>> --without-opt-dir
>> --with-opt-include
>> --without-opt-include=${opt-dir}/include
>> --with-opt-lib
>> --without-opt-lib=${opt-dir}/lib
>> --with-make-prog
>> --without-make-prog
>> --srcdir=.
>> --curdir
>> --ruby=/usr/bin/ruby1.8
>> --with-sqlite3-dir
>> --without-sqlite3-dir
>> --with-sqlite3-include
>> --without-sqlite3-include=${sqlite3-dir}/include
>> --with-sqlite3-lib
>> --without-sqlite3-lib=${sqlite3-dir}/lib
>> --enable-local
>> --disable-local
>>
>>
>> Gem files will remain installed
>> in /usr/lib/ruby/gems/1.8/gems/sqlite3-1.3.6 for inspection.
>> Results logged
>> to /usr/lib/ruby/gems/1.8/gems/sqlite3-1.3.6/ext/sqlite3/gem_make.out
>> ping@640g-laptop:~$ 
>>
>> you have any issues when installing or knowning of any tricks to
>> resolve
>> that?
>>
>>
>>
>> On 11/30/2012 09:02 AM, Grahame Blackwood wrote:
>>> Hi Ping
>>>
>>> Not that I am aware of, but it is good for gmail and I'm using it
>>> right now for this email.
>>>
>>> Cheers

> 
> apt-get install sqlite3 and sqlite3-devel, etc, etc
> 

You may also find it worth your while looking at RVM - the Ruby Version
Manager  if you're going to start using Ruby. Very
lively, happening community with great support & documentation.

Cheers,

  Phil...


-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical, OS
X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: Fuzzy Finder opens buffers in previous buffer rather than current one

[Phil Dobbin]

On 12/18/2012 10:50 PM, Pablo Giménez wrote:

> 2012/12/17 Asis Hallab  >
> 
> Dear Pablo,
> 
> Fuzzyfinder is somewhat outdated. I would strongly recommend to use
> the CtrlP plugin
> http://www.vim.org/scripts/script.php?script_id=3736
> 
> Thanks  Asis.
> I tried Ctrl-p like a year ago and preferred Fuzzy Finder. 
> But I'll give it another try when I find a moment.

I used to prefer FuzzyFinder but after either a Vim upgrade or a yum or
apt update it stopped working virtually altogether. I did contact the
author on BitBucket about it but he kind of given up development by
about then (this was about April this year I seem to recall).

Cheers,

  Phil...


> 
> It works wonders for me and has much more to offer than FuzzyFinder.
> 
> Kind regards!
> 
> 
> 2012/12/17 Pablo Giménez  >
> 
> Hello all.
> I am using Fuzzy Finder, it is great but there is something
> really annoying about it.
> Most of the time I use FufBuffer problem is that when press CR
> it open the buffer in a different window rather than the current
> one.
> Anybody knows how to force Fuf to open the selected buffer in
> the current one?
> Thanks 

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal



signature.asc
Description: OpenPGP digital signature

Re: Spam from ad...@139.com

[Phil Dobbin]

On 12/20/2012 08:02 AM, John Beckett wrote:

> I have no idea why, but it appears that the spam from
> ad...@139.com to anyone who posts to vim_use has stopped. As I
> mentioned, I have emailed everyone who receives vim_use asking
> about the problem (in batches of 60 at a time). Thanks to those
> who responded. I unsubscribed 60 members since some of them were
> obvious spammers but had not been banned, while others had
> permanent mail errors (for example, quite a lot were from
> yahoo.com which replied that the account did not exist). I am
> not aware of doing anything that might have fixed the spam
> problem, but perhaps all the noise caused someone to notice.
> 
> Please let me know if anyone receives a new spam from now on.

Thank you, John, for taking the time to clear this up. Any dealings with
email is usually tedious & time consuming so much appreciated.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: Vundle and mercurial repos

[Phil Dobbin]

On 12/22/2012 04:12 PM, Marco wrote:

> Hi,
> 
> I use Vundle to manage my plugins. Is it possible to add a
> plugin stored in a mercurial repository?

As it stands at the moment, it doesn't look like it can (but I'm no
Vimscript expert).

Have you tried to add a mercurial repo?

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: question: vim copy to another place, eg:doc

[Phil Dobbin]

On 01/03/2013 02:15 AM, lei yang wrote:

> Hi experts,
> 
> I know in one text,we can use "yy"  to copy something to another place
> in text, if I can't to copy something to another place, eg: from a
> text,and copy  something using vim, and paste( we don't need to use
> vim) something  to another place, how could I do? the real question is
> how chould I put something to the vim chipboard. and it can paste to
> another place( doc, terminal)

I use these mappings to make copy & paste easier:

'"Yank content in OS's clipboard
vnoremap yo "*y
"Paste content from OS's clipboard
nnoremap po "*p'

For this to work in console Vim, Vim would have to be complied
+clipboard as has been mentioned. If it has, these would need to be
appended to your ~/.vimrc.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: Default PYTHONPATH for vim (Mac OSX 10.8.2 Mountain Lion)

[Phil Dobbin]

On 01/10/2013 08:40 PM, William Broach wrote:

> Hello,
> 
> On a fresh install of Mac OSX 10.8.2 Mountain Lion, vim reports its 
> PYTHONPATH as follows:
> 
> :python import sys; print(sys.path)
> 
> ['/usr/lib/python27.zip', '/usr/lib/python2.7', 
> '/usr/lib/python2.7/plat-darwin', '/usr/lib/python2.7/plat-mac',
> '/usr/lib/python2.7/plat-mac/lib-scriptpackages', '/usr/Extras/lib/python', 
> '/usr/lib/python2.7/lib-tk', '/usr/li
> b/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload']
> 
> the system-wide "/Library/Python/2.7/site-packages" is not in its PYTHONPATH.
> 
> This is causing issues with my vim plugins as they will not run unless I add 
> the following to my vimrc: python import sys; 
> sys.path.append('/Library/Python/2.7/site-packages')
> 
> This doesn't seem right, can anyone provide any insight to this?
> 
> Thanks
> 

I have the same trouble too & I'm still running 10.6.8.

Although my console Vim & Python installation are from MacPorts, I still
had to set PYTHONPATH but I set it in my
bash_profile (it being OS X).

The output on Linux (in this case Fedora 17):

['/home/miracle/.vim/bundle/Python-mode-klen',
'/home/miracle/.vim/bundle/Python-mode-klen/pylibs', '/home/miracle',
'/usr/lib64/python27.zi
p', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2',
'/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/p
ython2.7/lib-dynload',
'/home/miracle/.local/lib/python2.7/site-packages',
'/usr/lib64/python2.7/site-packages', '/usr/lib64/python2.7/site-
packages/gst-0.10', '/usr/lib64/python2.7/site-packages/gtk-2.0',
'/usr/lib/python2.7/site-packages', '/usr/lib/python2.7/site-packages/setu
ptools-0.6c11-py2.7.egg-info',
'/home/miracle/.vim/bundle/vim-django/python']'

is as you would expect so I don't think it's a Vim problem.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: ctrl-f and ctrl-b don't scroll an entire page

[Phil Dobbin]

On 01/11/2013 07:34 PM, Charles Campbell wrote:

> Hello!
> 
> When I press ctrl-f and ctrl-b I seem to get a full page (in my case, 28
> lines) less 2, both forward (via ctrl-f) and backward (via ctrl-b).  I'd
> like to have my mpage plugin (which shows a buffer with multiple
> contiguous pages) scroll forwards and backwards by a full page.
> 
> I don't see documentation about this (:he ctrl-f says it scrolls a full
> page), nor did I see any way to modify what vim thought a full page
> was.  Now, I can do
> 
> noremap  2
> 
> (and similar for ) to get the effect I want -- but I'm wondering
> about that "2".  Is this "a page has rows lines less 2" standard, or is
> it an artifact of my o/s?  (I've tried it with both vim and gvim under
> Scientific Linux, huge).

It has always been thus on all the distros I use quoted below. I,
personally, find it a bonus because it helps to orientate me on the page.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: vim: how to disable vim backup file when launching vim command?

[Phil Dobbin]

On 01/21/2013 07:24 AM, ping wrote:

> vim backup file is great in 99% scenarios, but it's annoying to create
> an un-wanted file in some system directories, especially in dirs that
> contains configurations for apps.
> how, can I disable the backup file creation, right when I launch vim to
> read a file?
> 
> I know another workaround is to just launch vim without any file, turn
> off backup file creation, and then open the files...

I'm not aware of an option to turn backups off on a per file basis but I
always set in my vimrc the directory to which the backups are saved:

'set backup

set backupdir=~/.backup'

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: Powerline and terminal issues

[Phil Dobbin]

On 01/31/2013 08:14 PM, Marco wrote:

> Hi,
> 
> this might be the wrong mailing list for my issue. However, I think
> that many of you use a very similar setup and might have an idea how
> to solve it.
> 
> I use the vim-powerline plugin. The problem is that in rxvt-unicode
> it does not show up properly. The background colour is not applied,
> see the attached screenshots. The appearance is fine in gVim, xterm
> and in urxvt with tmux, but not in plain urxvt.
> 
> The screenshots show the output of :echo $TERM. I assume that I did
> not configure my urxvt correctly. Any ideas?

There are several issues on GitHub concerning similar problems with
rxvt-unicode: example 

It may be worthwhile opening a new one if you can't find the answer
you're looking for there.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: gvim color scheme in vim

[Phil Dobbin]

On 02/01/2013 10:16 AM, rudrab wrote:

> Dear friends,
> I am using slate color scheme in gvim(vim-X11 package in fedora).
> The problem is this color scheme (and many other) is not obeyed by vim. So, 
> while slate is dark, vim is still showing white background and comments on 
> yellow (neither is a slate scheme).
> Even more basic packages like blue are rendering color differently.
> In my $VIMRUNTIME, I do have those packages installed.
> So, what is the way to use same color scheme both in vim and gvim?
> NB: I can see vim's color changed if I use, say, :colo slate in vim terminal; 
> only that the color is different from what is seen in gvim.

I use the GTK2 version of gVim on Fedora & I experience no difficulties
with colours displaying correctly.

What values do you have set in your gvimrc?

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: gvim color scheme in vim

[Phil Dobbin]

On 02/01/2013 10:35 AM, Rudra Banerjee wrote:

> Mine is also gtk-2 version.
> my vimrc looks like(I only use vimrc, not gvimrc)
> set autoindent
> set smartindent
> set incsearch
> set ignorecase
> set smartcase
> set novisualbell
> set paste
> set ruler
> "set expandtab
> "set smarttab
> "set shiftwidth=3
> "set softtabstop=3
> colorscheme slate
> 
> Here is the complete gvim version:
> $ gvim --version
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 12 2012 14:43:48)
> Included patches: 1-415, 417-712

[snip for brevity]

You could try putting this in a gvimrc:

'colorscheme hybrid

syntax on

set guifont=Monospace\ 011'

replacing the values for colorscheme & guifont with your own.

It may help.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical,
Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal





signature.asc
Description: OpenPGP digital signature

Re: Favourite Terminal for use with vim ?

[Phil Dobbin]

On 12/02/2013 15:37, Patrick wrote:

> Hi Everyone. I would like to switch from gvim to vim. Some terminals don't 
> seem to support syntax highlighting well. I've got rxvt-unicode looking great 
> with vim but I am wondering about other options. What is your favourite 
> terminal to run vim in?
> 

Personally, on Linux I use gnome-terminal & on OS X, I use iTerm. They
seem to cope with everything that's thrown at them & are a pretty
standard setup (e.g. I've never had to touch termcap & so on)

Have tried plenty of others but always come back to those two. Then
again, on Linux, I always use Gnome so I can't speak for KDE & the like
(although I have tried Konsole).

Cheers,

  Phil...


-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Trouble building vim on a mac

[Phil Dobbin]

On 22/02/2013 11:21, So8res wrote:

> I'm trying to build vim on a mac. I'm pretty new to macs, so I'm almost 
> undoubtably doing something wrong. I have the Xcode developer tools etc. 
> installed, but when I clone vim from the mercurial head, configure, and make, 
> I get the following:
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MAC -fno-common 
> -fpascal-strings -Wall -Wn
> o-unknown-pragmas -mdynamic-no-pic -pipe -I. -Iproto -DMACOS_X_UNIX 
> -no-cpp-precomp -I/A
> pplications/Xcode.app/Contents/Developer/Headers/FlatCarbon  -g -O2 
> -U_FORTIFY_SOURCE -D
> _FORTIFY_SOURCE=1   -I/usr/X11/include -o objects/buffer.o buffer.c
> In file included from vim.h:338,
>  from buffer.c:28:
> os_mac.h:26:64: error: Quickdraw.h: No such file or directory
> os_mac.h:27:24: error: ToolUtils.h: No such file or directory
> os_mac.h:28:21: error: LowMem.h: No such file or directory
> os_mac.h:29:20: error: Scrap.h: No such file or directory
> os_mac.h:30:20: error: Sound.h: No such file or directory
> os_mac.h:31:24: error: TextUtils.h: No such file or directory
> os_mac.h:33:22: error: OSUtils.h: No such file or directory
> os_mac.h:34:20: error: Files.h: No such file or directory
> os_mac.h:36:22: error: Script.h: No such file or directory
> In file included from structs.h:81,
>  from vim.h:1731,
>  from buffer.c:28:
> gui.h:37:20: error: Types.h: No such file or directory
> gui.h:40:20: error: Fonts.h: No such file or directory
> gui.h:41:21: error: Events.h: No such file or directory
> gui.h:42:20: error: Menus.h: No such file or directory
> gui.h:44:24: error: Windows.h: No such file or directory
> gui.h:46:23: error: Controls.h: No such file or directory
> gui.h:48:22: error: Dialogs.h: No such file or directory
> [extensive output redacted]
> 
> Anyone run into this before and/or know what I'm doing wrong off the top of 
> their head?
> 

If you're trying to build MacVim, you need to pull the macvim sources:



If you're trying to build console vim on a Mac, you'll need to pass
disable gui to configure.

Cheers,

  Phil...


-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: make vim remember where I left

[Phil Dobbin]

On 15/03/2013 21:29, FlashBurn wrote:

> Like most of us I open plenty of files at the same time with vim. The problem 
> is that whenever I go from file 1 to file 2 and then back to file 1, Vim 
> doesn't remember where I left off. It opens the file and puts the cursor on 
> line 1. Is there a way to make it remember to put the cursor where I left 
> off? 
> Any help is appreciated.
> 

Try this in your vimrc:

autocmd BufReadPost *
\ if line("'\"") > 0 && line("'\"") <= line("$") |
\  exe "normal g`\"" |
\  endif

Cheers,

  Phil...

-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Learn Vimscript the Hardway

[Phil Dobbin]

Hi, all.

My hard copy paperback of Steve Losh's 'Learn Vimscript the Hardway'
arrived yesterday & I thought I let everybody know it's out.

As can be judged by the title, it's about the only book I know of that
attempts to teach Vimscript & it looks pretty good (disclaimer: I know
next to nothing about Vimscript. At the moment).

It's available at:



It comes in ebook (PDF, epub, mobi) versions, hardcopy paperback &
hardcover also. It's also freely available online.

I should mention that I have no affiliation with Mr Losh (apart from
following him on GitHub) & my only purpose is to pass this on to anybody
who may be curious, like me, about the dark arts of Vimscript ;-)

Cheers,

  Phil...

-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How can I open help in the current window?

[Phil Dobbin]

On 22/04/2013 11:37, Thiago Padilha wrote:

> I googled about this but only found how to open in a vertical split or
> in a full window. I cannot find how can I navigate to help without
> splitting or breaking my current layout.
> 
> Normally I already have two windows splitting the screen vertically and
> would like to open help in the current window then navigate back with
> ctrl+o. Any easy way to accomplish that?

I use:

':h foo.txt | only' to get the help files in the current window only but
I'm unaware of a key command to return you back.

I'm sure there is one & somebody will enlighten us with it shortly ;-)

Cheers,

  Phil...



-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: I'm not getting highlighting syntax for .twig files..

[Phil Dobbin]

On 27/04/2013 14:41, Javier Garcia wrote:

> Hi,
> 
> I have installed .vim/syntax/htmljinja.vim and wrote this in my .vimrc:
> 
> au BufRead,BufNewFile *.twig set syntax=htmljinja

Try:

'au BufRead,BufNewFile {*.twig} set ft=htmljinja'

Cheers,

  Phil...




-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: I'm not getting highlighting syntax for .twig files..

[Phil Dobbin]

On 27/04/2013 19:39, Gary Johnson wrote:
> On 2013-04-27, Phil Dobbin wrote:
>> On 27/04/2013 14:41, Javier Garcia wrote:
>>
>>> Hi,
>>>
>>> I have installed .vim/syntax/htmljinja.vim and wrote this in my .vimrc:
>>>
>>> au BufRead,BufNewFile *.twig set syntax=htmljinja
>>
>> Try:
>>
>> 'au BufRead,BufNewFile {*.twig} set ft=htmljinja'
> 
> The {} are not necessary.

That's right. Only if you intend to add more than one file extension (I
copied & pasted it straight out of my vimrc & deleted as appropriate).

Cheers,

  Phil...



-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: delete last character of multiple lines

[Phil Dobbin]

On 08/05/2013 18:29, Jürgen Krämer wrote:

> :
>>> what should i do in order to delete last character of multiple lines?\
>>
>> How about visually selecting the lines and then:
>>
>>   :'<,'>norm! $x
> 
> or
> 
>   :'<,'>s/.$//

Does the '.' replace a character with nothing?

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.9 & 6.4, Debian Squeeze & Wheezy, Fedora Beefy, Spherical &
That Damn Cat, Lubuntu 12.10, OS X Snow Leopard, Ubuntu Precise, Quantal
& Raring
GnuGPG Key : http://phildobbin.org/publickey.asc


-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: delete last character of multiple lines

[Phil Dobbin]

On 08/05/2013 19:46, Tim Chase wrote:

> On 2013-05-08 19:15, Phil Dobbin wrote:
>> On 08/05/2013 18:29, Jürgen Krämer wrote:
>>>   :'<,'>s/.$//
>>
>> Does the '.' replace a character with nothing?
> 
> This is the method I'd default to.  It's a standard search/replace
> command.  The pattern searched for is "any one character ('.') at the
> end of the line ('$')" and replaces it with nothing (there's nothing
> between the 2nd and 3rd slashes as a replacement).
> 
> You can visualize it by making the replacement something like "":
> 
>   :'<,'>s/.$/
> 
> (the trailing "/" is optional when you don't have any flags to
> include).  You can then "u"ndo that to return to your original
> document.  Also, when there are no flags *AND* no replacement value,
> the whole thing can be shortened to just
> 
>   :'<,'>s/.$

Many thanks, Tim.

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.9 & 6.4, Debian Squeeze & Wheezy, Fedora Beefy, Spherical &
That Damn Cat, Lubuntu 12.10, OS X Snow Leopard, Ubuntu Precise, Quantal
& Raring
GnuGPG Key : http://phildobbin.org/publickey.asc


-- 
-- 
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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.