4 ms·

Forgive the noise, but I second this. I haven't committed a hundred key combinations to memory. I find that knowing the twenty things I need to know (which ar

Forgive the noise, but I second this. I haven't committed a hundred key combinations to memory. I find that knowing the twenty things I need to know (which are different for everyone), and having another twenty in my back pocket for once or twice a year has lasted me since 1992, and left me very satisfied indeed with emacs.

downerending 7y ago
Also seconding. Vanilla emacs is already extremely powerful, and if you're doing real work, you'll end up having to use hosts that don't have all of your wonderful enhancements installed. It's good to know vanilla emacs. Beyond that, add language modes for anything you need that's not already included. If you use 'git', 'magit' is very nice. Beyond that, helm is interesting, though very large and kind of mind-blowing. Recommend these in your ~/.emacs.d/init.el, to avoid being that guy: (setq-default show-trailing-whitespace 't) (setq-default indicate-empty-lines 't) ; try not to use tab characters ever when formatting code (setq-default indent-tabs-mode nil) (setq-default require-final-newline 'ask) (setq-default mode-require-final-newline 'ask)
- philsnow 7y ago
  > if you're doing real work, you'll end up having to use hosts that don't have all of your wonderful enhancements installed. It's good to know vanilla emacs. If you're talking about production hosts, they shouldn't really have vanilla emacs installed either. Not having your creature comforts present on production machines is a feature, like the red shell prompt / terminal background some people use, a reminder to get you to think twice and try to not do things directly in production. If you really must, just use TRAMP, it's amazing. If, on the other hand, you're talking about using somebody else's laptop to do anything, that doesn't make sense to optimize for, at least in my experience. I prefer not to even touch other peoples' laptops/keyboards.
  - downerending 7y ago
    I'm fine with not installing emacs, as long as no one ever asks me to fix their crap on those hosts. In practice, their stuff will always break, and they always will ask me to fix it. Production hosts should never be neutered. At a bare minimum, emacs-nox, strace, nmap, tcpdump, lsof. No exceptions. Tramp is great, but not all such hosts are reachable that way. > I prefer not to even touch other peoples' laptops/keyboards. Me too, but that's why they call it work.
    - mbrock 7y ago
      Hopefully the Emacs is also configured to not leave tilde backup files everywhere!
- User23 7y ago
  > Also seconding. Vanilla emacs is already extremely powerful, and if you're doing real work, you'll end up having to use hosts that don't have all of your wonderful enhancements installed. It's good to know vanilla emacs. I wonder if I'm weird, but I use a highly customized Emacs on my dev machine, but if I have to ssh into a host and edit something I just use vi there. The correct answer to vi or emacs has always been "both" for me.
  - kqr 7y ago
    I'm the same way, and I don't see why that would be so controversial. Vi(m) clearly has the better defaults, but Emacs is the better platform. (Then again, I'm the person who occasionally also uses ed just to keep it fresh in my memory, so there's that.)
    - regularfry 7y ago
      They're just optimised for different jobs. Vim for line-based editing, emacs for nested. It just so happens that editing config files on remote hosts tends to be line-based, while editing code locally involves editing nested structures. I'll happily use both on the same machine though.
  - fantispug 7y ago
    I'm the same; I use evil-mode in emacs and find the friction of switching between them small.
  - kbp 7y ago
    You can also ssh in via Emacs with Tramp, and use your highly customised Emacs to edit remotely.
- shermanmccoy 7y ago
  Linux kernel developers would not want to use the third option on your list.
  - downerending 7y ago
    magit? Why not?
    - shermanmccoy 7y ago
      Some coding styles insist on tabs. I was referring to the third line of your configuration as quoted below. ; try not to use tab characters ever when formatting code (setq-default indent-tabs-mode nil)
- dizzystar 7y ago
  for trailing whitespace: (add-hook 'before-save-hook 'delete-trailing-whitespace) This deletes all whitespace when you save a buffer.

downerending 7y ago

Also seconding. Vanilla emacs is already extremely powerful, and if you're doing real work, you'll end up having to use hosts that don't have all of your wonderful enhancements installed. It's good to know vanilla emacs. Beyond that, add language modes for anything you need that's not already included. If you use 'git', 'magit' is very nice. Beyond that, helm is interesting, though very large and kind of mind-blowing. Recommend these in your ~/.emacs.d/init.el, to avoid being that guy: (setq-default show-trailing-whitespace 't) (setq-default indicate-empty-lines 't) ; try not to use tab characters ever when formatting code (setq-default indent-tabs-mode nil) (setq-default require-final-newline 'ask) (setq-default mode-require-final-newline 'ask)

philsnow 7y ago
> if you're doing real work, you'll end up having to use hosts that don't have all of your wonderful enhancements installed. It's good to know vanilla emacs. If you're talking about production hosts, they shouldn't really have vanilla emacs installed either. Not having your creature comforts present on production machines is a feature, like the red shell prompt / terminal background some people use, a reminder to get you to think twice and try to not do things directly in production. If you really must, just use TRAMP, it's amazing. If, on the other hand, you're talking about using somebody else's laptop to do anything, that doesn't make sense to optimize for, at least in my experience. I prefer not to even touch other peoples' laptops/keyboards.
- downerending 7y ago
  I'm fine with not installing emacs, as long as no one ever asks me to fix their crap on those hosts. In practice, their stuff will always break, and they always will ask me to fix it. Production hosts should never be neutered. At a bare minimum, emacs-nox, strace, nmap, tcpdump, lsof. No exceptions. Tramp is great, but not all such hosts are reachable that way. > I prefer not to even touch other peoples' laptops/keyboards. Me too, but that's why they call it work.
  - mbrock 7y ago
    Hopefully the Emacs is also configured to not leave tilde backup files everywhere!
User23 7y ago
> Also seconding. Vanilla emacs is already extremely powerful, and if you're doing real work, you'll end up having to use hosts that don't have all of your wonderful enhancements installed. It's good to know vanilla emacs. I wonder if I'm weird, but I use a highly customized Emacs on my dev machine, but if I have to ssh into a host and edit something I just use vi there. The correct answer to vi or emacs has always been "both" for me.
- kqr 7y ago
  I'm the same way, and I don't see why that would be so controversial. Vi(m) clearly has the better defaults, but Emacs is the better platform. (Then again, I'm the person who occasionally also uses ed just to keep it fresh in my memory, so there's that.)
  - regularfry 7y ago
    They're just optimised for different jobs. Vim for line-based editing, emacs for nested. It just so happens that editing config files on remote hosts tends to be line-based, while editing code locally involves editing nested structures. I'll happily use both on the same machine though.
- fantispug 7y ago
  I'm the same; I use evil-mode in emacs and find the friction of switching between them small.
- kbp 7y ago
  You can also ssh in via Emacs with Tramp, and use your highly customised Emacs to edit remotely.
shermanmccoy 7y ago
Linux kernel developers would not want to use the third option on your list.
- downerending 7y ago
  magit? Why not?
  - shermanmccoy 7y ago
    Some coding styles insist on tabs. I was referring to the third line of your configuration as quoted below. ; try not to use tab characters ever when formatting code (setq-default indent-tabs-mode nil)
dizzystar 7y ago
for trailing whitespace: (add-hook 'before-save-hook 'delete-trailing-whitespace) This deletes all whitespace when you save a buffer.