A.J.Mechelynck wrote:
Robert Lee wrote:
I have a gvim 7.0 (win32 with +comments) that seems to be ignoring
the set comments line in my .vimrc file. I can submit the entire
.vimrc file if desired but the relevant line is:
set comments=s:/**,mb:*,ex:*/
What I get is this (vim default
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:
server12 { admin
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
John Beckett wrote:
Marc Weber wrote:
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.
I don't think this should be a general vim feature
I'd like to see an external .vimrc editor shipping with gVim and
directly accessible from within easy mode (e.g. on the tools menu). The
editor would likely be a totally separate binary though, so maybe a
separate project is called for.
What I have in mind is a tabbed dialog (depending on
Nikolai Weibull wrote:
On 4/24/07, Gregory Seidman [EMAIL PROTECTED] wrote:
In fact, what I'm asking it
to do currently rarely takes much time, but it could be really nice
to ask
it to do a lot more and still not pay a huge time or memory penalty.
What plugins/functionality are we missing
Edward L. Fox wrote:
On 5/8/07, scott [EMAIL PROTECTED] wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to
7.1a -- from previous posts i had thought there was something extra
that had
to be done to get the beta, like create a new 71a directory or something
now
Bram Moolenaar wrote:
Mr Toothpik wrote:
i was surpised by the fact that simply running 'svn update' bumped me
up to 7.1a -- from previous posts i had thought there was something
extra that had to be done to get the beta, like create a new 71a
directory or something
now i've got the beta i
Stefano Zacchiroli wrote:
On Tue, May 08, 2007 at 04:50:36PM -0500, Robert Lee wrote:
The SVN Repos has conflict markers left in the file filetype.vim,
Sorry for the silly question, but the answer is not clear to me from
your text: is your working copy that has conflict markers
A.J.Mechelynck wrote:
Micah Cowan wrote:
A.J.Mechelynck wrote:
Micah Cowan wrote:
Bram Moolenaar wrote:
[...]
The solution is simple: Don't create a link in place of the .viminfo
file. And certainly not to /dev/null.
Background info: When Vim finds an existing .viminfo file, it
writes
Sebastian,
Why not utilize the talk: pages for the comments (see discussion tab
at top of each wiki page)?
Just curious.
-Robert
Sebastian Menge wrote:
[cross-posted to vim, vim-dev, vim-announce, wikia-l]
Hi all
Finally I have imported all the vim tips from http://vim.org/tips to
11 matches
Mail list logo
