251–260 of 265 posts
Earlier quoted context omitted.
You understate how great tramp is. It is what allows me to simply not care whether a file system is local or remote. They all behave like local file systems under tramp.
Describing Emacs using English is necessarily an understatement. It can only be properly described using Lisp.
Earlier quoted context omitted.
Ok let me be very honest here, let's look at both editors learning curves - vi/vim You need to learn to open a file, edit it, move around and exit and the edit/view mode. Everybody learns how to do it. At first it sucks but you can learn this in 5 min. Nothing too hard, and yes, do use the direction keys, it's not the 70s anymore. From there you can learn other things - Emacs You try reading anything about it, there'…
> use the direction keys, it's not the 70s anymore. In my experience, the fact that I can navigate a file without taking my hands off the home row far outweighs any disadvantages hjkl might have. With emacs, the big point is that you can do so many things in it that you never have to leave it; that also means once you have the keyboard shortcuts memorized, you can use them everywhere - besides editing text, emacs can…
In my experience, most (if not all) of the people who use Vim or Emacs are programmers — and I am including sysadmins etc. in the wide category of programmers — and a programmer typically spends far more time thinking about what to type than the actual typing[1]. So I don’t see how the speed of typing is synonymous with productivity.
[1] Unless it’s a Java programmer — they spend most of their time typing — just kidding.
Earlier quoted context omitted.
That's always funny. I have the same reaction with IDE users who vocally disdain my use of Vim. Usually, I find they're copying and pasting with a mouse in a solitary window in the centre of the screen whilst boasting about syntax highlighting. :D Of course it's great to see someone who actually really does know any piece of software give a demo of how they use it. For Vim newbies I'd point people first to the Vimtut…
Why not both though? Both Qt Creator and Visual Studio code have quite good Vim Integration and their IDE features dwarf Vim with tons of plugins. I use all three for various purposes, but an IDE is a very useful things when working with languages that can take advantage of it.
Earlier quoted context omitted.
Very difficult to do with free software and completely irrelevant really. At some point in your life it's OK to accept that you're the weird one. We're the weird ones. Donald Knuth, Richard Stallman, Guido van Rossum, Rich Hickey et al are the weird ones. I don't know why emacs is such a barrier to everyone else or why vim is so attractive. But I don't understand most other humans about most things.
Ok let me be very honest here, let's look at both editors learning curves - vi/vim You need to learn to open a file, edit it, move around and exit and the edit/view mode. Everybody learns how to do it. At first it sucks but you can learn this in 5 min. Nothing too hard, and yes, do use the direction keys, it's not the 70s anymore. From there you can learn other things - Emacs You try reading anything about it, there'…
";; This buffer is for text that is not saved, and for Lisp evaluation. ;; To create a file, visit it with C-x C-f and enter text in its buffer"
It comes with a Menubar as found on most applications and rightmost is one labeled help, the first entry goes to the tutorial
"Emacs tutorial. See end for copying conditions.
Emacs commands generally involve the CONTROL key (sometimes labeled CTRL or CTL) or the META key (sometimes labeled EDIT or ALT). Rather than write that in full each time, we'll use the following abbreviations:
C- means hold the CONTROL key while typing the character Thus, C-f would be: hold the CONTROL key and type f. M- means hold the META or EDIT or ALT key down while typing . If there is no META, EDIT or ALT key, instead press and release the ESC key and then type . We write for the ESC key.
Important note: to end the Emacs session, type C-x C-c. (Two characters.) To quit a partially entered command, type C-g. To stop the tutorial, type C-x k, then at the prompt. The characters ">>" at the left margin indicate directions for you to try using a command. For instance:
>> Now type C-v (View next screen) to scroll down in the tutorial. (go ahead, do it by holding down the CONTROL key while typing v). From now on, please do this whenever you reach the end of the screen."
It goes on at length covering all basic aspects of using emacs. Under the help menu there is also an extensive manual.
If this isn't discoverable enough a logical response would be to type Emacs tutorial into your favourite search engine and read at least one of the results. You say "Usability problems are never the fault of the user." and your not wrong per se but tools have intended audience and reasonable expectations. Scalpels and coffee pots are made for different users and its challenging to make a scalpel that would enable a surgeon to remove an appendix without having to crack a book.
Microsoft office which is aimed at a much broader and less skilled user base makes it very easy to enter a little text but its very normal for users to receive training, google for answers, and RTFM.
Regardless of what anyone hopes neither vim or emacs are much used by random joe to read their email they are tools made by technical people for technical people.
Given the audience I don't think its unreasonable to suppose that people who bypass both tutorials, and manual in favour of describe bindings and leave without a pit stop at the search engine might be the cause of their own discontent.
Let me make a wild guess here. You got frustrated. Took a minute to consult google to figure it out and moved on but you left that part out because it didn't support your position.
Earlier quoted context omitted.
On the contrary: with vim you have to write everything yourself over and over. With emacs you capture it in a Lisp function once and never write it again.
But using the alt and ctrl keys is super duper awkward.
If you like vi, Evil mode exists.
If you like modal editing, God mode exists.
If you like sequences, Hydra exists.
If you like chords, remapping caps lock to control exists.
Earlier quoted context omitted.
Why not both though? Both Qt Creator and Visual Studio code have quite good Vim Integration and their IDE features dwarf Vim with tons of plugins. I use all three for various purposes, but an IDE is a very useful things when working with languages that can take advantage of it.
Does any major platform really "dwarf" any other at editing text?
Earlier quoted context omitted.
Why not? Do Emacs users usually use other OS than Linux?
The fact that the subreddit is called r/linux instead of r/gnulinux is a major turnoff to emacs users.
Earlier quoted context omitted.
That brought back memories. When I was a kid I liked to poke around executables in the MS-DOS world. Hex editors were limited in the sense that they wouldn't let me insert bytes into the file, just edit existing ones. Because I didn't have access to an disassembler or an assembler (they were sold at stores but they were too expensive for me), I wrote a simple program that would convert a binary file into a text file…
it's a bit more involved than just hex.... it specifies address ranges and data that goes into those address ranges + more see https://en.wikipedia.org/wiki/Intel_HEX
I'm always happen to see when a uC vendor IDE keeps the elfs and the programmer takes elfs.
I still use the original, AT&T vi since I grew up on UNIX and Solaris 2.5.1 was my first UNIX OS after using my Amiga. Even when I’m on a GNU/Linux variant, I run vim by calling vi, primarily because syntax highlighting enrages me to no end. vi won because it came with every UNIX by default, and when one is in a cold server room connected to /dev/console via serial port at 3 o’clock in the morning, one quickly learns…
FWIW, you can compile emacs without support for X11, and you can run it in the terminal my adding the "-nw" parameter. Not that I want to interfere with your choice of editor. ;-)