USE V|M

USE V|M

Its like Linux in miniature, the process is more important than results of the process.
The Linux Perfect Process is like an infinite command line which executes to give a segfault.

>>80
As far as I can tell, you know nothing about any topic which you post about, ever. Why would this be an exception?

>>82
There is only two options
1.you spend alot of time editing:using vim macros,editing the macros,entering commands,
2.you spend little time editing: mostly writing, occasionally entering vim commands
#1 is the "constant editing pattern", which is counter-productive to flow, but easily answered by "powerful" command console 
#2 is answered by Notepad2 much better, does not require learning any macro languages and has intuitive keyboard bindings.

>>83
You are retarded. First you bring up how awesome ctrl+c and ctrl+v are with arrow keys. When the response is that you are wasting keystrokes, you switch to some bullshit about how much time you spend writing and not editing.

Basically, you are full of shit and have no argument. How could you, when you don't even know what you're talking about?

>>83
Please continue posting FrozenVoid, you're only showing us your true identify which is that you're a shitty person who doesn't know how to program at all and has hard time multitasker, probably autistic as well and you base all your arguments with a cloud of ignorance and try to use logic that would only apply back when vi and emacs were just getting started.

Please stop posting you ignorant fuck, no one wants you here. Go back to /g/ i'm sure you'll be welcomed there.

>>84
Its like this:
you have a linux system but configuring and editing is considered superior and preferable to actually using it.
Like this in editors, there is line with editors which you configure and edit to infinity(VIM) and editors which allow you to do productive work with minimum hassle(notepad2).

>>85
At the time of invention of vi/emacs there we no mices, menus, and every keystrokes=command was powerful and intuitive for machine which needed a while to process and display the results(the visual paradigm wasn't developed then) so making every keystroke of the editor/tape /punch card a valuable commodity it prematurely limited itself to making users hostage to its own command system(and since it was good enough, even with mistyped commands and constant errors of novice users, it stuck in unix userland.).

>>1-1000
Why do you care about text editors?
Would vim, notepad2, kate or anything else make my programs better?
PS: Oh I see, my opinion is bullshit because I am a dumb programmer. I need to think a lot before writing anything.
PS2: About mouses: grabbing small pieces of text is just quick and comfortable enough. But when I try to select a block larger than my screen, it becomes hell.

>>88
I use shift and drag it with mouse usually, or shift and arrow keys. Either way is not requiring thinking about what i'm doing(the process) and do the operation instantly(so mentally i'm still writing code and can return anytime)

Summarizing:
Since the Flow is not interrupted bu editing process in notepad-Type editors it makes a huge productivity boost.
Using standard editing hotkeys ctrl-v/ctrl-c/shift/Ctrl-f is much better than relying on single editor API which works only inside it(unlike very edit control in windows).
I can code a bit better editor, with more optimized menus for the extra 10-20% speed in specific mouse ops(several menu choices simplified into one right-click/select), but that would not be justified as learning and adapting to the extra menu choices(so they work subconsciously, without interrupting the Flow), which are available through another layer of menus which are not as often used as to not even justify adding them in the first place.

And for the ultimate argument against the layers-of-editing approach, if VIM is so powerful with its macro/command system, why are you still use "primitive" typing to enter macros/commands, you should use VIM to compose the text which would compose the text which would compose the text which would become macro/command executed by VIM.

>>91
use VIM to compose the text which would compose the text which would compose the text which would become macro/command executed by VIM
I don't get it

>>92
Using VIM inside command mode. i.e. at the point you enter commands/macros

In vim you have your shell at your finger tips. Just start with a bang and you can easily include output from another program or pipe line into your text, or you can simply run a program for its effect such as make. You have a current directory and opening and writing files is relative to where you are.

The concept of second order #define will help
#define VIM_MACRO VIM_TEXT
#define VIM_MACRO_LEVEL2 VIM_MACRO
#define VIM_MACRO_LEVEL3 VIM_MACRO_LEVEL2
You're using only the first layer

>>86
you have a linux system but configuring and editing is considered superior and preferable to actually using it.
So not only do you not know this editor, you don't know that operating system.

Sweet mother of ignorance, batman.