The goal of lsp-bridge is to implement the fastest LSP client in the Emacs ecosystem.
Using Python multithreading techniques, lsp-bridge builds a high-speed cache between Emacs and the LSP server, ensuring that Emacs never gets stuck while providing a smooth and seamless code completion experience.
EmacsConf 2022 talk page |
---|
- Install Emacs 28 or higher version
- Install Python dependencies: epc, orjson, sexpdata, six, paramiko, please choose one of the following methods to install Python dependencies
- PyPy (On Linux, we strongly recommend using PyPy instead of CPython for a 5x performance boost):
pypy3 -m pip install epc sexpdata six paramiko
- CPython: (Windows and MacOS users please use CPython)
pip3 install epc orjson sexpdata six paramiko
(orjson is optional, orjson is based on Rust, providing faster JSON parsing performance)
- Install Elisp dependencies:
- Download this repository using git clone, and replace the load-path path in the configuration below.
- Add the following code to your configuration file ~/.emacs:
(add-to-list 'load-path "<path-to-lsp-bridge>")
(require 'yasnippet)
(yas-global-mode 1)
(require 'lsp-bridge)
(global-lsp-bridge-mode)
Please note that:
- When using lsp-bridge, please first disable other completion plugins such as lsp-mode, eglot, company, corfu, etc. Lsp-bridge provides a complete solution from completion backend, frontend to multi-backend fusion.
- When the completion menu pops up,
acm-mode
will be automatically enabled, and when the completion menu disappears,acm-mode
will be automatically disabled. Please do not manually addacm-mode
to any mode-hook or manually executeacm-mode
.
Lsp-bridge works out of the box. After installing the corresponding LSP server and mode plugin for the language, you can start coding directly without any additional settings.
It should be noted that lsp-bridge has three scanning modes:
- When the
.git
directory is detected (determined by the commandgit rev-parse --is-inside-work-tree
), lsp-bridge will scan the entire directory to provide completion. - When the
.git
directory is not detected, lsp-bridge only provides single-file completion for the opened file. - Custom
lsp-bridge-get-project-path-by-filepath
function, where the input parameter is the path string of the opened file and the output parameter is the project directory path. Lsp-bridge will provide completion based on the output directory path.
lsp-bridge
can also provide code syntax completion for files on a remote server, similar to VSCode. Providing remote code completion is very useful when dealing with large and complex software that requires high resource demands or has complex environment configuration. The following are the steps to configure remote code completion:
- Install
lsp-bridge
and the corresponding LSP server on the remote server. - Start the lsp-bridge service:
pypy3 lsp-bridge/lsp_bridge.py
(If you are using CPython, please usepython3 lsp-bridge/lsp_bridge.py
) - Use the command
lsp-bridge-open-remote-file
to open the remote file and enter the username, server IP, ssh port (default: 22), and file path, such asuser@ip:[ssh_port]/path/file
.
Once the remote file is opened, lsp-bridge
will automatically display the code completion menu. The remote completion principle of lsp-bridge
is as follows:
- Login to the remote server with SSH authentication and access and edit the remote file.
- When editing the remote file locally, incremental diff sequences are sent to the
lsp-bridge
server in real-time. The server will rebuild the latest content of the file based on the incremental diff sequence and call the LSP server to complete the syntax calculation. - After calculating the LSP completion menu items,
lsp-bridge
will send the completion data to the local computer and render the completion menu.
If the completion menu does not appear, log in to the remote server and check the terminal output of lsp_bridge.py
. Generally, incomplete installation of the service-side LSP server is the cause.
lsp-bridge first looks for the content of the first *.pub file in the ~/.ssh
directory as the public key credential for logging into the remote server. If public key login fails, the user will be prompted to enter the login password. lsp-bridge does not store the server login password in a file. To avoid repeatedly entering the password, it is recommended that you use the public key method to log in to the remote server.
Key | Command | Description |
---|---|---|
Alt + n | acm-select-next | Select next candidate |
Down | acm-select-next | Select next candidate |
Alt + p | acm-select-prev | Select previous candidate |
Up | acm-select-prev | Select previous candidate |
Alt + , | acm-select-last | Select last candidate |
Alt + . | acm-select-first | Select first candidate |
Ctrl + v | acm-select-next-page | Select next page candidate |
Alt + v | acm-select-prev-page | Select previous page candidate |
Ctrl + m | acm-complete | Complete completion |
Return | acm-complete | Complete completion |
Tab | acm-complete | Complete completion |
Alt + h | acm-complete | Complete completion |
Alt + H | acm-insert-common | Insert common part of candidates |
Alt + u | acm-filter | Perform secondary filtering on candidate words, improving the selection efficiency of candidate words |
Alt + d | acm-doc-toggle | Enable or disable candidate documentation |
Alt + j | acm-doc-scroll-up | Scroll up candidate documentation |
Alt + k | acm-doc-scroll-down | Scroll down candidate documentation |
Alt + l | acm-hide | Hide completion menu |
Ctrl + g | acm-hide | Hide completion menu |
Alt + Number | acm-complete-quick-access | Selecting candidate quickly, you need enable acm-enable-quick-access first |
lsp-bridge-find-def
: jump to the definitionlsp-bridge-find-def-other-window
: jump to the definition in other-windowlsp-bridge-find-def-return
: return to the location before callinglsp-bridge-find-def
lsp-bridge-find-type-def
: Jump to the position of type definition.lsp-bridge-find-type-def-other-window
: Jump to the position of type definition in another window.lsp-bridge-find-impl
: jump to the implementationlsp-bridge-find-impl-other-window
: jump to the implementation in other-windowlsp-bridge-find-references
: traverse across code references (forked from color-rg.el)lsp-bridge-popup-documentation
: lookup documentation of symbol under the cursorlsp-bridge-popup-documentation-scroll-up
: scroll up popup document.lsp-bridge-popup-documentation-scroll-down
: scroll down popup document.lsp-bridge-rename
: rename symbol under the cursorlsp-bridge-diagnostic-jump-next
: Jump to the next diagnostic positionlsp-bridge-diagnostic-jump-prev
: Jump to the previous diagnostic positionlsp-bridge-diagnostic-list
: List all diagnostic informationlsp-bridge-diagnostic-copy
: Copy the current diagnostic information to the clipboardlsp-bridge-diagnostic-ignore
: Insert comment to ignore the current diagnosislsp-bridge-code-action
: Popup code action menu, you can pass specialactin-kind
to fix,action-kind
can use one of "quickfix", "refactor", "refactor.extract", "refactor.inline", "refactor.rewrite", "source", "source.organizeImports", "source.fixAll"lsp-bridge-workspace-list-symbols
: List all symbols in workspace and jump to the symbol definitionlsp-bridge-signature-help-fetch
: show signature help in minibuffer manually (move cursor to parameters area will show signature help automatically)lsp-bridge-popup-complete-menu
: Manually popup the completion menu, you only need this command when turn on optionlsp-bride-complete-manually
lsp-bridge-restart-process
: restart lsp-bridge process (only used for development)lsp-bridge-toggle-sdcv-helper
: Switch dictionary completion assistant
lsp-bridge-c-lsp-server
: C language server, you can chooseclangd
orccls
lsp-bridge-elixir-lsp-server
: Elixir language server, you can chooseelixirLS
(default) orlexical
lsp-bridge-python-lsp-server
: Python language server, you can choosepyright
,jedi
,python-ms
,pylsp
,ruff
lsp-bridge-php-lsp-server
: PHP language server, you can chooseintelephense
orphpactor
lsp-bridge-tex-lsp-server
: LaTeX language server, you can choosetexlab
ordigestif
lsp-bridge-csharp-lsp-server
: C# language server, you can chooseomnisharp-mono
oromnisharp-dotnet
, note that you need to give execute permissions to the OmniSharp filelsp-bridge-python-multi-lsp-server
: Python multi-language servers, you can choosepyright_ruff
,jedi_ruff
,python-ms_ruff
,pylsp_ruff
lsp-bridge-python-command
: The path of the python command, if you useconda
, you may customize this option. Windows platform usingpython.exe
rather thanpython3
, if lsp-bridge can't work, try set topython3
lsp-bridge-complete-manually
: Only popup completion menu when user calllsp-bridge-popup-complete-menu
command, default is nillsp-bridge-get-workspace-folder
: You need to put multiple project in aworkspace
directory in Java before you can jump function defintion normally. This function can be customized, the function input is the project path and returns theworkspace
directory correspondinglsp-bridge-org-babel-lang-list
: list of language to support org-mode code block completion, nil enable all languages, default is nillsp-bridge-enable-diagnostics
: code diagnostic, enable by defaultlsp-bridge-enable-hover-diagnostic
: show diagnostic tooltip when cursor hover diagnostic place, disable by defaultlsp-bridge-enable-search-words
: index the word of the file, enable by defaultlsp-bridge-enable-auto-format-code
: automatic format code, disable by defaultlsp-bridge-enable-signature-help
: show function parameter in minibufer, enable by defaultlsp-bridge-enable-log
: enable LSP message log, disable by default, only enable this option for development purposes, usually do not turn on this option to avoid affecting performancelsp-bridge-enable-debug
: enable program debugging, disable by defaultlsp-bridge-disable-backup
: forbidden version manage of emacs, enable by defaultlsp-bridge-code-action-enable-popup-menu
: enable code action posframe popup menu, enable by defaultlsp-bridge-diagnostic-fetch-idle
: diagnostic delay, start pulling diagnostic information 0.5 second after stopping typinglsp-bridge-signature-show-function
: The function used for displaying signature info, default show message in minibuffer, setlsp-bridge-signature-posframe
to show signature info in framelsp-bridge-completion-popup-predicates
: the predicate function for completion menu, completion menu popup after all the functions passlsp-bridge-completion-stop-commands
: completion menu will not popup if these commands are executedlsp-bridge-completion-hide-characters
: The default value is'(":" ";" "(" ")" "[" "]" "{" "}" ", " "\"")
, the completion menu does not pop up when the cursor is behind these characters. You can customize this option to remove this restriction, or call thelsp-bridge-popup-complete-menu
command to force the menu to pop uplsp-bridge-user-langserver-dir
: the dir where user place langserver configuration file, if the configuration file name in the dir is the same as that in lsp-bridge/langserver , lsp-bridge will use the configuration file in this dirlsp-bridge-user-multiserver-dir
: the dir where user place multiserver configuration file, if the configuration file name in the dir is the same as that in lsp-bridge/multiserver , lsp-bridge will use the configuration file in this dirlsp-bridge-symbols-enable-which-func
: Using lsp backend forwhich-func
, disable by defaultlsp-bridge-enable-org-babel
: Using lsp backend for org babel, disable by defaultacm-frame-background-dark-color
: Menu background color in dark themeacm-frame-background-light-color
: Menu background color in light themeacm-markdown-render-font-height
: The font height of function documentation, default is 130acm-enable-doc
: Whether the complete menu display the help documentacm-enable-doc-markdown-render
: Richly render Markdown for completion popups, you can choose'async
,t
ornil
. When set to'async
, styles are applied asynchronously, chooset
, styles are applied synchronously and will slow down the completion speed, default isasync
acm-enable-icon
: Whether the completion menu displays icons (Many macOS users have reported that emacs-plus28 cannot display icons properly, showing colored squares instead. There are two ways to solve this: install Emacs Mac Port or add the--with-rsvg
option to the brew command when compiling Emacs yourself)acm-enable-tabnine
: Enable tabnine support, enable by default, when enable need executelsp-bridge-install-tabnine
command to install TabNine, and it can be used. TabNine will consume huge CPUs, causing your entire computer to be slow. If the computer performance is not good, it is not recommended to enable this optionacm-enable-codeium
: Enable Codeium support, when enable need executelsp-bridge-install-update-codeium
command to install Codeium, then executelsp-bridge-codeium-auth
command to get auth token and executelsp-bridge-codeium-input-auth-token
command to get API Key, and it can be used.acm-enable-search-file-words
: Whether the complete menu display the word of the file, enable by defaultacm-enable-quick-access
: Whether the index is displayed behind the icon, you can quickly select the candidate through Alt + Number, disable by defaultacm-enable-yas
: yasnippet completion, enable by defaultacm-enable-citre
: Integration with citre(ctags). Enable this to add citre (ctags) backend (disabled by default)acm-doc-frame-max-lines
: Max line number of help documentation, default is 20acm-candidate-match-function
: The complete menu matching algorithm, the algorithm prefix of orderless-* needs to be installed additional orderlessacm-completion-backend-merge-order
: Display order of completion backends. By default, multiple completion backends are merged in the order of LSP, Templates, and TabNine, and then the remaining templates and LSP completion options are displayed. You can adjust the order of completion back-end merging according to your needsacm-backend-lsp-candidate-min-length
: The minimum characters to trigger lsp completion, default is 0acm-backend-elisp-candidate-min-length
: The minimum characters to trigger elisp completion, default is 0acm-backend-yas-candidate-min-length
: The minimum characters to trigger yasnippet completion, default is 0acm-backend-search-file-words-candidate-min-length
: The minimum characters to trigger search file words completion, default is 0acm-backend-codeium-candidate-min-length
: The minimum characters to trigger codeium completion, default is 0acm-backend-lsp-enable-auto-import
: automatic insert import code, enable by defaultacm-backend-lsp-candidate-max-length
: Maximum length of LSP candidate, some language, such as Java, argument list is very long, you can increase the value of this option to see clear argument listacm-backend-yas-candidates-number
: yasnippet display number, 2 by defaultacm-backend-citre-keyword-complete
: Completion is performed according to the keywords of each mode defined byacm-backend-citre-keywords-alist
, which takes effect only after citre is enabled.acm-backend-search-sdcv-words-dictionary
: StarDict dictionary for word completion, default iskdic-ec-11w
, you can replace it with StarDict dictionary path, example, if you have dictionary/usr/share/stardict/dic/stardict-oxford-gb-formated-2.4.2/oxford-gb-formated.ifo
, you need set this value to/usr/share/stardict/dic/stardict-oxford-gb-formated-2.4.2/oxford-gb-formated
, not include.ifo
extension.
The configuration for the LSP server of each language in lsp-bridge is stored in lsp-bridge/langserver.
In most cases, you can customize the server configuration according to the following priority order:
lsp-bridge-get-single-lang-server-by-project
: A user-defined function that takes project-path and file-path as input parameters and returns the corresponding LSP server string. You can query the names of all LSP servers in the lsp-bridge-single-lang-server-mode-list list. By default, this function returns nil.lsp-bridge-single-lang-server-extension-list
: Returns the server based on the file extension, for example, when opening a *.wxml file, we will use the wxml LSP server for completion.lsp-bridge-single-lang-server-mode-list
: Returns the corresponding server based on Emacs's major-mode.
If you are writing JavaScript code, you may need to customize multiple server configurations:
lsp-bridge-get-multi-lang-server-by-project
: A user-defined function that takes project-path and file-path as input parameters and returns the multiple server configuration names. You can search for them in the subdirectory lsp-bridge/multiserver.lsp-bridge-multi-lang-server-extension-list
: Returns multiple server configuration names based on the file extension. For example, when opening a *.vue file, we will use volar_emmet to simultaneously utilize volar and emmet-ls for completion.lsp-bridge-multi-lang-server-mode-list
: Returns the corresponding multiple server configuration names based on Emacs's major-mode.
For example, we can enable the Deno LSP server for Deno scripts with the following configuration:
(setq lsp-bridge-get-single-lang-server-by-project
(lambda (project-path filepath)
;; If typescript file include deno.land url, then use Deno LSP server.
(save-excursion
(when (string-equal (file-name-extension filepath) "ts")
(dolist (buf (buffer-list))
(when (string-equal (buffer-file-name buf) filepath)
(with-current-buffer buf
(goto-char (point-min))
(when (search-forward-regexp (regexp-quote "from \"https://deno.land") nil t)
(return "deno")))))))))
Copy the configuration files in lsp-bridge/langserver or lsp-bridge/multiserver to lsp-bridge-user-langserver-dir or lsp-bridge-user-multiserver-dir for customization. Lsp-bridge will prioritize reading the configuration files in lsp-bridge-user-langserver-dir or lsp-bridge-user-multiserver-dir.
We can set the value of lsp-bridge-user-langserver-dir or lsp-bridge-user-multiserver-dir before starting lsp-bridge-mode to achieve different project-specific configuration files.
(defun enable-lsp-bridge()
(when-let* ((project (project-current))
(project-root (nth 2 project)))
(setq-local lsp-bridge-user-langserver-dir project-root
lsp-bridge-user-multiserver-dir project-root))
(lsp-bridge-mode))
- Create a configuration file in the lsp-bridge/langserver directory. For example,
pyright.json
is the configuration file for the pyright server (usepyright_windows.json
for Windows andpyright_darwin.json
for macOS). - Add
(mode . server_name)
to thelsp-bridge-single-lang-server-mode-list
option in the lsp-bridge.el file, for example,(python-mode . "pyright")
. - Add a new mode-hook to the
lsp-bridge-default-mode-hooks
option in the lsp-bridge.el file. - Add a new indentation variable to the
lsp-bridge-formatting-indent-alist
option in the lsp-bridge.el file.
We welcome patches to help us support more LSP servers. Thank you for your help!
You need to install the LSP server corresponding to each programming language, then lsp-bridge can provide code completion service.
LSP Server | Language | Note |
---|---|---|
clangd | C, C++, Object-C | need you config compile_commands.json first |
ccls | C, C++, Object-C | lsp-bridge-c-lsp-server set to ccls , you need to configure compile_commands.json first |
pyright | Python | lsp-bridge-python-lsp-server set to pyright , pyright-background-analysis is faster sometimes, but it can't response diagnostic informations |
jedi | Python | lsp-bridge-python-lsp-server set to jedi |
python-ms | Python | Legacy language server for Python2 |
pylsp | Python | lsp-bridge-python-lsp-server set to pylsp |
ruff | Python | pip install ruff-lsp , lsp-bridge-python-lsp-server is set to ruff , which only has the function of linter. If you need to complete the functions, install other Python language servers, and set the lsp-bridge-python-multi-lsp-server to [LSP NAME]_ruff |
solargraph | Ruby | |
rust-analyzer | Rust | |
elixirLS | Elixir | Please ensure that the elixir-ls release directory is in your system PATH at first |
lexical | Elixir | Kindly make sure that the lexical release directory is included in your system's PATH and that lexical has been compiled using the same version of Elixir/Erlang as your project. |
gopls | Go | Make sure install go-mode and gopls in PATH, please do ln -s ~/go/bin/gopls ~/.local/bin , and do go mod init first |
hls | Haskell | |
dart-analysis-server | Dart | |
metals | Scala | |
typescript | Typescript, Javascript | |
ocamllsp | Ocaml | |
erlang-ls | Erlang | |
texlab | Latex | |
eclipse.jdt.ls | Java | Please ensure that org.eclipse.jdt.ls.product/target/repository/bin is in your system PATH at first |
clojure-lsp | Clojure | If you use homebrew , please ensure install clojure-lsp/brew/clojure-lsp-native clojure-lsp-native |
bash-language-server | Bash | |
volar | Vue | npm install -g typescript @volar/vue-language-server |
sumneko | Lua | Please ensure bin under sumneko installation is in your system PATH at first |
wxml-language-server | Wxml | |
vscode-html-language-server | HTML | npm i -g vscode-langservers-extracted |
vscode-css-language-server | CSS | npm i -g vscode-langservers-extracted |
vscode-eslint-language-server | JavaScript | npm i -g vscode-langservers-extracted |
vscode-json-language-server | JSON | npm i -g vscode-langservers-extracted |
elm-language-server | Elm | |
intelephense | PHP | |
Phpactor | PHP | lsp-brige-php-lsp-server set to phpactor |
yaml-language-server | Yaml | npm install -g yaml-language-server |
zls | Zig | Execute zls config to generate configuration for zls. see Configuration Options |
groovy-language-server | Groovy | Create a script "groovy-language-server" in PATH, with $JAVA_HOME/bin/java -jar <path>/groovy-language-server-all.jar |
docker-language-server | Dockerfiles | |
serve-d | D | serve-d does not support single file mode, please init .git repository under project root at first or custom lsp-bridge-get-project-path-by-filepath function |
fortls | Fortran | |
emmet-ls | HTML, JavaScript, CSS, SASS, SCSS, LESS | |
rnix-lsp | Nix | |
texlab | Latex | lsp-bridge-tex-lsp-server set to texlab |
digestif | Latex | lsp-bridge-tex-lsp-server set to digestif |
rlanguageserver | R | |
graphql-lsp | GraphQL | |
cmake-language-server | Cmake | pip install cmake-language-server |
ds-pinyin | Org-mode | cargo install ds-pinyin-lsp , download dict.db3 of ds-pinyin, and save to ~/.emacs.d/ds-pinyin/ directory, then turn on option lsp-bridge-use-ds-pinyin-in-org-mode |
Wen | Org-mode | pip install pygls pypinyin , then turn on option lsp-bridge-use-wenls-in-org-mode |
sourcekit-lsp | Swift | The SourceKit-LSP server is included with the Swift toolchain. |
omnisharp-mono | C# | OmniSharp is a .NET development platform based on Roslyn workspaces. use M-x lsp-bridge-install-omnisharp to install it. lsp-bridge-csharp-lsp-server set to omnisharp-mono |
omnisharp-dotnet | C# | OmniSharp is a .NET development platform based on Roslyn workspaces. use M-x lsp-bridge-install-omnisharp to install it. lsp-bridge-csharp-lsp-server set to omnisharp-dotnet (6.0) |
deno | Deno | Deno runtime use TypeScript as source code, you need customize option lsp-bridge-get-single-lang-server-by-project that return result "deno" when project-path match Deno project. |
ansible-language-server | Ansible | Ansible uses YAML as source code, you'll need to customize lsp-bridge-get-single-lang-server-by-project to return "ansible-language-server". |
astro | Astro | npm i -g @astrojs/language-server |
qmlls | QML | The qmlls binary should be part of the normal Qt packages since Qt 6.3.0 Ensure that the directory of qmlls binary file is in PATH |
kotlin-language-server | Kotlin | |
vhdl-tool | VHDL | |
julials | Julia | |
typst-lsp | Typst | |
verible | Verilog | |
move-analyzer | Move | The move-analyzer is included in the move language repository |
The following is the framework of lsp-bridge:
The following is the directory structure of the lsp-bridge project:
File Name | Purpose |
---|---|
lsp-bridge.el | The Elisp main logic part of lsp-bridge provides custom options and Elisp functions for python sub-processes to call, such as code jumps, renaming, etc. |
lsp-bridge-epc.el | The code that communicates with the lsp-bridge python sub-process, which mainly implements Elisp IPC to interface with Python EPC, implementing data serialization, sending, receiving, and deserialization. |
lsp-bridge-call-hierarchy.el | Displays the code's call order relationship in a pop-up frame. |
lsp-bridge-code-action.el | Code repair related code. |
lsp-bridge-diagnostic.el | Diagnostic information related code. |
lsp-bridge-ref.el | A code reference viewing framework that provides reference viewing, batch renaming, and reference result regular filtering. The core code is forked from color-rg.el. |
lsp-bridge-jdtls.el | Provides third-party library jump functions for the Java Language. |
lsp-bridge-lsp-installer.el | Installs TabNine and Omnisharp. |
lsp-bridge.py | The Python main logic part of lsp-bridge provides event loops, message scheduling, and state management. |
acm/acm.el | An asynchronous completion menu designed specifically for lsp-bridge backend, supporting lsp, elisp, words, TabNine, and other backends. |
core/fileaction.py | Mainly records the status of each file, processes LSP response messages, and calls Emacs Elisp functions. |
core/lspserver.py | The LSP message processing module mainly parses, sends, and receives LSP messages, ensuring that LSP request order conforms to LSP protocol specifications. |
core/remote_file.py | Used to handle remote server file access and synchronization. |
core/utils.py | Some global utility functions that facilitate the calling of various modules. |
core/mergedeep.py | JSON information merge, mainly used to send custom options to LSP servers. |
core/hanlder/ | Implementation of LSP message sending and receiving, where __init__.py is the base class. |
core/tabnine.py | The backend searches and completes with TabNine. |
core/codeium.py | The backend searches and completes with Codeium. |
core/search_file_words.py | Asynchronous search backend for file words. |
core/search_paths.py | Asynchronous search backend for file paths. |
core/search_sdcv_words.py | English word search backend, interchangeable with other language's StarDict dictionaries. |
core/search_tailwindcss_keywords.py | TailwindCSS keyword search backend. |
core/search_list.py | Asynchronous search framework that can be used to write your own asynchronous search backends. |
langserver | Mainly places the configuration of LSP servers, with a json file for each server, defining the server's name, language ID, startup command, and settings options. |
multiserver | Mainly places the configuration of multiple LSP servers. |
resources | English dictionary data, mainly for serving Chinese users. |
Please read below articles first:
Then turn on develop option lsp-bridge-enable-log
and happy hacking! ;)
For some common problems, please read Wiki first.
Please use emacs -q
and load a minimal setup with only lsp-bridge to verify that the bug is reproducible. If emacs -q
works fine, probably something is wrong with your Emacs config.
If the problem still exists, please report it here with *lsp-bridge*
buffer content, it contains many clues that can help us locate the problem faster.
-
If you get a segfault error, please use the following way to collect crash information:
- Install gdb and turn on option
lsp-bridge-enable-debug
- Use the command
lsp-bridge-restart-process
to restart theLSP-BRIDGE
process - Send issue with
*lsp-bridge*
buffer content when next crash
- Install gdb and turn on option
-
If you get other errors, please use the following way to collection information:
- turn on option
lsp-bridge-enable-log
- Use the command
lsp-bridge-restart-process
to restart theLSP-BRIDGE
process - Send issue with
*lsp-bridge*
buffer content
- turn on option