general customisation guidance #128
-
hey I have been meaning to give this a go and for the most part things look great, I have a few concerns, however, how do I control what is displayed when I hit SPC, what is the name of this package and where can I edit what appears, what is the recommended way to overwrite the built in module, in particular I want to add a few things to the clojure-mode that are missing |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Hello @michaelssingh , You can take a look to Please note that MinEmacs uses |
Beta Was this translation helpful? Give feedback.
-
What about overwriting what you have here https://github.com/abougouffa/minemacs/blob/main/core/me-keybindings.el, I am trying to avoid forking this project. |
Beta Was this translation helpful? Give feedback.
-
If you want to overwrite the default keybindings you can do it using the minemacs/core/me-keybindings.el Lines 225 to 229 in 5c6739e If you don't like how a particular package is configured and you want to disable its default configuration (provided by MinEmacs) and install it in your configuration file ( Lines 58 to 73 in 5c6739e I hope this answers your question! |
Beta Was this translation helpful? Give feedback.
-
Hi! I'm still not sure how to add additional packages and how to override some general behaviours. For example I have: (use-package embark
:straight t
:bind (("C-." . embark-act)
:map embark-file-map
("V" . cust/vsplit-file-open)
("X" . cust/split-file-open))
:config
(define-key embark-url-map "X" #'dorneanu/embark-open-url-in-xwidget-webkit))
In general: How do I change the default keybindings (which by default use the leader (use-package cape
:straight t
:demand t
:hook ((prog-mode . dorneanu/set-basic-capf)
(text-mode . dorneanu/set-basic-capf)
(org-mode . dorneanu/set-basic-capf)
;; (go-ts-mode . dorneanu/set-go-capf)
(lsp-completion-mode . dorneanu/set-lsp-capf))
:general (:prefix "M-c" ; I don't really use capitalize-word
"p" 'completion-at-point
"t" 'complete-tag ; etags
"d" 'cape-dabbrev ; basically `dabbrev-completion'
"f" 'cape-file
"k" 'cape-keyword
"s" 'cape-symbol
"a" 'cape-abbrev
"i" 'cape-ispell
"l" 'cape-line
"w" 'cape-dict
"\\" 'cape-tex
"_" 'cape-tex
"^" 'cape-tex
"&" 'cape-sgml
"r" 'cape-rfc1345)
:custom
(cape-dabbrev-min-length 1)
:init
;; Add `completion-at-point-functions', used by `completion-at-point'.
;; (add-to-list 'completion-at-point-functions #'cape-history)
;; (add-to-list 'completion-at-point-functions #'cape-keyword)
;; (add-to-list 'completion-at-point-functions #'cape-dabbrev)
;; (add-to-list 'completion-at-point-functions #'cape-symbol)
(add-to-list 'completion-at-point-functions #'cape-dabbrev)
(add-to-list 'completion-at-point-functions #'cape-elisp-block)
(add-to-list 'completion-at-point-functions #'cape-file)
) The above example is from my current configuration (without minemacs). |
Beta Was this translation helpful? Give feedback.
Hello @michaelssingh ,
You can take a look to
skel/
, I'm trying to keep it updated with configuration examples. The logic of user customization is explained briefly in the README file. In a nutshell, it is recommended to configure packages inwith-eval-after-load
blocks, or by including ause-package
block inside yourconfig.el
with your extra customization. Theconfig.el
is loaded after MinEmacs modules, so it can override what has been configured before. The order of loading configuration files is described here.Please note that MinEmacs uses
straight.el
to install packages, so it is recommended to use the same package manager and not mix it up with the builtinpackage.el
. TLDR: use:s…