51–60 of 131 posts
Earlier quoted context omitted.
Someone who uses vim daily will surely not struggle with vi.
You are right about that. What you will miss though, are the plugins and customization while making big edits.
Earlier quoted context omitted.
Magit is probably the easiest one for casual devs to appreciate. "M-x magit" get a nice list of the status of the files in the current branch. After you mark which ones you want to keep by moving up and down pressing s(tage) u(nstage) you just press "c c" and write your commit message. Then you press P and your git repo is up to date. At a previous job the head engineer flagged the number of commits I was making as a…
> "M-x magit" get a nice list of the status of the files in the current branch. Except it will randomly split your frame and show up in a seemingly arbitrary location - often obscuring what you're working on. I find the whole layout system in Emacs completely chaotic. I guess it comes with the flexibility (VS a fixed system like most Ides) nor do I have any particular solution in mind I'm curious if anyone has tamed…
Year after year I find myself using vscode instead of emacs for almost everything. Until org-mode support in vscode improves, I'll keep using emacs for that.
I keep trying VS Code, but I hate how when I split the screen three wide ("splits") it wants to open "editors" in each of the columns, even if it's the same file. I want a "buffer" like Emacs has that can be called up into any of the "splits" without reopening the file. I disable the tabs display, but when I visit a file in each of the three columns (i.e. what in Emacs would be calling a buffer into a window) I end u…
I don't see why people are still using 1970s-era IDEs in 2023. Sure, it's a joke that emacs and vim users are at loggerheads, but name me one user of either who isn't a graybeard at this point. And specifically a graybeard who refuses to use more modern tools.
Being old doesn't imply something is bad. Should we be asking what Emacs and Vim have done right so that they're still being used 50 years later?
I don't see why people are still using 1970s-era IDEs in 2023. Sure, it's a joke that emacs and vim users are at loggerheads, but name me one user of either who isn't a graybeard at this point. And specifically a graybeard who refuses to use more modern tools.
I'm not an old greybeard (in my 20s) and I solely use Emacs. What's "modern tools"? Emacs has everything; with the Language Server Protocol it is exactly like VS Code and the like, with autocomplete, find definitions, native tree-sitter support. It can even read PDFs, images, man/info pages, browse the web. I don't see any advantage that VS Code has over Emacs. PS. Try Doom Emacs and evil-mode: https://github.com/doo…
I don't see why people are still using 1970s-era IDEs in 2023. Sure, it's a joke that emacs and vim users are at loggerheads, but name me one user of either who isn't a graybeard at this point. And specifically a graybeard who refuses to use more modern tools.
Year after year I find myself using vscode instead of emacs for almost everything. Until org-mode support in vscode improves, I'll keep using emacs for that.
I keep trying VS Code, but I hate how when I split the screen three wide ("splits") it wants to open "editors" in each of the columns, even if it's the same file. I want a "buffer" like Emacs has that can be called up into any of the "splits" without reopening the file. I disable the tabs display, but when I visit a file in each of the three columns (i.e. what in Emacs would be calling a buffer into a window) I end u…
Earlier quoted context omitted.
> Yes, if you're talking about a timeframe of ~50 years, use vim and emacs. There isn't any compromises that make vim or emacs less useful than those tools with much less longevity. They are just as good as an editor to even those who don't care if they will be around 50 years from now.
I used vim (and still using it for non-coding text editing today) but I just don't feel it's so powerful that it's comparable to IDEA. Of course it's probably because I haven't properly taken time to learn and configure it. I only know how to move cursor around, search/replace and enable syntax highlighting. But that's the point: I don't want to take a significant amount of time to learn and configure an editor. I wa…
Earlier quoted context omitted.
Literally changing the editor code, to do whatever you want. Emacs is a lisp (elisp) environment mostly with a small C based core for performance sensitive primitives. But the user code is at the same "level" as the Emacs core code. This is very different from most extensible editors, where extensions are sandboxed and have a limited, controlled API to the core editor, which is kept separate. This makes Emacs very "m…
> small C based core Count before you post; Emacs now boasts over 300,000 lines of C. "Encompassing Massive Amount of C Source"
Emacs 29.1, excluding the test directory; top ten languages:
all SLOC=2618374 (100.00%) LLOC=182918 in 2584 files
elisp SLOC=1188181 (45.38%) LLOC=0 in 1566 files
man SLOC=501820 (19.17%) LLOC=0 in 48 files
C SLOC=387169 (14.79%) LLOC=159681 in 317 files
Texinfo SLOC=288384 (11.01%) LLOC=0 in 182 files
Lisp SLOC=175786 (6.71%) LLOC=0 in 1 files
Objective-C SLOC=18289 (0.70%) LLOC=8480 in 8 files
Tex SLOC=16031 (0.61%) LLOC=0 in 23 files
m4 SLOC=10436 (0.40%) LLOC=0 in 133 files
shell SLOC=6819 (0.26%) LLOC=0 in 28 files
C++ SLOC=6240 (0.24%) LLOC=2924 in 5 files