Treesitter started freaking out because you either need to TSInstall vimdoc, or you need to TSUpdate. Your vim helpdoc treesitter grammar is either outdated, or doesn't exist
well if you didnt have time for linux you wouldnt be using NixOS becasue of all distros one that wasted most of my time was nixOS, Once i setup any linux i can fairly well use it without much problems but due to NixOS being well NixOS unless i do stupid shit i really maintain my system in trully maintainable way when it comes to custom tools i built and shit. And part of that is lack of documentation and well bad documentation other part is insistance on using a what is essentially trying to be a programming configuratuin language Nix which doesnt serve either role at all and its just horrible why cant it just use yaml for basic usage. In many instances there are 3-5 ways to do exactly the same thing and only 1-2 are actually correct. I personally say one that doesnt waste time is Fedora silverblue or more likely ublue becuase as a containers guy i already know how to build a custom image with known industry standard tooling of OCi
so you don't have time for it but you go on to show how much time you waste with it. clickbait trash. all these videos are just a big dick touching sword fight.
But take this debate seriously you can get vim emulation almost any editor, IDE including emacs. In addition, emacs can be used with modern keybinding (i.e. ergoemacs) There is no reason to argue which one is the better or worse. Use whatever you want.
WHat is this Ginger Three Musketeers looking Luke Smith impersonator doing on my feed. I'm looking forward to rants about how witches are ruining our medieval society and culture, and how the only way to recieve redemption is taking part in the crusades.
Emacs doesn't follow UNIX's philosophy because GNU is Not UNIX, it is the next thing. GNU borrows a lot from UNIX because UNIX was very important back then, but it builds upon it. Doing one thing well is important, but sometimes you need to do two or more things in the same program. Emacs certainly has some jank because of its age, but how many programs made in 1984 or before do you know that are still being used as widely as Emacs is? This is a problem that can be and is being solved by more modern packages, so it will only get better. On the topic of packages, you can absolutely use file managers other than dired, people just gravitate towards the default features because, more often than not, they already do a lot. Maybe not in an obvious way to new users because, again, Emacs is very old, it precedes the alt key being universally called "alt" and the concepts of copying and pasting as we know today, so does Vi. Anyway, learning Vim first and then expecting Emacs to have the same philosophy is a mistake that I see a lot of people making, that I myself did when I was learning, but eventually I came to prefer Emacs and its philosophy. Because of that I generally recomend learning to use Emacs first, and then Vim. Heck, you can even simulate Vim inside Emacs with ease, how difficult would it be to do the opposite? Vim is just one form of modal editing, there are various, God Mode, Meow, Kakoune, etc. I think Emacs is worth the effort, but ultimately it is a matter of taste and need, computers and tools in general offer a way to do something that you need in a way that you like.
Linux, Emacs, Vim, Nix, all those things are a matter of investment. You learn all those things hoping that eventually they'll save more time than it took to learn them, and in my experience that was the case.
I find the dependency graphing highly attractive. I recently installed debian but I may switch to this. I never liked the concept of apps and containerized environements just for apps.
My take on 5:31 regarding modality is many of the things listed as 'Modes' in Emacs are termed 'Options' (or something similar) in Vim. IMO it's just different terminology for the same thing. I don't think that these differences in phrasing constitute an improvement of one editor over another. Example: I see that one of the modes listed in emacs is Display-Line-Numbers. Maybe I don't understand emacs, but as far as I'm aware, that is also an option in the majority of editors, but you wouldn't necessarily be calling visual studio code a 'modal editor'. I always try and minimize bias but I do have a personal bias towards Vim as I have never fully gotten into Emacs (not for lack of trying though) and I welcome any corrections, as I know that I might be wrong on the specifics here. But this is from my viewpoint as someone who uses Vim.
kickstart.nvim with remapped iTerm or Tmux for pane splitting is such a good developer experience that I don't see myself switching anytime soon. I'd be completely content if I was able to open browser panes as well. What's the best tiling window manager out there?
I use ranger... its great until I accidentally open up my nix store directory and it struggles with that many items in one directory. Also randomly over the years image preview will work or not work and I don't even know why (after hours of debugging). I'll check out Yazi as a possible upgrade. Its written in and configured with languages I know so should be easier to customize for my needs. Thanks for the overview. I will also note that the vlog -> screen share transition was smooth!
I've been a diehard ranger user for more years than I can count, I can't imagine living without it. But now... yazi looks like a total game changer!!! If I can configure it to use all the keybindings from ranger that are ingrained in my muscle memory, then it might just be time to finally say goodbye to ranger. Thanks a lot for this video!! Time to read yazi docs :)
@@kbprojekty Here's some things that stand out for me after using yazi for a few days now: 1. The speed - it's very noticably much faster than ranger. 2. Image preview over ssh - I can ssh to a server, run yazi there and have image previews! Very nice when managing files on my media server, which is what I often use a terminal file manager for. Now I can do it on the server itself over SSH instead of locally over NFS. 3. Async / non-blocking tasks and I/O - I can keep using the file manager even if it's loading a bunch of previews or copying large files in the background. 4. Very active development, many improvements coming. Ranger, on the other hand, seems to have stalled (v1.9.3 was released in 2019, almost no commits lately, almost 800 open issues.) 5. Movie previews (via ffmpegthumbnailer for now) - maybe not unique to yazi, but again very useful for media management (also works over SSH!) 6. I have recreated most keybindings / shortcuts I'm used to from ranger, some via yazi plugins, and the config system seems to be quite flexible/powerful so far. Haven't totally wrapped my brain around it yet though. 7. Personally I've been learning Rust for the last few years, so I'm more excited about potentially contributing to yazi than ranger. 8. Copy-on-write (e.g. for the new block cloning feature of ZFS) seems to work properly out of the box in yazi. In ranger it doesn't. I use this feature quite a bit and had to resort to silly workarounds in ranger..
Hi, I can help you in the image issue you had 3:55 The simple solution is as follows: add this line above the image #+ATTR_ORG: :width 800 THE IMAGE and that's it ✨, now you can change the width to your liking, I do 400 or 600 or 800 Hope I helped you
Thanks so much for the tip. I was using markdown, not org, so the fix was to set a variable for the max size of an image. Beyond that though, perhaps it didn't come through in this specific recording, but the scrolling around images is incredibly jumpy and I've had issues of images popping in and out, especially when multiple are on screen as once. Possible, but still far away from an experience I would describe as smooth.
I feel like I understand Emacs users now. It's basically what I feel about Obsidian "Neovim is where I get my work done, Emacs is where I have my documents look nice" is exactly what I feel about obsidian, not to mention the ecosystem and the plethora of addons
Notable points that bring me to the Emacs camp are compatibility with LSPs, the ability to partially render Latex and such, Obsidian is proprietary and uses election, and Emacs tends to be much more visually customizable. All of that said, Obsidian does appear to integrate nicely between devices. That wouldn't get me using it, but definitely something that open projects ought to take note from.
I love Luke Smith, and learn a lot from his video. This video reminds me of his. But I don’t mean your video is imitation, your opinion resembles mine that Vim and Emacs are not comparable. They focus on different jobs and solve their own problems. I do hope Neovim could get a better interface for users to discover its features. I know how to use Vim/Neovim starting from when I know how to search help pages with it. 最后 欢迎你来到深圳 玩得开心 注意安全！
@@AndrewGiraffeI don’t think Shenzhen city itself is a good place for traveling, after all it’s not a tourist city. However, it may be a good idea to visit some small restaurants, try out local foods especially those for breakfast. Guangdong province is famous in cuisine. Btw, Guangzhou city is a better place for people who enjoy local foods and culture. 玩的開心！(say in Cantonese, just imagine it)
Fair and balanced review. I use both for different purposes but your point about the self documenting nature of Emacs is why it’s my go to. On a different note, I developed a which-key like pop up menu via X11 and Wayland for user key chords. If you like which-key and key chords, you can check out the demo videos and links on my account. The look is similar to dmenu, but it supports curved borders which you seem to prefer. If you check it out I’d appreciate any feedback you might have.
Neovim imo. its faster, supports both vim _and_ lua. and it has a graphical API which is nice. Also treesitter, native lsp support, and a bunch of other stuff. (I use vim tho)
The only links the browser will accept are to Joe Rogan's podcast and Don Black's message board so you know that your echo chamber remains intact at all times
I really think the question is more about tmux vs emacs, or tmux+vim vs emacs. I use emacs, and it often feels all-consuming to me. Emacs creates the need to do everything within emacs. So on that aspect, tmux is a much more fair comparison. You can configure it to suit all your needs and navigate between different usecases very rapidly. You aren’t supposed to do all that inside nvim, which is for the most part just a text-editor. You might change files or compile code with nvim, but why would you even want to manage files or read man-pages, or use cli-tools with nvim? You have tmux. Here tmux can score easy points against emacs for usability. You don’t need a tmux framework to present all the possibilities: its a shell. Almost nothing is preconfigured nor needs configuring for new usecases. For me, 99% of the time I leave emacs to open a terminal is because it massively reduces the complexity of the task or problem. I imagine tmux is like that, but all of the time. I use emacs because of the many times something just works with doom emacs, and the times emacs-lisp makes the configuration enjoyable. Not leaving emacs feels great, and learning emacs-packages like magit also feels great. But it really makes no sense to say nvim can’t do those things, as you aren’t supposed to do them with a text-editor in the first place.
I agree with your comment. It's more convenient to see this in the context of 'workflows' than in the context of 'editors'. I would reason most people who use a console-based editor also use console-based tools. I personally control everything from the terminal except for my web browser. These things include emails, music, editing and notes, file management, git, and so on. And to wrap all of these applications together into their relative categories/workflows I use tmux, which is an absolute Godsend. I would imagine it's super convenient to not have to leave Emacs to do various things, but that convenience is also present when using Tmux. It doesn't feel as though you're switching applications, because everything is contained and running adjacently, and tmux _is_ the application at that point. (At least for me).
In my opinion, NeoVim is becoming more like Emacs, not the other way around. The Vim/NeoVim combo today holds the same position Emacs did in the mid-late 90s. Vim/NeoVim are the most poplar choice for people who can't stand bloated IDEs. They're what you are going to find the most co-workers using, the most help available for, the most commercial support for (e.g. plugins for AI code assistants), The Vim/NeoVim schism shares similarities to the XEmacs fork of Emacs. The irony is that XEmacs forked to *add* GUI to Emacs, and NeoVim forked to basically remove it (yes, I know about the various nvim guis, but my impression is they are all unpopular). Both forked to break a development bottleneck enforced by core maintainers, who were moving too slow for some peoples' tastes. The plugin and "mod" space for NeoVim is in a state of rapid evolution and churn. People talk about hacking their NeoVim config for days on end until they get it "just right," etc. There are multiple popular distros because people can't easily configure NeoVim for themselves. Setting up LSP and completion, from scratch, in NeoVim is way too convoluted right now. Talk about blindly copying and pasting config without understanding what it does! One advantage Emacs has over NeoVim is a stronger set of conventions and idioms for developing plugins. When messing with NeoVim I got the sense that the idea was "expose stuff to Lua, done, have fun!" The Emacs concepts of global and local modes, hooks, documentation attached to functions and variables *in the langage itself*, all seem absent in NeoVim. Compared to Emacs it is a free for all, and it shows. One sad irony is that Emacs has long had a good Vi emulation mode built in, for over 30 years. Evil is external only for FSF copyright political reasons. It works great, is better than Emacs' "vi-mode", but Evil will never become part of core Emacs. That is a shame, because there is an imaginable world where modal editing is a first class feature of Emacs, but that probably won't happen unless someone creates a NeoEmacs fork (maybe one that can use Lua!).
This is the most honest comparison of emacs and vim I have ever seen. Ive veen using vim (now neovim) for 6+ years, and being a unix-loving power user, I was always interested in what emacs was, given its popularity. Most people who talk about emacs give all the positives and spend time talking about what vim doesnt do, but this was a great demonstration of everyday use and what really matters. I was planning on trying emacs out some time, but this video has made me reconsider (for now!). Unix philosphy is one of the most important things to me
