Hi,
One problem with searching for phrases in files that contain wrapped
text (LaTeX source files, e-mails, source code comments, etc.) is that
you never know whether two words will be separated by a space or a
newline. Therefore, it would be handy to have an option that makes
spaces match
The whole situation is pretty arbitrary. E.g. ./demo's output under a
modifyOtherKeys:2 UXTerm, compressed to one row, for Shift+ the top row of my
typical US 105-key or variant:
S-~ ! S-@ # $ % S-^ * ( ) S-_ + Backspace
Why the Shift modifier on ~, @, ^, and _, but not !, #, $, etc? (Guessing
Sorry, I forgot the attachment.
--
Best regards,
lilydjwg
Linux Vim Python 我的博客
http://lilydjwg.is-programmer.com/
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Hi there,
I made a patch to fix some bugs related to Vim's Python3 support. The
bugs I found are:
* vim.error is a `str` instead of an `Exception` object, so `except` or
`raise` it causes a `SystemError` exception
* buffer objects do not support slice assignment
* when exchange text between
On Thu, Feb 24, 2011 at 10:29:02AM +1100, Ben Schmidt wrote:
rxvt uses its own, totally-incompatible encoding scheme for modified
keypresses. This scheme is different to any other terminal that has such
abilities (all the others follow xterm's CSI scheme). It is also
incompatible with ECMA-48
On Mon, Feb 21, 2011 at 02:09:17PM +0100, Bram Moolenaar wrote:
I have been wondering if we should restrict the Unicode characters to
10. This is the official limit that was set a couple of years ago.
There won't be valid characters above this limit, so why allow inserting
them?
I made
Sorry Ben
This is my first time joining a discussion, I had a hard time just to
open an account and send my suggestion. I use the default reply
function and I don't mean to upset anyone. Hopefull now this reply is
well-edited (I removed the quote).
About vim, I misunderstood that it was a
