this post was submitted on 21 Nov 2023
1 points (100.0% liked)

Emacs

311 readers
1 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis@communick.news
raphael@communick.news
1
How can I become a more "proficient" Emacs user? Esp. in regards to developing (alien.top)
submitted 11 months ago by MailRegular8914@alien.top to c/emacs@communick.news
34 comments fedilink hide all child comments
 

I hope my question makes sense.

I am using Doom Emacs for a while now and have become fairly proficient. But I feel like whenever I am browsing emacs content online there are still many topics for me to discover. So I was wondering if there is anything that I might be "missing" yet which might help with my productivity or improve my development skills.

Sofar I what have learned, on top from my head:

  • Org/Org Agenda (refile etc.)
  • Magit
  • Vterm
  • LSP Commands
  • Multiple Cursors
  • Literal Config
  • Navigating Emacs itself (which key, debugging, reading Emacs-Lisp (abit))
  • Using Language specific commands, i.e. send buffer to repl
  • Using Undo with Vundo

Only thing I know that I still need to learn is beeing more proficient with vim keybindings, but with that I know where to start.

I know the question is quite broad, but maybe there some "killer features" worth to explore which I am not aware of yet.

I'd appreciate any input.

you are viewing a single comment's thread
view the rest of the comments
[–] ideasman_42@alien.top 1 points 11 months ago (5 children)

I'd suggest not to attempt to become proficient at Emacs for the sake of it, instead.

  • Use Emacs for whatever you need an editor for.
  • Ensure your workflow is good.
  • If you see some room for improvement, investigate packages/configuration.
  • If you need to scratch an itch, write your own commands/packages.

Once in a while you might like to play & explore areas you didn't dig into before but you don't have to. Have a nice workflow, get your work done - and leave it at that :)

For some context, packages I've developed: https://codeberg.org/ideasman42

[–] Horrih@alien.top 1 points 11 months ago

This is the way, adress pain points, don't do things for the sake of it.

You will naturally dig deeper in the things that matter to you

If you hear of some fancy new package, read/watch an introduction about it and ask yourself if it would actually solve one of your issues. If it doesn't really, pass

load more comments (4 replies)