emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

nit(mu4e): neutralize comments

Browse source 
Some of our comments/docs can come off as disparaging or snide. They're
glimpses of unfiltered frustration or snarky rubber ducking gone too
far, something I can totally sympathize with, as a scatterbrained
tinkerer, unwittingly made responsible for a lot of work that isn't mine
because of Doom's position as a middleman. But now that Doom has a
veritable userbase, I'd like to hold it to a higher standard.

Light-hearted banter and aired grievances in our source code,
documentation, or community are fine if focused on the problem or the
personal/shared experiences of the community (things that offer value or
amusement to others), but it is never acceptable to attack people or
their efforts. Especially not the very people on whose shoulders Doom
stands.

I sincerely apologize if these have offended you.

Amend: b07614037f
This commit is contained in:
Henrik Lissner 2022-08-10 23:06:45 +02:00
parent 02bb28dc82
commit 3239ab8b2e
No known key found for this signature in database
GPG key ID: B60957CA074D39A3
6 changed files with 16 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

13
modules/term/eshell/autoload/backport.el
View file

@ -3,14 +3,13 @@
;; DEPRECATED Remove this when we drop Emacs 27 support.
;; HACK Eshell resets its keymap every time `eshell-mode' is enabled. Why? It
;; is not for us mere mortals to question! Anyhow, we undo this brilliant
;; design by backporting the fix from Emacs 28, so keys can be bound to
;; `eshell-mode-map' & `eshell-command-map' like any normal keymap,
;; rather than in a hook.
;; HACK Eshell resets its keymap every time `eshell-mode' is enabled. This is
;; fixed in Emacs 28+, but this file backports that fix for 27 users. This
;; way, keys can be safely bound to `eshell-mode-map' and `eshell-command-map'
;; like any normal keymap, rather than a hook.
;;
;; Fun fact: there's a "FIXME What the hell?!" above the offending line
;; in esh-mode.el.
;; Fun fact: there's a "FIXME What the hell?!" above the offending line in
;; esh-mode.el.
;;;###autoload
(defvar eshell-mode-map