Hello,
I don'd advocate for either the change or no-change in vim. I just want to
clarify the UNIX behavior:
I understand that this is before the plugin is invoked, but why the
difference?
If 'bar' is a directory,
ls foo/bar
and
ls foo/bar/
produce the same result -- the
Yes. But what happens when you then edit that macro by putting the
register into a buffer, changing it, and yanking it again? This is not
uncommonly done. How should the registers be stored in .viminfo? How do
you write the input to the feedkeys function as a string in vimscript?
Etc.. These
On Feb 21, 2011, at 1:38 AM, Phil Carter wrote:
Using ctrl+v U in insert mode, you can enter Unicode characters by code
point. UTF-8 can only encode up to U+7FFF. Entering any code point up to
that value works fine, but if if you type ctrl+v U 81234567 for example,
you get t_ followed
On Mon, Feb 21, 2011 at 4:31 AM, Milan Vancura mi...@ucw.cz wrote:
Hello,
I don'd advocate for either the change or no-change in vim. I just want to
clarify the UNIX behavior:
I understand that this is before the plugin is invoked, but why the
difference?
If 'bar' is a directory,
ls
Phil Carter wrote:
Using ctrl+v U in insert mode, you can enter Unicode characters by
code point. UTF-8 can only encode up to U+7FFF. Entering any code
point up to that value works fine, but if if you type ctrl+v U
81234567 for example, you get t_ followed by some other bytes
instead of
Firstly: even if it would be true for ls - it's a matter of 'ls'
maintainers decision, nothing more. Especially it does not say
foo/bar and foo/bar/ are same, in any manner. Only it says is ls
shows them in the same way, sometimes.
That's true. But it's like saying that 3.14159 isn't exactly
On 22/02/11 12:09 AM, Bram Moolenaar wrote:
Phil Carter wrote:
Using ctrl+v U in insert mode, you can enter Unicode characters by
code point. UTF-8 can only encode up to U+7FFF. Entering any code
point up to that value works fine, but if if you type ctrl+v U
81234567 for example, you get
I have gnupg.vim 3026 from
http://www.vim.org/scripts/script.php?script_id=661
This is a plugin to edit a file encrypted with GnuPG.
A few issues:
- when encrypting files, unwiped plaintext is left on the temporary
directory disk. This can be mitigated by setting TMPDIR to point to a
ramdisk
-
Adding the author to Cc.
I've attached an updated version of the plugin that I sent to Markus a
while back which I think addresses these problems. I've described below
specifically how the changes should have the desired effect. Would you
mind testing it?
On Mon, Feb 21, 2011 at 01:56:52PM
