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

Private Additional Packages possible? #2278

Closed
nugend opened this issue Jul 7, 2015 · 12 comments
Closed

Private Additional Packages possible? #2278

nugend opened this issue Jul 7, 2015 · 12 comments

Comments

@nugend
Copy link

nugend commented Jul 7, 2015

Hi, I've defined a syntax highlighting package for a language I use. It doesn't need to do anything fancy or have any additional configuration with other modes. My global defaults are perfectly fine with it.

Is there a way to use dotspacemacs-additional-packages to make spacemacs load it up? What I'm trying right now is putting the my-mode.el file into ~/.emacs.d/private and specify dotspacemacs-additional-packages '(my-mode)

That doesn't seem to work. Not quite sure where I'm going wrong.

@jasoncyu
Copy link

jasoncyu commented Jul 7, 2015

i think dotspacemacs-additional-packages is for packages in a repo like melpa. Can you just (load-file ...) and (require ...) your package in dotspacemacs/config?

@nugend
Copy link
Author

nugend commented Jul 7, 2015

That works, but would it make sense for dotspacemacs-additional-packages to also look for packages in private? I'd like to eventually make this available through MELPA (there isn't a good one already out there), but I figured it'd make sense to test it locally first.

Sorry if I'm not getting it. I'm pretty new to spacemacs and getting a hang of the emacs ecosystem.

@ghost
Copy link

ghost commented Jul 8, 2015

I'm not exactly certain what you are trying to do, but I suspect M-x configuration-layer/create-layer <RET> is what you want.

That is what I have used when trying out packages/layers I've created myself. See https://github.com/syl20bnr/spacemacs/blob/master/doc/DOCUMENTATION.org#configuration-layers for more info.

@pigmej
Copy link

pigmej commented Jul 14, 2015

create a layer and add your package as extension. (extension.el and extension folder).

@ghost
Copy link

ghost commented Jul 14, 2015

A simpler way would be to set the "dont delete orphan packages bool" in ´.spacemacs´and then just install your desired package from paradox.

@pigmej
Copy link

pigmej commented Jul 14, 2015

@endrebak you can do it already, just define dotspacemacs-additional-packages

The problem is with custom el packages that you have on disk.

@ghost
Copy link

ghost commented Jul 14, 2015

Thanks, had never used it myself. Now I better understand what it is for.

@StreakyCobra
Copy link
Contributor

It is possible to add additional packages… well, in dotspacemacs-additional-packages. To use a local package, it is possible to use there the syntax presented in LAYERS.org#packages.el or, as already explained, to use (load-file …) and (require …).

This issue having been answered, and as there was no activity last 4 months, I'm closing it. Feel free to open a new issue if you have troubles with all this ☺️

@tcfunk
Copy link

tcfunk commented Dec 16, 2015

@nugend I wasn't really able to get local packages to work, but I did get dotspacemacs-additional-packages to fetch a random github repo, if that helps you. Try something like the following:

dotspacemacs-additional-packages '(some-package
                                   (some-package2 :local (recipe
                                                          :fetcher github
                                                          :repo "someuser/some-package2"))

@adamcavendish
Copy link
Contributor

adamcavendish commented Mar 2, 2017

Use :location local will give you what you would like.

dotspacemacs-additional-packages '(some-package (some-package2 :location local))

@LeaveNhA
Copy link

@adamcavendish any documentation on that ?

@nickbarnwell
Copy link

I spent forever figuring out how to do this to run some packages from my GH account before they're accepted to MELPA and eventually ended up looking through the spacemacs source to find it.

The format is is: ($package-name :location (recipe :fetcher github :repo "gh-path"))

Recipe format is described in the MELPA documentation.

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

No branches or pull requests

8 participants