Live data from Hacker News

Why Kakoune – The quest for a better code editor

kakoune.org

71–80 of 329 posts

Re: Why Kakoune – The quest for a better code editor

#71
post #68
post #35

Earlier quoted context omitted.

>How would that work if the motion comes first? Would I go "wwwwd"? Would that delete one word, or four? 'w' will move the current selection to the next word so only one word. To extend the selection you need to press 'W' so "wWWWd" will delete four words. For most motions (if not all), the uppercase variant will extend the current selection. This also makes searching slightly different: / search forwards ? extend se…

Can you add counts to motions/objects? I.e. does "3w" select three words you can act on, or do you have to go "wWW"?

3w works

Re: Why Kakoune – The quest for a better code editor

#72

Earlier quoted context omitted.

The ones I have used (IntelliJ, Netbeans and eclipse) were quite effortless to jump between. I doubt Visual Studio will be much harder. Jetbrains covers Ruby, Python, JS, C and more and it would surprise me bigtime if those language specific versions aren't quite similar to the plain Java version as well.

I think Vim is far easier to learn than Visual Studio. The menus are completely unintuitive, bureaucratic and painful to use. I always use cl.exe from the command line with Makefiles.

I think it is very hard to be more unintuitive than vim.

Re: Why Kakoune – The quest for a better code editor

#73
One functionality I find missing in all modern code editors is - repeat action. This was present and extremely useful in, now extinct, Convergent Technology OS (CTOS) resident editor. In brief, it allowed users to repeat all the actions they performed on one-line of code, on another line of code. It's amazing how productive you can be when you have that feature. This goes beyond find & replace; It also helps format code, insert, replace multiple parts of the line, etc. all with one keystroke.

Re: Why Kakoune – The quest for a better code editor

#74

Earlier quoted context omitted.

What would a GUI bring to this that isn't possible in the console? You can use a mouse to issue commands to console programs, after all: if you want to use your mouse to scroll through or select regions of text, you can.

I find that console apps are far less intuitive when it comes to visual thinkers. I also am not too keen on modal editing, it doesn't match how I do most things in life. I don't have to switch out my teeth when eating vs drinking. It just doesn't seem natural to me. I've always found I'm more productive with a GUI. Command line is great for simple tasks and executing commands, but editing files has always seemed less…

what is a visual thinker?

Re: Why Kakoune – The quest for a better code editor

#75
post #73

One functionality I find missing in all modern code editors is - repeat action. This was present and extremely useful in, now extinct, Convergent Technology OS (CTOS) resident editor. In brief, it allowed users to repeat all the actions they performed on one-line of code, on another line of code. It's amazing how productive you can be when you have that feature. This goes beyond find & replace; It also helps format c…

Yep - this is "." in vim and it saves me so much work all the time.

Re: Why Kakoune – The quest for a better code editor

#76
post #73

One functionality I find missing in all modern code editors is - repeat action. This was present and extremely useful in, now extinct, Convergent Technology OS (CTOS) resident editor. In brief, it allowed users to repeat all the actions they performed on one-line of code, on another line of code. It's amazing how productive you can be when you have that feature. This goes beyond find & replace; It also helps format c…

I don't know what you are talking about. Every major editor I know has that functionality.

Re: Why Kakoune – The quest for a better code editor

#77
post #73

One functionality I find missing in all modern code editors is - repeat action. This was present and extremely useful in, now extinct, Convergent Technology OS (CTOS) resident editor. In brief, it allowed users to repeat all the actions they performed on one-line of code, on another line of code. It's amazing how productive you can be when you have that feature. This goes beyond find & replace; It also helps format c…

This sounds like macros? Of course, the problem with macros is that you sometimes realize you should have hit "Record" only after you've completed the action.

Re: Why Kakoune – The quest for a better code editor

#78

Modal text editors are definitely not my thing, but anyway this looks like a huge improvement on vim. Still a shame that it is entirely console-based. It's 2016 people! We've had GUIs for literally decades.

yeah...

fta:

>The first thing to realize is that non-modal text editors are extremely biased towards insertion. They make insertion easy (by making the default behaviour of most keys to insert a character into the buffer) at the expense of making most other operations suboptimal, by requiring hard to reach keys or modifiers (or, even worse, moving your hand all the way to your mouse).

i disagree whole heartedly that reaching a modifier key is some great expense. I can do many things very quickly in sublime and have never felt that there was any time loss hitting a modifier key. compared to the expense of:

1) occasionally entering several commands by accident when in the wrong mode and having to correct it

2) lack of ease of use both for initial learning and for other coders who might have to type something on your comp when pairing and they dont use your exact modal editor

3) lack of transitionable skills to other editors, difficult discoverability, and many other side effects of modal systems

i respect the choice of others to use modal editors but it is absolutely not some cut and dry thing as the author presents it.

i can do things in sublime at probably 90% of the speed of someone in vim and perform many or all of the same operations including some you cant do in vim etc thanks to plugins.

aside from all that, reading, writing, and navigating code are not my bottlenecks for productivity anyway.

Re: Why Kakoune – The quest for a better code editor

#79
post #50

Earlier quoted context omitted.

What would a GUI bring to this that isn't possible in the console? You can use a mouse to issue commands to console programs, after all: if you want to use your mouse to scroll through or select regions of text, you can.

> What would a GUI bring to this that isn't possible in the console? Not being destructive of user input, for starters.

I'm with Kaod here - what do you mean by this?
Post reply on HN