My lovely Prom date and I

CTgowiththeFLOW · 1 day

which one is you?

antrix · 26 days

Still that's four times as fast as Bill Joy's terminal when he wrote the thing. http://www.theregister.co.uk/2003/09/11/bill_joys_greatest_gift/

sickill · 27 days

I think this will do what you want:

autocmd InsertEnter * set noic
autocmd InsertLeave * set ic

alols · 1 month

Could be. A quick and dirty hack would be to replace

if (XkbKeycodeToKeysym (self->ctrl_conn, key_code, 0, 0)
                == XK_Control_L)

with

if (key_code == 66)

in xcape.c and it should work for you.

alols · 1 month

Strange. I could not reproduce the issue. Could you please confirm that Caps Lock still works as Control? That seems to be your problem.

xssl · 1 month

Thank you. I'm using gnome-terminal. Interestingly, putting

export TERM=xterm-256color

in my .bashrc solved the issue. Even though I am only using 16 colors. Nothing else has has changed. In VIm under tmux: t_Co=16 and TERM=screen, just like before. Anyways, it is working and I'm happy :)

xssl · 1 month

You have convinced me to try tmux, but it renders the colors in Vim all wrong. Anybody who know what might be wrong? I am not using a 256 color terminal. GNU Screen renders the colors correctly.

alols · 1 month

It would be fairly easy to add a command line option deciding which modifier key that should act as an additional Escape when pressed by itself.. If that is what you are asking for?

alols · 1 month

The point is that Control key acts as Ecape only if it is pressed by itself, when pressed together with other keys it still works as a Control key.

alols · 1 month

Author here. Thank you for the fix! :)

pseudousername · 3 months

What you are doing wrong is that you are pressing enter. Press Esc to leave insert mode or keep typing.

r00k · 3 months

Pride has got nothing to do with it. Use the settings that suite you and be humble about it. I can think of several reasons for wanting a minimal vimrc. Ease of migration for one, and being able to use my colleagues terminals.

ktr73 · 3 months

0 and $ move on the buffer line, g0 and g$ (and gm) move on the screen line, which is what OP wanted.

erichzann · 3 months

This will make it impossible to save in any other format than unix:

autocmd BufWritePre * set ff=unix

ktr73 · 3 months

g0 and g$ takes you to the far left and far right of the screen line.

flyingmeteor · 4 months

What is the use case?

arrygoo · 4 months

This question pops up once in a while and this is the usual answer. But it only answers why vi uses these keys, it does not answer why the arrows were put on those keys in the first place. I guess we will never really know how much thought that went into selecting these keys, if any.

fishtank · 4 months

Would learning vim improve my workflow

Most certainly yes.

or is this something for larger/more complicated projects only, more of an alternative to eclipse?

No. Eclipse is an IDE, Vim is not an IDE, it is a text editor. However, some people prefer text editors over IDEs. So yes it is an alternative to Eclipse, also.

Samus_ · 4 months

Use nnoremap instead of nmap so it won't mess with your other mappings.

FictiveKin · 5 months

Assuming you mean the current paragraph:

 :'{,'}s/old/new/g

1337_n00b · 5 months

Because of this I always hard-wrap my text when working with prose. If I need to paste it into a word processor I use this:

https://gist.github.com/1420072

alols · 5 months

This is exactly the same way I use them.

I think it would be very handy to use more of them though if I only could remember them.

alols · 5 months

I was hoping that somebody would point me to something like that.

alols

TROPHY CASE

you'll need to login or register to do that

create a new account

login