emacs-anywhere
ivy-lsp-current-buffer-symbols
| emacs-anywhere | ivy-lsp-current-buffer-symbols | |
|---|---|---|
| 4 | 1 | |
| 1,067 | 0 | |
| - | - | |
| 0.0 | 1.8 | |
| almost 3 years ago | about 3 years ago | |
| Shell | Emacs Lisp | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
emacs-anywhere
-
Ask HN: Do Emacs users feel as stuck without Emacs, as Vim users do with Vim?
Sure, but there are things you can do to improve this. Browserplugins and others. See for instance:
https://github.com/zachcurry/emacs-anywhere
-
Can emacs be used as a backend like Neovim is for VSCode?
Someone mentioned Emacs Anywhere in a different thread. Looks like it could apply to your use case.
-
Does anyone here live inside emacs? can you share your workflow if you do?
You may also be interested in Emacs Anywhere, which lets you open an ephemeral Emacs buffer to edit text that then gets copied into a text box. This bridges the interface of non-Emacs applications you have to use with the editing experience you've come to expect from Emacs.
-
From Vim to Emacs in Fourteen Days
As always, the Emacs experience is better: https://github.com/zachcurry/emacs-anywhere
:)
ivy-lsp-current-buffer-symbols
-
From Vim to Emacs in Fourteen Days
I would say that what areally changes the game is to use evil (vi style bindings, 95% stays the same) with Emacs so you keep the muscle memory and you can keep making use of the common ex commands.
I have gone back and forth between vim and emacs, usually for a bunch of years each time before currently settling on emacs with Doom. With the nativecomp branch, it's actually pretty snappy and doom emacs is a great setup to get started without drowning in the amount of configuration.
I would say that I just love vim style input and modal editing, but doing that on top of emacs with evil mode and elisp is a better match for me than vimscript. The feedback loop you get with LISP and emacs is incredible when tweaking things to your liking.
Every function is accessible, there is just a global scope and you can call pretty much anything. It's sounds like an horrible idea, but it also means you can quickly hack stuff by reusing the internals of a package you like.
For example, it took me half an hour to initially POC this https://github.com/jhchabran/ivy-lsp-current-buffer-symbols by just skimming through the emacs-lsp codebase and randomly trying funcs in the repl to get an idea of what each function was doing.
What are some alternatives?
lem - Common Lisp editor/IDE with high expansibility
vim-anywhere - Use Vim everywhere you've always wanted to
lsp-dart - lsp-mode :heart: dart
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
emacs4cl - A tiny DIY kit to set up vanilla Emacs for Common Lisp programming
makem.sh - Makefile-like script for linting and testing Emacs Lisp packages
public
emacs-application-framework - EAF, an extensible framework that revolutionizes the graphical capabilities of Emacs
.emacs.d - My [old] Emacs Config. I've moved to Doom now 👇
.config - ⚙️ Bootstrappable user environment for macOS & Ubuntu
helm-lsp - lsp-mode :heart: helm