John Beckett wrote:
Suggested new feature:
Make an easy way to encrypt a secret within a line.
Then you can have a simple text file to document stuff, with
embedded secrets. On reading, you only need to enter a key if you
want to see a secret.
Example lines before encryption:
1. Persistence of search highlighting is IMO good thing.
Forgot to explain why: newbies often are pressing Esc just in case of ... . So
this key shouldn't do by default anything more than changing of mode.
m.
Adaptacja bestsellerowej
Nicolas Weber wrote:
Hi,
You are correct, I was thinking of this the other way around. My
suggestion would only be security in the sense that someone reading
over your shoulder would be prevented from seeing sensitive content
in the file (e.g. passwords) and would really only be an extension
On 17/01/2007 19:44, Bram Moolenaar wrote:
Mike Williams wrote:
Attached is a patch to use VC8 specific optimization options. FTR, VC8
no longer supports the /Gn processor code generation directive, and the
makefile now uses link time code generation when not optimizing for space.
Although
On 1/18/07, Robert Lee [EMAIL PROTECTED] wrote:
Also, executing such a command on a password while
someone is watching only brings attention to the password, which appears
in clear text until the command sequence has been completed (where-as
folding can be applied automatically when the file is
Mike Williams wrote:
On 17/01/2007 19:44, Bram Moolenaar wrote:
Mike Williams wrote:
Attached is a patch to use VC8 specific optimization options. FTR,
VC8 no longer supports the /Gn processor code generation directive,
and the makefile now uses link time code generation when not
Alexei Alexandrov wrote:
Hi Bram et al.,
here is a rather strange bug. It seems to be specific for Windows and only when I try to open *.exe or *.dll file (yes, it's strange but sometimes I use it). If I open an *.exe file with
gvim bjam.exe
it opens just fine. But if I open it with
gvim
Denis Perelyubskiy wrote:
hello,
I briefly upgraded to patch 182 a little while back, and selectbuf
script which I absolutely adore :) stopped working
(http://vim.sourceforge.net/scripts/script.php?script_id=107) I am using
version .178 right now. Something about those 4 patches
Mikołaj Machowski wrote:
I won't say more now. If Bram feels that improved defaults would be
worth investigating, a discussion here would probably be best.
OTOH people who dream in Vim script may not be the best source of
ideas on how Vim should be configured to win new converts.
I suppose
Hi Bram Moolenaar, you wrote:
I can't reproduce it. It could be caused by a plugin.
Does adding -V10 show some context of the error?
Does anyone else see this?
Not sure if my previous message reached the list: the bug is reproducible only
if the extension of the file is in
Hi A.J.Mechelynck, you wrote:
Exe or dll files are usually binaries (which shouldn't cause E479
however); and unlike cmd.exe when executing them, Vim doesn't lookup the
PATH for editfiles.
1) Are you sure the directory containing the editfile was current? If it
wasn't, you should
Hi John Beckett, you wrote:
The best way to expand Vim usage IMHO would be to work out better
default settings to improve the first hour of contact. In addition,
perform necessary fixups, but resist new features.
I also think that Vim is feature-enough. What affects me most of all every
John Beckett wrote:
Suggested new feature:
Make an easy way to encrypt a secret within a line.
Then you can have a simple text file to document stuff, with
embedded secrets. On reading, you only need to enter a key if you
want to see a secret.
Example lines before encryption:
Mike Williams wrote:
Attached is a patch to use VC8 specific optimization options. FTR, VC8
no longer supports the /Gn processor code generation directive, and the
makefile now uses link time code generation when not optimizing for space.
Although MS keeps changing the arguments,
Alexei Alexandrov wrote:
On 1/17/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
I can't reproduce it. It could be caused by a plugin.
Does adding -V10 show some context of the error?
Does anyone else see this?
It reproduces only when the extension of the file is added into
John Beckett wrote:
Sorry I'm late, but I just listened to the Vim BOF session that Bram
mentioned three months ago.
In the talk, Bram sounded quite evangelical with regard to promoting
Vim usage, and he asked for suggestions on how he should best spend
his limited time in working towards
Dnia czwartek 18 styczeń 2007, Matthew Woehlke napisał:
...I am not a Vim hacker, but if you can rig Vim to handle some escape
sequence, I may be able to help make Konsole understand/send them. A
start might be to write a simple application that sends the sequence to
turn on the function and
Dnia czwartek 18 styczeń 2007, Bram Moolenaar napisał:
Note that we also need one to enable/disable getting these events. A
program should only get the events when asked for.
Are you talking here about Vim part or Konsole part?
m.
Mikolaj Machowski wrote:
Dnia czwartek 18 styczeñ 2007, Bram Moolenaar napisa³:
Note that we also need one to enable/disable getting these events. A
program should only get the events when asked for.
Are you talking here about Vim part or Konsole part?
Both. The terminal emulater
Bram Moolenaar wrote:
Alexei Alexandrov wrote:
On 1/17/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
I can't reproduce it. It could be caused by a plugin.
Does adding -V10 show some context of the error?
Does anyone else see this?
It reproduces only when the extension of the file is added
Bram Moolenaar wrote:
Mikolaj Machowski wrote:
Dnia czwartek 18 styczeñ 2007, Bram Moolenaar napisa³:
Note that we also need one to enable/disable getting these events. A
program should only get the events when asked for.
Are you talking here about Vim part or Konsole part?
Both. The
Dnia piątek 19 styczeń 2007, Matthew Woehlke napisał:
So, just to make sure I am following, Vim does or does not currently
understand any escape sequences for focus events? It sounds like no,
but then what about A.J.'s comment about reacting to [focus] events for
'the GUI and a few console
22 matches
Mail list logo