[-] throwawayish@lemmy.ml 1 points 11 months ago

Thank you so much for all the lovely insights you've provided! Have a good one ☺️!

Re macros. If you are editing something and you need to repeat a pattern, eg. Remove every third line or whatever, you just get to your start point and press q in command mode to start recording into macro buffer . Q to quit then you can reuse it and use it as a command with @

That's so cool!

Re fonts. It’s your terminal which controls your font in windows. In wsl, eg. The font is controlled by the external windows terminal and not by wsl. It’s dependent upon your environment I’m afraid.

Hmm..., that's unfortunate. Hopefully I can find a work-around.

[-] throwawayish@lemmy.ml 1 points 11 months ago

If you have yet to do that, I strongly suggest that you go dive into using vim for a month or three before you start worrying about which plugin set you prefer.

Noted. Thank you!

For example, VSCode has a decent enough set of keybindings that it’s usable, but I still prefer console editing and on the fly macro creation.

Very interesting. Would you mind elaborating?

Speaking of which, lvim works in most terminal environments, but may require font tweaking on windows, wsl, etc.

A few weeks ago when I tried LunarVim for the first time, I had trouble assigning a different font for it than the one I prefer using in the terminal otherwise. A quick search didn't bear anything that I could use to resolve the issue. Would you happen to know if it's possible to assign a different font to LunarVim (or any Neovim distribution for that matter) than the preferred one to use in the terminal?

[-] throwawayish@lemmy.ml 1 points 11 months ago

Since childhood, they wanted to become the head of a bank; this wish -however- was more rooted in the (childish/immature) association that being at that position should mean that they've made it (monetary-wise). So, they started Finance with the belief that it would be the best step to attain that goal. Furthermore, I believe they had misinformed ideas on what studying Finance was at the time 😅,

[-] throwawayish@lemmy.ml 1 points 11 months ago

I appreciate your input. Thank you!

Also, there are too many plugins to serve the same purpose and I found it difficult (compared to neovim) to figure out the difference between them.

Interesting.

Finally, the level of customization was also less granular than what offers neovim.

Very interesting. I'd love to hear more about this. Could you elaborate?

I would add that neovim and emacs both have a steep learning curve but I personaly found the level of support and core and plugins documentation for neovim more accessible, readable, and better organized.

I wouldn't be surprised if this is in part attributable to the fact that Emacs is both an older project and is generally-speaking a bigger and/or more capable piece of software.

I completely share your vision about what an IDE should be doing. I’m old school and adhere to the “do one thing but do it right” philosophy. Also, I hate relying on one tool for several needs because if anything goes wrong it has multiple impacts.

I've often heard Emacs users pose the argument that Emacs as an Elisp interpreter does just one thing. It's just that this single thing allows the myriad of functionality it offers. So in that sense comparing it to a terminal/console seems more apt than comparing it to a text editor. I wonder what you think of that argument.

As a side note, I use neomutt as my email client and you can nicely couple neovim to it to write your emails ;)

Hehe, that's cool! Currently I'm really happy with Thunderbird so I don't expect to move away anytime soon, but I'll keep it in mind.

[-] throwawayish@lemmy.ml 1 points 11 months ago

I use Emacs + spacemacs in VI mode as a base for all my text editing

Do you specifically prefer using Spacemacs as a base over Doom Emacs? Or is the usage of Spacemacs primarily attributable to it coming earlier to the scene?

Furthermore, as you're using it in "VI mode", would it be fair to assume that you've got some experience/history with Neo(Vim) as well? If so, what led you to making the switch from (Neo)Vim to Emacs?

For dev environments I mostly use nix + direnv + direnv-mode.

Very interesting! Relying on Nix rather than Distrobox has been something I've been pondering upon. But besides the fact that I'm still very new to Nix as an ecosystem, I've also got my concerns related to what degree the containers can be sandboxed. Do you happen to have some insights on this?

[-] throwawayish@lemmy.ml 1 points 11 months ago

Hi!

I’ve briefly shared my experience with neo(vim) and emacs here.

Thanks for sharing that! I've just read through it and it was a very interesting read. Would you mind elaborating upon the following statement?

"the lack of uniformity across plugins coding which sometimes created some conflicts"

I think the main factor of choice would be to know if you prefer to build your own perfect tool with just what you need and expand as you go (i.e. neovim) or just have a do-it-all ready tool right out of the box (i.e. emacs).

That is indeed something that concerns me regarding Emacs. Like being able to surf on the internet or using it as a email client isn't quite what I expect out of my IDE 😅. I guess the extensibility should allow 'minimal' installations, but this is something I should read more into. Thanks for pointing that out!

[-] throwawayish@lemmy.ml 1 points 11 months ago* (last edited 11 months ago)

Thank you for touching upon some of LunarVim's 'oddities'!

[-] throwawayish@lemmy.ml 1 points 11 months ago

Ah okay. It has become a lot more clear what you meant. And I agree; implementation for Vi(m) keybindings is ubiquitous while the same can't be said for Emacs'. But, while Vi(m)'s keybindings define a lot of what it is and why people love to use it, the same simply can't be said for Emacs' keybindings. I'm sure there's someone out there that absolutely loves it, but it doesn't come close to how Emacs' modeless nature allows almost limitless extensibility or how 'smart', 'useful' and just plain excellent its org-mode is.

[-] throwawayish@lemmy.ml 1 points 11 months ago

As a long-time Vi user I would highly recommend giving it a shot for a solid month to see if it clicks for you.

Makes sense. Thanks for the tip!

Emacs is dead near as I can tell.

Am I correct to assume that you think that Emacs is dying? If so, would you be so kind to elaborate on why you think that's the case?

[-] throwawayish@lemmy.ml 1 points 11 months ago

Thanks! Those should provide some decent pointers.

Would it be a fair assessment to suggest that LunarVim was chosen primarily for the fact that it came out first? Like, either one Astronvim, LazyVim and NvChad might have done a similarly great job, but you were already using LunarVim and saw no reason to switch as the functionality they provide is relatively close to one another.

Furthermore, because you were already accustomed to Vim, you were able to properly utilize LunarVim as a startingpoint. As such, switching from startingpoint would only amount to more work without any real benefits.

[-] throwawayish@lemmy.ml 1 points 11 months ago

I use lunarvim almost exclusively.

Was it a very conscious choice? Like have you tried the others but (somehow) didn't like them etc? And if so, why do you prefer LunarVim over the others?

[-] throwawayish@lemmy.ml 1 points 1 year ago

This seems interesting. I didn't make the link to 'immutable'/read-only with templates. But I'll read up on it and explore the possibilities. Thank you!

view more: ‹ prev next ›

throwawayish

joined 1 year ago