Hugo Ahlenius wrote:
> Is there some good spot where one can get updated Windows
> 64-bit binaries?

I haven't tried it, but there is another site mentioned at:
http://vim.wikia.com/wiki/Download

John

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I want Vim defaults to be
- sane
- follow the principle of least surprise.
(I'd like nocompatible to be set by default, but that's another story)

Christian: :set cpo+=l still makes my test cases fail:
   [1] echo len(matchstr("\n",'\zs[^\n]\ze'))
   [2] echo len(matchstr("\n","\\zs[^\n]\\ze")

You explained it by \n not being chr(10), so what is it?

Let's try by understanding \n's behaviour:
==========================================

case 1) vim buf
     To my undestanding $ matches end of line (in a vim buffer) without eating
that
     end of line whereas \n does both: it matches and eats the end of line.
     Eg try /..\n.. and :set hlsearch

     Thus \n is the same as $\n when applying regex to vim buffers. dos 1310
usually
     is encoded in a ff setting, so \n does what you want if you want it.

case 2) matchstr, matchall, substitute =~ and whatnot (?)

     So if \n is not chr(10), what is it then in this case?

       echo len(matchstr("\n",'\zs[^\n]\ze'))

     clearly indicates it matches \n and and I agree on Erik which called it this
way

       Sorry, [^\n] can never match \n ; not even in pink. That is broken
       behaviour.

So from this point of view I'd say \n behavior is broken when regex get applied
to strings only (which your patch is supposed to fix - I'll test it
later)

Is there more to fix?
=====================

issue 1)

   docs state:
     [] (with 'nomagic': \[])  */[]* */\[]* */\_[]* */collection*
     \_[]

   Well - try /[] - it will not be treated as collection, it'll match [], because
   its empty!! So there should be a comment that collections must contain at
least
   one char to be seen as one.

issue 2)
   With "\_" prepended the collection also includes the end-of-line - why does it
exist, because
   [\n] is accepted and works as expected?

   So can \_[] syntax be deprecated?


Marc Weber

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Marc!

On Di, 19 Feb 2013, Marc Weber wrote:

> I want Vim defaults to be
> - sane
> - follow the principle of least surprise.
> (I'd like nocompatible to be set by default, but that's another story)
>
> Christian: :set cpo+=l still makes my test cases fail:
>   [1] echo len(matchstr("\n",'\zs[^\n]\ze'))
>   [2] echo len(matchstr("\n","\\zs[^\n]\\ze")

Well, you need to prevent that expr-quote (:h expr-quote) is being
evaluated. You need to escape the \ then.

> You explained it by \n not being chr(10), so what is it?

No. Please read again what I wrote. I am not going to repeat myself.

> Let's try by understanding \n's behaviour:
> ==========================================
>
> case 1) vim buf
>     To my undestanding $ matches end of line (in a vim buffer) without eating
that
>     end of line whereas \n does both: it matches and eats the end of line.
>     Eg try /..\n.. and :set hlsearch
>
>     Thus \n is the same as $\n when applying regex to vim buffers. dos 1310
usually
>     is encoded in a ff setting, so \n does what you want if you want it.
>
> case 2) matchstr, matchall, substitute =~ and whatnot (?)
>
>     So if \n is not chr(10), what is it then in this case?
>
>       echo len(matchstr("\n",'\zs[^\n]\ze'))
>
>     clearly indicates it matches \n and and I agree on Erik which called it
this way
>

Vim internals do not distinguish between evaluating functions and
buffers. They work on matching a regular pattern on a string of text. In
Vim buffers, lines are distinguished in memory by NUL and that is the
only thing, that '.' does not match and so does [^\n] so that in a
buffer a search for /[^\n] will match any char (even control codes like
CR or LF)

What you want is, that in a text /[^\n] also does not match LF character
and that is what my patch provides thus it should do what you want.

> Is there more to fix?
> =====================
>
> issue 1)
>
>   docs state:
>     [] (with 'nomagic': \[])  */[]* */\[]* */\_[]* */collection*
>     \_[]
>
>   Well - try /[] - it will not be treated as collection, it'll match [],
because
>   its empty!! So there should be a comment that collections must contain at
least
>   one char to be seen as one.

I would call this a bug as well. I think, this should give an error.

> issue 2)
>   With "\_" prepended the collection also includes the end-of-line - why does
it exist, because
>   [\n] is accepted and works as expected?
>
>   So can \_[] syntax be deprecated?

Why is this an issue? I don't see a problem with \_ syntax at all.

Mit freundlichen Grüßen
Christian
--
Dem großen Publikum ist ein Buch nicht leicht zu schlecht, sehr
leicht aber zu gut.
		 -- Marie von Ebner-Eschenbach

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

> Why is this an issue? I don't see a problem with \_ syntax at all.
Let me tell you. People get to know Vim. Vim is a tool to serve users.
They want to edit text, get their job done (At least that's what I
assume). For this reason every construct such as \_ which requires you
to lookup help is going to take your time - time which should be spent
on the wiki or the homepage (yes - there is much to improve).

So from technical point of view there is nothing wrong: Something is
documentented, and it works as expected.

If you look at the ruby community there are some voices which
dislike some aspects about ruby: That there are so many ways to do
something ..

If you look at the whole ecosystem it is wrong, because its
wasting resources in many ways (human resources being the most
expensive ones). You may disagree on this - but its true.
The best docs are the ones you don't have to read.

I'm not proposing dropping it (if Vim was my projcet I'd do so - showing
an error message instead) - but maybe docs can be adjusted so that
people use [\n] and maybe even miss the Vim only special case on the
first glance.

Christian, thanks for your support.

Marc Weber

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Di, 19 Feb 2013, Christian Brabandt wrote:

> On Mo, 18 Feb 2013, Marc Weber wrote:
> > I don't think that additional threads are going to help
> > There is an issue, and we should find a way to fix (IMHO).
> > Let me summarize again - and tell me if you feel differently.
> >
> > Test cases:
> > [1] echo len(matchstr("\n",'\zs[^\n]\ze'))
> > [2] echo len(matchstr("\n","\\zs[^\n]\\ze"))
> >
> > I expect both do the same, the difference is that the second as chr(10) in
[^],
> > while the first has \n (which should be translated to chr(10).
> >
> > However I obsorve that [2] returns 0 as expected , but [1] does return
> > 1, thus it matches \n even though I told Vim that I do not want to match
> > it. People told me this was because '.' is equal to [^\n].
> >
> >
> > Current situation: at least to be fixed
> > 1:
> >   No matter whether '.' should behave like [^\n]
> >   [1] and [2] should behave the same, right?
> > 2:
> >   This should be documented.
> > (Do you all at least agree these two statments?)
>
> Bram, here is a patch, making [^\n] not match NL within the text and
> that also documents, that '.' matches CR and LF within the text.
>
> This makes both [1] and [2] behave the same and seems to better match
> the users expectations.

Attached is an updated patch, that also prevents /[] matching []
(a collation cannot be empty, so I think it should return an error and
other vi clones do, also grep and perl throw an error).

Included are tests as well.

regards,
Christian
--
Sprachlexikon-Namen: GERRITT - gemütl. Schritt-Tempo b. Pferden

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 17, 2013, at 7:07 PM, Chris Lott wrote:

> Nothing competes with Vim, but I still can't get past the fact
> that--most of the time--I can't ever get into insert mode with iPad
> Vim and my external keyboard. In the meantime, I use
> Textastic...that's the best I've found and it integrates with dropbox.

I have no problem getting into insert mode using the virtual keyboard. I was
also able to remap <esc> to jj, which some have said can't be done. It is a
little tricky, though. You have to do the jj real fast. [Is there a setting I
could change that would get jj recognized as a single command by allowing for a
slightly longer delay between the letters?]

I am sticking with the virtual keyboard. I don't want to lug around a bluetooth.
The problem, of course, is that at present many of the keys required for
efficient use of vim are either awkward to get to or missing altogether. That
will be remedied when somebody comes up with enhancements for the virtual
keyboard.

There are lots of editors and other applications out there for the iPad that
have enhanced keyboards, several of them with configurable enhancements. One,
FastKeyboard, has 12 rows of configurable keys! A couple rows would do for vim

Regards,
--------------------------------------------------------------------------------\
----------
Eric Weir
eeweir@...

"Our world is a human world." - Hilary Putnam



--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 18, 2013, at 12:09 AM, Chris Lott wrote:

> On Sun, Feb 17, 2013 at 7:31 PM, Bee <forth@...> wrote:
>> On Feb 17, 4:07 pm, Chris Lott <ch...@...> wrote:
>>> On Sun, Feb 17, 2013 at 12:42 PM, Bee <fo...@...> wrote:
>>> Nothing competes with Vim, but I still can't get past the fact
>>> that--most of the time--I can't ever get into insert mode with iPad
>>> Vim and my external keyboard.
>>
>> I have never had a problem getting into insert mode, simply the letter
>> 'i' but have remapped getting out of insert back to normal mode
>> because the default ios vim mapping is '\' which is buried 3 levels.
>
> It seems to be a problem with (some?) external keyboards. It works
> fine if I just use the on-screen keyboard. A number of us were having
> this problem and it was never resolved. I'm not sure that development
> of the iPad version of Vim is still going.

It seems not. Given the fondness of developers for vim I don't understand why. I
would think especially the MacVim crowd would be interested. And given what
others have done with other apps it should be possible. Maybe even not that
difficult.

[Says he, knows nothing and could contribute nothing to the effort.]

--------------------------------------------------------------------------------\
----------
Eric Weir
Decatur, GA  USA
eeweir@...

"Hatred destroys. Love heals."

- Eknath Easwaran

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Tue, Feb 19, 2013 at 4:33 AM, Eric Weir <eeweir@...> wrote:
>
> I have no problem getting into insert mode using the virtual keyboard.

Nor do I. But it's too slow. Or I should say: I'm too slow on it. I
type between 90-100 wpm on my external keyboard.

>
> I am sticking with the virtual keyboard.

My keyboard folds up as part of a folio that also holds paper. Most
people have no idea there's an iPad and keyboard until I fold it out,
so it's no burden. It's just frustrating that Vim iOS seems to have
stopped because I have to think this would be an easy fix (after all,
I have no problems with any other editing apps and I have used a LOT
of them).

An extra row of virtual keys, as some editors provide, would be
useful, but just a kludge for those of us who prefer a keyboard we can
type significantly faster on.

c
--
Chris Lott <chris@...>

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 17, 2013, at 4:42 PM, Bee wrote:

> Making progress. I keep trying other ios editors, so far only iText
> Pad is even usable. Still ios vim is much better, but needs DropBox or
> WiFi file sharing support.

A question: Will there be a problem with vim on ios with plugin managers that go
out to the web to look for plugins and download and install them? I.e., does
that violate Apple's rules for what ios apps can do?

Thanks,
--------------------------------------------------------------------------------\
----------
Eric Weir
eeweir@...

"Any assurance economists pretend to with
regard to cause and effect is merely a pose."

- Emanuel Derman






--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 17, 2013, at 4:42 PM, Bee wrote:

> I used the 'd' command in netrw, created all the folders that are
> normally in .vim. Added my own colorscheme... it worked.
>
> ....
>
> Making progress. I keep trying other ios editors, so far only iText
> Pad is even usable. Still ios vim is much better, but needs DropBox or
> WiFi file sharing support.

Thanks for letting me know, Bill. I started gearing up to try the vimball route
just before checking the mail here. It would probably be a snap for most here,
but it was beginning to look like a formidable task for me. Using netrw and 'd'
sounds a lot more feasible.

I take it you created the folders on the ios device, then transferred to the
contents from the osx device via iTunes?

I'm also taking it that once we get syncing with cloud services or even just
wireless with osx devices it will be possible to use netrw to navigate remote
file systems?

Even with file transfer limited to the iTunes mode, once I get my setup
installed---or as much of it as proves to be possible---I will be using vim
rather than the iPad-specific editors that I've installed---Textkraft and
Nebulous notes, among others.

Regards,
--------------------------------------------------------------------------------\
----------
Eric Weir
Decatur, GA
eeweir@...

"A writer is a person for whom writing is more difficult
than it is for other people."

- Thomas Mann






--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

> [..] patch, [..] prevents /[] matching []
> other vi clones do, also grep and perl throw an error).
:) You start comparing Vim against what other tools do.

We should discuss whether /[] is a bug or feature. docs state that /[abc
matches [abc by purpose (which could also be treated as error because
there is no closing ]. And I actually might agree on this being useful.

Marc Weber

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On 2013-02-19 18:54, Erik Christiansen wrote:
> The tiny and distant Esc key on laptops quickly forced me to find
> something better, primarily for vim,

I work primarily on laptops and found that <esc> wasn't the problem,
but that it was too close to <f1>.  So I mapped <f1> to behave like
<esc> so I can just shove my finger in the general direction of the
upper-left corner and get the behavior I want regardless of my
poor accuracy. :-)

-tim



--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Netrw isn't going to work for browsing remote services: it relies on external
helper apps for that. There is still development going on at the  project's
github page.

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

It seems I cannot unsubscribe from this mailing list.

I sent a mail both to vim-unsubscribe@... and to the google address
one. I received the confirmation but replying lead to nothing (vim.org address)
and to a

> Delivery to the following recipient failed permanently:

      vim_use+unsubscribe@googlegroups.com

> Technical details of permanent failure:
> RpcError

error. I don't have spam filtered, so I wonder what's happening. Thanks in
advance

                                                 -Franco

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi

The File Synchronizer Unison has the possibility to merge two versions of a file
both of which have been changed. Unison is perfect for use in a shell, so using
it with vim as the merging tool would be perfect, too. The problem is that using
a simple
"vimdiff CURRENT1 CURRENT2"
just does not start vim. The two best links regarding this are the following:

http://trembits.blogspot.co.at/2010/02/merging-unison-conflict-with-vim.html
http://hash-bang.net/2009/08/ia-merging-unison/

Their solutions are workarounds, one starts a screen-Session, the other uses
gvimdiff. But it would be better to have it working directly in the terminal
session.
So my question is, does anybody know what kind of problem this is?
I've tried some options like -debug or -V, but there is no possibility to get
more information out of it.

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Tue, Feb 19, 2013 at 5:44 AM, David Sanson <dsanson@...> wrote:
>  There is still development going on at the  project's github page.

Sort of. But this particular issue has been reported for nearly a year
with no response of any kind. It's not a total loss, though, because
even when I could make the keyboard work it was so laggy that I didn't
see the point in it!

c
--
Chris Lott <chris@...>

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 19, 2013, at 8:42 AM, Chris Lott wrote:

> An extra row of virtual keys, as some editors provide, would be
> useful, but just a kludge for those of us who prefer a keyboard we can
> type significantly faster on.

The bluetooths will always be there, though I gather they're not yet ideal for
vim.

I gather "typing fast" is important to programmers, at least to some. As a
writer, "typing fast" is not important. The critical thing is how fast is my
thinking. If I'm writing something that requires thought, if writing is
thinking, the thinking is often slower than the typing. At least for me.
Actually, being forced to "type slow" can improve the thinking.

--------------------------------------------------------------------------------\
----------
Eric Weir
Decatur, GA  USA
eeweir@...

"Hatred destroys. Love heals."

- Eknath Easwaran

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

:-)

Thanks Daniel,

I can't do that because I use capslock all the time for its intended
purpose.

Of course, what maybe I COULD (see what I mean) do would be to make
Capslock Esc, and then make Esc capslock. I use capslock much less than
Esc.

SteveT

On Tue, 19 Feb 2013 11:03:56 +0800
Daniel Zhang <wodesuck@...> wrote:

> I map Caps_Lock as Esc
>
>
> 2013/2/19 Steve Litt <slitt@...>
>
> > On Tue, 19 Feb 2013 10:23:00 +1100
> > "John Beckett" <johnb.beckett@...> wrote:
> >
> > > Steve Litt wrote:
> > > > Question for all of you: What's your favorite substitute for
> > > > Esc, whether a keystroke, key combination, or key sequence?
> > >
> > > Some ideas are at:
> > > http://vim.wikia.com/wiki/Avoid_the_escape_key
> > >
> > > I use the bizarre method on that page involving Enter (search
> > > for "ToggleEnterMapping"). It's really weird and it took a while
> > > to get used to it, but pressing Enter is so easy and natural when
> > > one wants to terminate a command that it is now second nature.
> > > I press Ctrl-Enter in gvim to insert a manual end line, or
> > > switch off the mapping with its procedure for that.
> > >
> > > John
> > >
> >
> > Thanks John,
> >
> > I wish I'd read that article years ago. Right now I'm trying jk,
> > but I might try a lot of that web page's other suggestions.
> >
> > Thanks
> >
> > SteveT
> >
> > --
> > --
> > 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+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> >
>

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On 02/19/2013 08:33 AM, Eric Weir wrote:
> I was also able to remap <esc> to jj, which some have said
> can't be done. It is a little tricky, though. You have to do
> the jj real fast. [Is there a setting I could change that
> would get jj recognized as a single command by allowing for a
> slightly longer delay between the letters?]

Take a look at the 'timeoutlen' and 'ttimeoutlen' options:

   :help 'timeoutlen'
   :help 'ttimeoutlen'

I have mine set as follows:

   :set timeoutlen=3000
   :set ttimeoutlen=50

This gives me 3 seconds (3000 milliseconds) to type the next key
in a mapping, while having to wait only 50 milliseconds for Vim
to recognize multi-byte key codes.  For example, on many
terminals, the code for the <Escape> key is a prefix of the
codes for function keys, arrow keys, etc., and Vim has to wait
some amount of time to be sure that it's really an <Escape> and
not just part of a multi-byte keycode.

Michael Henry

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Mon, 18 Feb 2013 21:50:38 -0600
Benjamin Klein <ben@...> wrote:

> On Feb 18, 2013, at 7:52 PM, Steve Litt <slitt@...>
> wrote:
>
> > Thank you!
>
> You're welcome -- glad to be of help. :) I was going to say that I
> borrowed that one from Steve Losh's excellent (and lengthy) "Coming
> Home To Vim" (http://stevelosh.com/blog/2010/09/coming-home-to-vim/),
> but I just looked and it seems that he uses jj instead, so I must
> have found that one elsewhere.
>
> I've read that jk is faster than jj -- I can't prove that, but
> certainly jk is very fast once you get to used to it.

Thanks Benjamin,

I'm actually thinking of using jf. The jk sequence seems a little
slow/tiring because I have to reposition the hand in a weird way. The
jj combo is similar. But with jf, the left index finger is readying
itself as the right index finger strikes, so it will be faster. The
cool thing about the j key is it's unlikely to be followed by a
consonant, so I have the choice of many, many key combos.

I'll get back to you all when I've fully evaluated key combos.

Thanks

SteveT

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Tue, 19 Feb 2013 11:43:10 +0000
Franco <franco00@...> wrote:

> It seems I cannot unsubscribe from this mailing list.
>
> I sent a mail both to vim-unsubscribe@... and to the google
> address one. I received the confirmation but replying lead to nothing
> (vim.org address) and to a
>
> > Delivery to the following recipient failed permanently:
>
>      vim_use+unsubscribe@googlegroups.com
>
> > Technical details of permanent failure:
> > RpcError
>
> error. I don't have spam filtered, so I wonder what's happening.
> Thanks in advance


Hi Franco,

This doesn't answer your question, but be aware that the last time I
unsubscribed and then re-subscribed, it took me days, and I had to
contact people and have somebody in charge manually subscribe me. From
that moment on, I decided to ALWAYS be subscribed to the Vim list,
because at least for me, it was too hard to get back on once I left.

SteveT

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Tue, Feb 19, 2013 at 7:48 AM, Eric Weir <eeweir@...> wrote:
>
>
> I gather "typing fast" is important to programmers, at least to some. As a
writer, "typing fast" is not important. The critical thing is how fast is my
thinking. If I'm writing something that requires thought, if writing is
thinking, the thinking is often slower than the typing. At least for me.
Actually, being forced to "type slow" can improve the thinking.
>

You have me wrong there. I am a writer, not a programmer. I use Vim
almost exclusively for prose and poetry. For the former, a cursor that
lags significantly behind my typing is frustrating because I type as
close to the speed of my thoughts as I can. It's very rare that I find
myself typing something in which my thought moves slower than my
ability to type.

*My* process involves handwriting for the slow writing.

My point is this: the bluetooth keyboard works EVERYWHERE except with
Vim. There's no good reason for that and no good reason it hasn't been
examined at all nearly a year after multiple reports. This isn't some
obscure accessory! But as long as it is *that* laggy, I won't find it
useful.

c
--
Chris Lott <chris@...>

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Mon, Feb 18, 2013 at 10:54 PM, Steve Litt <slitt@...> wrote:

> from: Steve Litt <slitt@...>
> date: Mon, Feb 18 05:54 PM -05:00 2013
> to: vim_use@googlegroups.com
> reply-to: vim_use@googlegroups.com
> subject: mapping a substitute for the Esc key?
>
> Hi all,
>
> I injured my left middle finger and can no longer extend it. Therefore,
> hitting the Esc key to get out of insert mode stops my work in its
> tracks.
>
> Question for all of you: What's your favorite substitute for Esc,
> whether a keystroke, key combination, or key sequence?
>
> Thanks
>
> SteveT
>
Hi Steve

I find ;; feels quite natural and quick.

Cheers

Grahame

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 19, 2013, at 1:53 PM, Chris Lott <chris@...> wrote:

> On Tue, Feb 19, 2013 at 7:48 AM, Eric Weir <eeweir@...> wrote:
>>
>>
>> I gather "typing fast" is important to programmers, at least to some. As a
writer, "typing fast" is not important. The critical thing is how fast is my
thinking. If I'm writing something that requires thought, if writing is
thinking, the thinking is often slower than the typing. At least for me.
Actually, being forced to "type slow" can improve the thinking.
>
> You have me wrong there. I am a writer, not a programmer. I use Vim
> almost exclusively for prose and poetry. For the former, a cursor that
> lags significantly behind my typing is frustrating because I type as
> close to the speed of my thoughts as I can. It's very rare that I find
> myself typing something in which my thought moves slower than my
> ability to type.
>
> *My* process involves handwriting for the slow writing.

My apologies for assuming you we're a programmer. -;) And I understand now where
you're coming from when you complain about the keyboard being "slow." I'd be
disconcerted by that, too.

And on "speed of thought" vs."speed of typing," there are lots of pauses in my
writing. Often I am figuring it out word  by word. (Or, as Anne Lamott would
have it, "Bird by Bird.")

> My point is this: the bluetooth keyboard works EVERYWHERE except with
> Vim. There's no good reason for that and no good reason it hasn't been
> examined at all nearly a year after multiple reports. This isn't some
> obscure accessory! But as long as it is *that* laggy, I won't find it
> useful.

You might give the virtual keyboard more of an opportunity to prove itself. It's
definitely faster than a laggy keyboard, but if the keyboard's not a problem
with whatever other editors you're using, you might not be interested in that.

Regards,

Eric Weir
eeweir@...
Decatur, GA. USA

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Feb 19, 2013, at 1:01 PM, Michael Henry <vim@...> wrote:

> On 02/19/2013 08:33 AM, Eric Weir wrote:
>> I was also able to remap <esc> to jj, which some have said
>> can't be done. It is a little tricky, though. You have to do
>> the jj real fast. [Is there a setting I could change that
>> would get jj recognized as a single command by allowing for a
>> slightly longer delay between the letters?]
>
> Take a look at the 'timeoutlen' and 'ttimeoutlen' options:
>
> :help 'timeoutlen'
> :help 'ttimeoutlen'

Thanks, Michael. I thought I'd encountered a setting like that once when I
didn't need it.

--------------------------------------------------------------------------------
Eric Weir
Decatur, GA. USA

"The invincible shield of caring
is a weapon from the sky
against being dead."

– Tao Te Ching, 67

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Monday, February 18, 2013 4:38:56 PM UTC-6, MarcWeber wrote:
>
> So why should anybody write [^\n] if you can use '.'? So why make [^\n]
>
> behave the same way?

Sometimes the meaning is clearer.

What if you're searching for a sequence of certain characters including
newlines, where the first character is NOT a newline?

I'd probably want to use:

/[^\n]\&[a-f0-9\n]\+

which is equivalent to, but clearer in meaning than:

/.\&[a-f0-9\n]\+

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Tuesday, February 19, 2013 2:06:07 PM UTC-6, Daniel M. Eldridge wrote:
>
>
> Thank-you John.
> I've found a number of fonts that have increased coverage--more characters,
but I'm confused about how to display more fonts in Edit | Select Font...
>
>

Vim should display all *monospace* fonts currently installed on your system in
this menu.

If the fonts you found are not monospace, Vim will not show them.

If they are monospace...did you install them by copying their files to
C:\Windows\Fonts or wherever that folder is?

Note: see http://vim.wikia.com/wiki/Change_font for useful related information.

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Tuesday, February 19, 2013 7:08:21 AM UTC-6, erwin.g...@... wrote:
> Hi
>
> The File Synchronizer Unison has the possibility to merge two versions of a
file both of which have been changed. Unison is perfect for use in a shell, so
using it with vim as the merging tool would be perfect, too. The problem is that
using a simple
> "vimdiff CURRENT1 CURRENT2"
> just does not start vim. The two best links regarding this are the following:
>
> http://trembits.blogspot.co.at/2010/02/merging-unison-conflict-with-vim.html
> http://hash-bang.net/2009/08/ia-merging-unison/
>
> Their solutions are workarounds, one starts a screen-Session, the other uses
gvimdiff. But it would be better to have it working directly in the terminal
session.
> So my question is, does anybody know what kind of problem this is?
> I've tried some options like -debug or -V, but there is no possibility to get
more information out of it.

Maybe vimdiff is an alias which is not being used, or a script not on the path,
or something like that?

Try vim -d CURRENT1 CURRENT2 to launch Vim in diff mode a different way.

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.