Tony Mechelynck, 28.02.2009:
On 28/02/09 12:06, Markus Heidelberg wrote:
Tony Mechelynck, 28.02.2009:
On 28/02/09 11:34, Markus Heidelberg wrote:
[...]
This debate is going nowhere. You won't change your mind, and neither
shall I, so I'm shutting up.
OK, do so,
when you click middle mouse button while Vim is key-mapped on MiddleMouse
Vim copies from clipboard or Vim does the instructions inserted by
key-mapping. It does randomly!
I think Vim should do not copy from clipboard while Vim is key-mapped on
MiddleMouse
I am using Vim-win64. Thank you.
I think that it's a bug.
from b import classParent
class classChild(classParent):
def __init__(self):
print 'blabla'
def anyfunction(self):
print 'anyfunction'
object = classChild()
object.C-xC-o
it's not working, because the line 'from b import classParent' appears
Milan Vancura, 02.03.2009:
Similarly, if I need to check something in the vim history, another
repository,
made by Christian Michon, is very helpful (http://github.com/cmichon/vim).
Indeed! I used it, when I recently used git-bisect, since vim_extended
doesn't have much useful history for
On 19-Feb-09 12:02, Luc Hermitte wrote:
I've finally implemented my own unit testing plugin for vim. [1]
This is a first draft, and all comments are welcomed.
The plugin has been strongly inspired by Tom Link's tAssert plugin
(thanks Tom!).
...
My plugin is made for Unit Testing, and
Hello,
when searching for the EOL ($) and 'hlsearch' is set, it doesn't get
properly highlighted, if the EOL is in the same column as the cursor is
placed after the first match.
To reproduce:
vim -u NONE -U NONE -c set hlsearch -c normal 3ix^Mxx^Mxxx^M^[/$^M
^M = Ctrl-vEnter
^[ =
With Vim's current behavior, 'encoding' is derived from the environment
and 'fileencoding'/'termencoding' derive from 'encoding' (modulo
'fileencodings' affect on 'fenc'). This seems sub-optimal for various
reasons.
1) Vim is using an internal encoding derived from the environment which
may
Markus Heidelberg, 03.03.2009:
Hello,
when searching for the EOL ($) and 'hlsearch' is set, it doesn't get
properly highlighted, if the EOL is in the same column as the cursor is
placed after the first match.
To reproduce:
vim -u NONE -U NONE -c set hlsearch -c normal
On 03/03/09 01:40, James Vega wrote:
With Vim's current behavior, 'encoding' is derived from the environment
and 'fileencoding'/'termencoding' derive from 'encoding' (modulo
'fileencodings' affect on 'fenc'). This seems sub-optimal for various
reasons.
1) Vim is using an internal encoding
On 02/03/09 13:48, Milan Vancura wrote:
Tony Mechelynck, 28.02.2009:
On 28/02/09 12:06, Markus Heidelberg wrote:
Tony Mechelynck, 28.02.2009:
On 28/02/09 11:34, Markus Heidelberg wrote:
[...]
This debate is going nowhere. You won't change your mind, and neither
shall I, so I'm shutting
On Tue, Mar 03, 2009 at 03:32:45AM +0100, Tony Mechelynck wrote:
On 03/03/09 01:40, James Vega wrote:
...
3) File encoding detection ('fencs') defaults to a value that is
unlikely to correctly work with most interesting (non-ascii) files.
Defaulting 'enc' to UTF-8 helps address
On 03/03/09 06:40, James Vega wrote:
On Tue, Mar 03, 2009 at 03:32:45AM +0100, Tony Mechelynck wrote:
On 03/03/09 01:40, James Vega wrote:
...
3) File encoding detection ('fencs') defaults to a value that is
unlikely to correctly work with most interesting (non-ascii) files.
Hi!
Am 03.03.2009 06:40, James Vega schrieb:
[...]
2) Vim compiled with the --disable-multibyte configure option cannot use
UTF-8, or any other multibyte encoding; in fact it doesn't even accept
the 'encoding' option as valid.
Is there a reason to allow building Vim without multibyte
13 matches
Mail list logo
