ivy-lsp-current-buffer-symbols VS helm-lsp

Compare ivy-lsp-current-buffer-symbols vs helm-lsp and see what are their differences.

ivy-lsp-current-buffer-symbols

Jump to a symbol in current buffer with an Emacs ivy buffer (by jhchabran)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
ivy-lsp-current-buffer-symbols helm-lsp
1 1
0 89
- -
1.8 1.8
about 3 years ago about 3 years ago
Emacs Lisp Emacs Lisp
- GNU General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

ivy-lsp-current-buffer-symbols

Posts with mentions or reviews of ivy-lsp-current-buffer-symbols. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-11.
  • From Vim to Emacs in Fourteen Days
    8 projects | news.ycombinator.com | 11 Mar 2021
    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.

helm-lsp

Posts with mentions or reviews of helm-lsp. We have used some of these posts to build our list of alternatives and similar projects.

What are some alternatives?

When comparing ivy-lsp-current-buffer-symbols and helm-lsp you can also consider the following projects:

lem - Common Lisp editor/IDE with high expansibility

helm - Emacs incremental completion and selection narrowing framework

lsp-dart - lsp-mode :heart: dart

lsp-docker - Scripts and configurations to leverage lsp-mode in docker environment

emacs4cl - A tiny DIY kit to set up vanilla Emacs for Common Lisp programming

emacs-anywhere - Configurable automation + hooks called with application information

helm-system-packages - A Helm interface to the package manager of your operating system

public

emacs-run-command - Efficient and ergonomic external command invocation for Emacs

.emacs.d - My [old] Emacs Config. I've moved to Doom now 👇

lsp-volar - Language support for Vue3