Integers on 64-bit Vim: how many bits?

According to :help Number, a Number variable is a 32-bit signed integer. No mention of anything else. According to :help limits, a Number variable can have an absolute value larger than 2^31 (i.e. 2 * 1024^3) on 64-bit systems. AFAICT, the former seems to be true: Experiments with :echo and v

When using BufWriteCmd, :undo command doesn't set 'modified' flag properly.

When using BufWriteCmd, :undo command doesn't set 'modified' flag properly. Steps to reproduce: $ vim -u NONE -N :edit sample :autocmd BufWriteCmd setlocal nomodified :put ='1st' " The 1st change of buffer. :write :put ='2nd' " The 2nd change of buffer. :put ='3rd'

Re: Integers on 64-bit Vim: how many bits?

> According to :help Number, a Number variable is a 32-bit signed integer. No > mention of anything else. > > According to :help limits, a Number variable can have an absolute value > larger than 2^31 (i.e. 2 * 1024^3) on 64-bit systems. > > AFAICT, the former seems to be true: Experiments with :ec

Re: When using BufWriteCmd, :undo command doesn't set 'modified' flag properly.

Yukihiro Nakadaira wrote: > When using BufWriteCmd, :undo command doesn't set 'modified' flag properly. > > Steps to reproduce: > > $ vim -u NONE -N > :edit sample > :autocmd BufWriteCmd setlocal nomodified > :put ='1st' " The 1st change of buffer. > :write > :put ='2nd'

Re: Integers on 64-bit Vim: how many bits?

Tony Mechelynck wrote: > According to :help Number, a Number variable is a 32-bit signed integer. > No mention of anything else. It should be "32 or 64". I'll fix that. > According to :help limits, a Number variable can have an absolute value > larger than 2^31 (i.e. 2 * 1024^3) on 64-bit sy

bug when configuring for both python and python3 (was :python forwarding to :py3 and vice-versa in case of incompatibility)

I've tried ./configure --enable-pythoninterp --enable-python3interp on Linux From Scratch with python 2.7 and python 3.2 both compiled with --enable-shared. I would have expected both to work in one instance of vim, but the same messages came up. E836: This Vim cannot execute :pyth

Re: When using BufWriteCmd, :undo command doesn't set 'modified' flag properly.

On Tue, Aug 30, 2011 at 4:56 AM, Bram Moolenaar wrote: > > Yukihiro Nakadaira wrote: > >> When using BufWriteCmd, :undo command doesn't set 'modified' flag properly. >> >> Steps to reproduce: >> >>   $ vim -u NONE -N >>   :edit sample >>   :autocmd BufWriteCmd setlocal nomodified >>   :put ='1st'

Explorer does not honour port number when editing over SCP

I am experiencing a bug where Explorer does not honour a port number when editing files over SCP. To reproduce Open a directory over scp (gvim scp://user@domain:1234//home/user/) Files and directories listed as expected... Open a file vim ignores the port number and attempts to edit the file a