Comments (5)
Going to take a bit of a different stance: I personally like the experimental features and aggressive changes and fast development pace. If I don't like a particular feature, I'll modify them. I'd like to keep Hydra and see what it can bring.
from lispy.
I have the same opinion: lispy
is very far from stable. I keep trying new ideas; some of
them work, some of them don't work. But to get the really good ones I have to try a lot of
new ideas.
Besides, (require 'hydra)
does absolutely nothing to modify the behavior of your Emacs.
It just defines a couple of macros and nothing is done unless the user calls these macros
in her config. What I did so far, was to make the previously unbound z into a
Hydra. No other behaviors were changed. But you should expect that x will
become a Hydra eventually, possibly with current behavior as a fallback through a custom
var.
Note that this is completely different from the currently very popular evil
package which
installs and enables undo-tree
even when evil-mode
is not on.
If you like to be conservative, you can stick to stable versions of lispy.
Each time I release a new version, I list the user-visible changes, so that you can modify
them if you want in your own config.
Btw, here's my personal config; I don't just merge it into lispy willy-nilly:
(use-package lispy
:load-path "~/git/lispy"
:init
(progn
(define-key lispy-mode-map (kbd "φ") 'lispy-parens)
(define-key lispy-mode-map (kbd "σ") 'lispy-braces)
(define-key lispy-mode-map (kbd "ρ") 'lispy-brackets)
(define-key lispy-mode-map (kbd "θ") 'lispy-quotes)
(define-key lispy-mode-map (kbd "C-φ") 'lispy-parens-down)
(define-key lispy-mode-map (kbd "χ") 'lispy-right)
(define-key lispy-mode-map (kbd "C-M-a") 'lispy-beginning-of-defun)
(define-key lispy-mode-map (kbd "C-x C-j") 'lispy-debug-step-in)
(define-key lispy-mode-map (kbd "C-8") nil)
(define-key lispy-mode-map (kbd "C-9") nil)
(define-key lispy-mode-map (kbd "<return>") 'lispy-alt-line)
(define-key lispy-mode-map (kbd "RET") 'lispy-newline-and-indent-plain)
(define-key lispy-mode-map (kbd "C-M-h") 'lispy-backward)
(setq lispy-helm-columns '(1 46 51 80))
(setq lispy-no-permanent-semantic t)
(set-face-background 'lispy-command-name-face "#d8d8f7")))
from lispy.
Please push stable version of lispy to http://stable.melpa.org/packages/ so I can install it using package.el.
from lispy.
It's already there at http://stable.melpa.org/#/lispy.
from lispy.
Sorry, I didn't see it in the *Packages*
buffer after installing it but I can get it at http://stable.melpa.org/packages/ , it turns out, if you've already installed it, there will not be another one from other repo, I have to remove the installed one and refresh the buffer.
BTW, if it is possible, please do not put it into lispy stable version, I know hydra won't do a thing or modify the behavior of my Emacs unless I call it manually. The thins is, if I got something in my disk but I never use it, I will just delete it, but if I delete hydra, the hydra will be downloaded again once I update lispy.
from lispy.
Related Issues (20)
- `make test` fails
- Repeat self-insert-command does not. HOT 4
- Package specifier is interpreted as start of new symbol in Common lisp. HOT 6
- EOL comment makes ";" comment one more s-exp
- `(#:a->b)` is formatted as `(#:(ly-raw symbol "a->b"))` HOT 2
- lispy unexpectedly expands shorthands in elisp HOT 1
- lispy-toggle-thread-last fails with comments HOT 1
- Consider importing gnureadline instead of readline when necessary
- Consider making native completion optional or consistent with "python-shell-completion-native-enable"
- Feature request: possibility to enable just some of the keybindings.
- `lispy-tab` doesn't respect `indent-tabs-mode`
- Add support for treesit mode
- Add support for Fennel and/or Lua HOT 1
- conflicting key mapping in evilcp theme?
- Error with Clojure evaluation HOT 7
- Port to R?
- Numbered anonymous function arguments are being incorrectly auto-formatted
- Fix warning on Emacs 30 related to deprecated (defadvice) macro
- jedi should not be imported into the active (lispy--python-proc) HOT 2
- org-elements "cannot be used in non-org buffer"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lispy.