517 karma · joined January 8, 2019
Idk the Mission is pretty crazy, too
(global-set-key "\C-w" 'backward-kill-word)
(global-set-key "\C-x\C-k" 'kill-region)
(global-set-key "\C-c\C-k" 'kill-region)
;; https://www.reddit.com/r/emacs/comments/5jbvc3/kill_is_now_cc_ck_instead_of_cw/https://github.com/cheat-engine/cheat-engine/issues/60#issue...
(ns foo.bar
(:refer-clojure :exclude [print] :rename {print println}))
(print "Should have a newline")Christopher Havens, a convicted murderer serving a twenty-five-year sentence, made a world-class discovery in mathematics; from his prison cell.
https://dr-younes-henni.medium.com/from-murderer-to-mathemat...
Edit: My curiosity regarding USENET was piqued after seeing DFeed on here, a forum front end to USENET, made for and in use at forums.dlang.org.
Two major modes can not be active at the same time, one major mode, N minor modes to a buffer.
For me, my emacs config, less is more. I think often about which packages can be commented out of my .emacs.
2. I rarely debug issues-- I dont really program my editor much, preferring macros or regex to manipulate buffers, though if I am having editor / external package issues and am in a rush I'll just use a temp emacs -Q, but my config doesn't change that often anymore, so I havent yet had to do that this year. I've been through several emacs bankruptcies over the years, at least one because I couldn't figure out why everything sucked/was slow.
3. I used spacemacs for a while (6m-1y ish), I liked the layers concept and it was easy to use, but there is a lot more to it, so its more complex than emacs. Further, emacs+use-package+which-key got me most of the experience I liked from it, with less resource use, less tricky bugs, and I was already more comfortable with emacs bindings than vi.
Location: Florida, USA
Remote: Yes
Willing to relocate: Yes, with assistance
Technologies: PHP, SQL, HTML, JS, Ruby, Ruby on Rails, Clojure, Linux
Résumé/CV: https://docs.google.com/document/d/e/2PACX-1vSgYY1p2N0uTbfv7qF32lGDl3j_y8rR0YjjIE2Ld9LG1W84-ceRsux8n9eTV1FRjH00r9PkyPTROEJF/pub
Email: see resume