A.J.Mechelynck wrote:
It took me quite some time to get around to finding out how to use the
quickfix window. I would venture that a beginning user can blissfully
ignore it and concentrate on the basic ":help " command, the
normal-mode yank, put and delete command, and on switching between Norm
John Beckett wrote:
Bram Moolenaar wrote:
No, I don't want that. Pressing ESC is to get back to Normal mode,
it should not have side effects like this.
OK. But my suggestion was not that ESC would go to Normal mode _and_
clear highlighting. My proposal was that if I start in Insert mode,
then
Bram Moolenaar wrote:
No, I don't want that. Pressing ESC is to get back to Normal mode,
it should not have side effects like this.
OK. But my suggestion was not that ESC would go to Normal mode _and_
clear highlighting. My proposal was that if I start in Insert mode,
then press ESC I would be
Ilya Bobir wrote:
If you think that you can provide a better defaults for novice users you
can just write a script that will adjust vim the way you see it and ask
Bram to add it into the distribution along with a note in the tutor
OK. Perhaps that would handle the issue. I don't care how it's
Nikolai Weibull wrote:
Well, hlsearch only kicks in /after/ you've completed your search,
whether you're using 'incsearch' or not. I once thought this was a
nice feature, but I've realized that I rarely need to have other
matches highlighted. I mean, either I've found what I want using
'incsear
Nikolai Weibull wrote:
In particular, any network admin simply has to record passwords and other
sensitive information - you can't reliably remember more than two or
three
passwords, particularly when you're not using them often.
I don't understand what you're trying to say in the first part of
Stefano Zacchiroli wrote:
On Thu, Jan 18, 2007 at 05:46:55PM +0100, A.J.Mechelynck wrote:
Vim defaults to 'compatible' mode everywhere, except where it finds a
"user" _vimrc or .vimrc (system vimrc doesn't count).
I personally recommend to create the following as $HOME/_vimrc (or
$HOME/.vimrc
Martin Stubenschrott wrote:
On Fri, Jan 19, 2007 at 07:28:51PM +1100, John Beckett wrote:
In the BOF talk, Bram really was asking for ideas on what would make
new users flock to Vim.
Biggest changes would really be defaults imho. And that should be done
without really compromising compatible m
On Fri, 19 Jan 2007 16:14:59 -0500, "Charles E Campbell Jr"
<[EMAIL PROTECTED]> said:
> Denis Perelyubskiy wrote:
>
> >If I remove the netrw plugin, things go back to normal. I did notice
> >that netrw plugin changed recently...
> >
> >
> Can you give me an example? Also, what o/s are you usin
John Beckett wrote:
[...]
Then, I could write an email to a friend saying
"Run gvim and do .
Then you can press F11 to do ".
For example, perhaps F11 = ":cn", Shift-F11 = ":cp".
[...]
This sounds very like file types. When you are opening a file
appropriate actions can be done automatically i
Denis Perelyubskiy wrote:
Thanks. While I can't tell what went wrong by just eye-balling the
patches, I did find that the problem results from netrwPlugin.vim.
Basically, netrw registers this autocommand:
au BufEnter .* silent! call s:LocalBrowse(expand(""))
When it is executed on a buffer swi
On Thu, 18 Jan 2007 17:22:24 +0100, "A.J.Mechelynck"
<[EMAIL PROTECTED]> said:
> 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.ph
John Beckett wrote:
> Bram Moolenaar wrote:
> > Mostly PageUp and PageDown do the reverse of each other. If you
> > mean that the cursor has moved, that is a completely different thing.
>
> I'm not sure what "completely different thing" adds. I'm just trying
> to respond to your call for sugges
> From: [EMAIL PROTECTED]
> On 1/19/07, Matthew Winn <[EMAIL PROTECTED]> wrote:
>
> > Gung'f ab tbbq. Erny areqf pna ernq ebg13 grkg jvgubhg
> hfvat fbsgjner.
>
> Hm. I don't understand. Is that some sort of encryption
> you're using?
Garbled, typo somewhere or spellchecker goofed! :-)
---
On 1/19/07, Matthew Winn <[EMAIL PROTECTED]> wrote:
Gung'f ab tbbq. Erny areqf pna ernq ebg13 grkg jvgubhg hfvat fbsgjner.
Hm. I don't understand. Is that some sort of encryption you're using?
nikolai
P.S.
Sorry, I couldn't keep from joking around a bit.
D.S.
Matthew Winn wrote:
> In other products I've seen where search highlighting is always on, it
> generally takes users no more than a couple of seconds to realise that
> if the highlighting is distracting them all they have to do is enter a
> search that won't work, typically by dragging their finge
On Fri, 19 Jan 2007 23:15:57 +1100, "John Beckett"
<[EMAIL PROTECTED]> wrote:
> IMHO it is quite idiotic that Vim has the really great feature of
> globally highlighting searches, but the user has to learn how to
> map keys to make it work in a sensible way. I suppose there
> are people who don't
On Thu, 18 Jan 2007 11:04:00 +0100, Nicolas Weber
<[EMAIL PROTECTED]> wrote:
> > 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
> > cont
On 1/19/07, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
Which defeats the whole point of having multiple passwords, as if
someone figures out the master password then the other passwords will
also be available. So it's better to use one good password/passphrase
and stick with it.
No, is not.
On Fri, Jan 19, 2007 at 01:09:41PM +0100, Martin Stubenschrott wrote:
> First and most important thing would be to enable nocompatible by
> default when the executable name is (g)vim, compatible should still be
> on, when the executable name is vi. Enabling/disabling by an (non-)existing
That's pr
On 1/19/07, John Beckett <[EMAIL PROTECTED]> wrote:
Nikolai Weibull wrote:
> 2. Don't write down passwords at all - use phrases that you remember
> instead
> 3. Don't write down passwords where other people might walk by and
> see what you're typing
Let's not start a religious war, but FWIW ma
On 1/19/07, John Beckett <[EMAIL PROTECTED]> wrote:
Nikolai Weibull wrote:
> Perhaps a better way is to leave 'hlsearch' off and provide a binding
> that toggles it on and off. That way you don't get the "distracting"
> highlighting until you actually request it.
OK but I imagine most people wo
A.J.Mechelynck wrote:
I sense an attitude here that it's just the luser's loss if they
don't learn how to use Vim. Fair enough, but there should be a way
for a non-vi user to enter a command telling Vim "I'm one of those
95% of people who use a modern PC - please switch to a useful mode".
"Easy
Nikolai Weibull wrote:
Perhaps a better way is to leave 'hlsearch' off and provide a binding
that toggles it on and off. That way you don't get the "distracting"
highlighting until you actually request it.
OK but I imagine most people would like hlsearch on while they
are searching (I certainl
On Fri, Jan 19, 2007 at 07:28:51PM +1100, John Beckett wrote:
> In the BOF talk, Bram really was asking for ideas on what would make
> new users flock to Vim.
Biggest changes would really be defaults imho. And that should be done
without really compromising compatible mode.
First and most importa
Bram Moolenaar wrote:
Mostly PageUp and PageDown do the reverse of each other. If you
mean that the cursor has moved, that is a completely different thing.
I'm not sure what "completely different thing" adds. I'm just trying
to respond to your call for suggestions on how to make Vim more
attra
Nikolai Weibull wrote:
2. Don't write down passwords at all - use phrases that you remember
instead
3. Don't write down passwords where other people might walk by and
see what you're typing
Let's not start a religious war, but FWIW many authorities have changed
their mind and no longer advoca
Bram Moolenaar wwrote:
Suggested new feature:
Make an easy way to encrypt a secret within a line.
This is very a specific feature. You should implement this in a script,
this doesn't sound like something Vim should support internally.
OK. I just thought I would mention the concept because I
Nikolai Weibull wrote:
Make an easy way to encrypt a secret within a line.
[Really complex scheme to implement this.]
Why is it not enough to simply implement a function that
encrypts/decrypts a range of text, much like g? ROT13s a
range of text?
Because the scheme needs to be simple to use.
On 18/01/2007 20:55, 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 M
On 18/01/2007 15:50, A.J.Mechelynck wrote:
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 li
John Beckett wrote:
A.J.Mechelynck wrote:
I personally recommend to create the following as $HOME/_vimrc
(or $HOME/.vimrc) immediately after first installation, and to
add tweaks as one gets going:
...
Good advice, as always, Tony. But I am trying to crack a different
nut.
In the BOF talk, Br
On Thu, Jan 18, 2007 at 05:46:55PM +0100, A.J.Mechelynck wrote:
> Vim defaults to 'compatible' mode everywhere, except where it finds a
> "user" _vimrc or .vimrc (system vimrc doesn't count).
>
> I personally recommend to create the following as $HOME/_vimrc (or
> $HOME/.vimrc) immediately after
On 1/19/07, John Beckett <[EMAIL PROTECTED]> wrote:
One problem was how search highlighting is persistent (which is
great), but it is very distracting to some people when you want to
turn your attention to another issue. Telling him how to map a key
to do ':nohl' is just unnecessary mumbo jumbo.
A.J.Mechelynck wrote:
I personally recommend to create the following as $HOME/_vimrc
(or $HOME/.vimrc) immediately after first installation, and to
add tweaks as one gets going:
...
Good advice, as always, Tony. But I am trying to crack a different
nut.
In the BOF talk, Bram really was asking
On 1/18/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
I do agree that good defaults are important. But backwards
compatibility is also important. It's not always easy to make a choice.
I think some things would be really sane to have on by default, such
as :syntax on, but at the same time it
36 matches
Mail list logo
