Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should user-config be migrated into layer package configuration? #1

Open
keevindoherty opened this issue Sep 28, 2022 · 0 comments
Open

Comments

@keevindoherty
Copy link
Owner

There's a decent amount of additional configuration you have to do once this copilot.el package is installed. Currently, this entails placing the following lines in the dotspacemacs/user-config area of your .spacemacs file:

"Configuration for Copilot"
(setq copilot-node-executable "/usr/local/bin/node")

(with-eval-after-load 'company
  ;; disable inline previews
  (delq 'company-preview-if-just-one-frontend company-frontends))


(define-key copilot-completion-map (kbd "<tab>") 'copilot-accept-completion)
;; (define-key copilot-completion-map (kbd "TAB") 'copilot-accept-completion)

(add-hook 'prog-mode-hook 'copilot-mode)

(define-key evil-insert-state-map (kbd "C-<tab>") 'copilot-accept-completion-by-word)
(define-key evil-insert-state-map (kbd "C-TAB") 'copilot-accept-completion-by-word)

Could/should these be set as defaults at the layer level? This would make it easier to get started without additional modifications to the .spacemacs file. The path to node seems like it may have to be set by a user in the end, since this could vary on different machines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant