I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up as a
performance issue that could be addressed in future releases of gvim?
Opening a large file would
skelker wrote:
I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up as a
performance issue that could be addressed in future releases of gvim?
Opening
On Dec 4, 2007 5:40 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
skelker wrote:
I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up as a
On Dec 4, 2007 7:40 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
Regardless, I wonder how much of an issue this really is. It seems to
me that the code is quite optimized
How much of an issue the size of the writes, that is.
[1] fsync is a slow operation, especially on a reiser4
Juergen Jottkaerr wrote:
On 3 Dez., 22:20, Bram Moolenaar [EMAIL PROTECTED] wrote:
Patch 7.1.168 (extra)
Problem:Win32 GUI: Since patch 7.1.095, when the Vim window does not
have
focus, clicking in it doesn't position the cursor. (Juergen
Kraemer)
On Dec 3, 2007 4:59 PM, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
On Dec 3, 2007 2:05 PM, Charles E. Campbell, Jr. wrote:
Assuming that I have an encrypt/decrypt function pair, the pid could be
used as a single-session p/w that would be transparent to the user. I
don't see
My point was that a would-be cracker would have access to both the
encryption key and the encrypted text. Using the pid as the key is
not made more secure by not storing it, since that cracker would also
have access to the hypothetical getpid() function; it just saves him
the trouble of
Thank you, Ben! That's exactly what I meant.
For this, keeping a variable in a script-local function would suffice
--
I personally haven't found a way yet to access a s:var. (If you know
of
a vim-only solution, please tell me.) Although rot13 is of course is
no
encryption/obfuscation at all,
