TakeV/spacemacs
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2024-10-22. You can view files and clone it, but cannot push or open issues or pull requests.
spacemacs/layers/+lang/faust/packages.el

37 lines
868 B
EmacsLisp
Raw Normal View History

add faust-layer, remove faust from extra-langs My first spacemacs layer, total elisp newb. Does what it says in the README, with one bug: I have auto-completion-enable-snippets-in-popup t in my .spacemacs In faust files, only yas-keys that have a similar word in an open buffer show up in the company menu. Example: with no open buffers ne doesn't show a company menu, if a file has the word nent in it, I get a menu with ne -> nentry (the snippet) and nent. having ne$AnyTwoCharacters in the file also works, but just ne or nen doesn't.
2016-02-11 19:14:46 +00:00
;;; packages.el --- faust layer packages file for Spacemacs.
;;
update copyright to 2020
2020-09-16 21:34:40 +00:00
;; Copyright (c) 2012-2020 Sylvain Benner & Contributors
add faust-layer, remove faust from extra-langs My first spacemacs layer, total elisp newb. Does what it says in the README, with one bug: I have auto-completion-enable-snippets-in-popup t in my .spacemacs In faust files, only yas-keys that have a similar word in an open buffer show up in the company menu. Example: with no open buffers ne doesn't show a company menu, if a file has the word nent in it, I get a menu with ne -> nentry (the snippet) and nent. having ne$AnyTwoCharacters in the file also works, but just ne or nen doesn't.
2016-02-11 19:14:46 +00:00
;;
;; Author: Bart Brouns <bart@magnetophon.nl>
;; URL: https://github.com/syl20bnr/spacemacs
;;
;; This file is not part of GNU Emacs.
;;
;;; License: GPLv3
;;; Code:
(defconst faust-packages
Unify packages list parentheses style problem: some layer packages lists have the open and closing parentheses on the same line as the first and last listed package, but most seem to have them on a separate lines. solution: put the open and close parentheses on separate lines, except for lists with only a single package, they are written on the same line as the variable name and parentheses. fix the lists indentation
2018-11-20 19:55:37 +00:00
'(
company
add faust-layer, remove faust from extra-langs My first spacemacs layer, total elisp newb. Does what it says in the README, with one bug: I have auto-completion-enable-snippets-in-popup t in my .spacemacs In faust files, only yas-keys that have a similar word in an open buffer show up in the company menu. Example: with no open buffers ne doesn't show a company menu, if a file has the word nent in it, I get a menu with ne -> nentry (the snippet) and nent. having ne$AnyTwoCharacters in the file also works, but just ne or nen doesn't.
2016-02-11 19:14:46 +00:00
faust-mode
Unify packages list parentheses style problem: some layer packages lists have the open and closing parentheses on the same line as the first and last listed package, but most seem to have them on a separate lines. solution: put the open and close parentheses on separate lines, except for lists with only a single package, they are written on the same line as the variable name and parentheses. fix the lists indentation
2018-11-20 19:55:37 +00:00
yasnippet
))
add faust-layer, remove faust from extra-langs My first spacemacs layer, total elisp newb. Does what it says in the README, with one bug: I have auto-completion-enable-snippets-in-popup t in my .spacemacs In faust files, only yas-keys that have a similar word in an open buffer show up in the company menu. Example: with no open buffers ne doesn't show a company menu, if a file has the word nent in it, I get a menu with ne -> nentry (the snippet) and nent. having ne$AnyTwoCharacters in the file also works, but just ne or nen doesn't.
2016-02-11 19:14:46 +00:00
faust: refactor layer Add a funcs.el. Fix `use-package` usage. Modify key bindings to meet conventions. Prefix function with `spacemacs/`
2016-03-22 00:33:35 +00:00
(defun faust/post-init-company ()
Refactor and simplify company backends declaration Enabling a company backend for a specific mode was a tedious tasks with code scattered at different locations, one for local variable definitions, one for company hook function definitions and another where the backends were pushed to the local variables (which was problematic, since we ended up pushing the same backends over and over again with `SPC f e R`, pushes have been replaced by add-to-list calls in the new macro). All these steps are now put together at one place with the new macro spacemacs|add-company-backends, check its docstring for more info on its arguments. This macro also allows to define arbitrary buffer local variables to tune company for specific modes (similar to layer variables via a keyword :variables) The code related to company backends management has been moved to the auto-completion layer in the funcs.el file. A nice side effect of this move is that it enforces correct encapsulation of company backends related code. We can now easily detect if there is some configuration leakage when the auto-completion layer is not used. But we loose macro expansion at file loading time (not sue it is a big concern though). The function spacemacs|enable-auto-complete was never used so it has been deleted which led to the deletion of the now empty file core-auto-completion.el. The example in LAYERS.org regarding auto-completion is now out of date and has been deleted. An example to setup auto-completion is provided in the README.org file of the auto-completion layer.
2017-01-02 05:39:04 +00:00
(spacemacs|add-company-backends :modes faust-mode))
add faust-layer, remove faust from extra-langs My first spacemacs layer, total elisp newb. Does what it says in the README, with one bug: I have auto-completion-enable-snippets-in-popup t in my .spacemacs In faust files, only yas-keys that have a similar word in an open buffer show up in the company menu. Example: with no open buffers ne doesn't show a company menu, if a file has the word nent in it, I get a menu with ne -> nentry (the snippet) and nent. having ne$AnyTwoCharacters in the file also works, but just ne or nen doesn't.
2016-02-11 19:14:46 +00:00
faust: refactor layer Add a funcs.el. Fix `use-package` usage. Modify key bindings to meet conventions. Prefix function with `spacemacs/`
2016-03-22 00:33:35 +00:00
(defun faust/init-faust-mode ()
(use-package faust-mode
Revert "Defer packages by default using use-package-always-defer" This reverts commit 29c78ce841ee5a99bb4077a2862afc96c8136107 and all other fixes that have been made afterwards. The motivation is that use-package is seen by many as a replacement for `require`. Is use-package always defer the loading of packages then is breaks this use case, this does not respect POLA so even if it was making Spacemacs loading faster (up to 3s faster on some startup on my machine) we just cannot use it, it would be irresponsible. Spacemacs should be easy to use, loading performance will come with time but it is not a priority.
2018-03-04 04:37:53 +00:00
:defer t
faust: refactor layer Add a funcs.el. Fix `use-package` usage. Modify key bindings to meet conventions. Prefix function with `spacemacs/`
2016-03-22 00:33:35 +00:00
:mode "\\.\\(dsp\\|lib\\)\\'"
Refactor jump to definition This commit defines: - spacemacs-default-jump-handlers: a list of functions that can jump to definition in ALL modes. - spacemacs-jump-handlers-MODE: a list of functions that can jump to definition in MODE. - spacemacs-jump-handlers: a buffer-local list of functions that can jump to definition. This is made up of the values of the two previous variables whenever a given major mode is activated. - spacemacs/jump-to-definition: a function that tries each function in spacemacs-jump-handlers in order, and stops when one of them takes us somewhere new. - spacemacs|define-jump-handlers: a macro that * defines spacemacs-jump-handlers-MODE, possibly filled with initial functions * defines a function that is added to the hook of the given MODE * binds “SPC m g g” of that MODE to spacemacs/jump-to-definition This is an attempt to harmonize all the different approaches to jumping. Specifically, - Existing intelligent jump packages that work for only a single mode should go to the beginning of spacemacs-jump-handlers-MODE. E.g. anaconda for python, ensime for scala, etc. - Packages like gtags that work for several modes (but potentially not all) and which is dumber than the intelligent jumpers should go the the END of spacemacs-jump-handlers-MODE. - Packages like dumb-jump that work for all modes should go to spacemacs-default-jump-handlers. In all cases the order of the jump handlers in each list should be from most to least intelligent. Fixes #6619
2016-08-13 13:43:37 +00:00
:init
(progn
(spacemacs/set-leader-keys-for-major-mode 'faust-mode
"cf" 'spacemacs/faust-to-firefox
"cg" 'spacemacs/faust-to-jack-gtk
"cq" 'spacemacs/faust-to-jack-qt))))
faust: refactor layer Add a funcs.el. Fix `use-package` usage. Modify key bindings to meet conventions. Prefix function with `spacemacs/`
2016-03-22 00:33:35 +00:00
(defun faust/post-init-yasnippet ()
(add-hook 'faust-mode-hook 'spacemacs/load-yasnippet))
Reference in a new issue Copy permalink