You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# this is an example configuration file for ra-multiplex## all configuration options here are set to their default value they'll have if# they're not present in the file or if the config file is missing completely.# time in seconds after which a rust-analyzer server instance with no clients# connected will get killed to save system memory.## you can set this option to `false` for infinite timeoutinstance_timeout = 300# after 5 minutes# time in seconds how long to wait between the gc task checks for disconnected# clients and possibly starts a timeout task. the value must be at least 1.gc_interval = 10# every 10 seconds# ip address and port on which ra-multiplex-server listens# or unix socket path on *nix operating systems## the default "127.0.0.1" only allows connections from localhost which is# preferred since the protocol doesn't worry about security.# ra-multiplex server expects the filesystem structure and contents to be the# same on its machine as on ra-multiplex's machine. if you want to run the# server on a different computer it's theoretically possible but at least for# now you're on your own.## ports below 1024 will typically require root privileges and should be# avoided, the default was picked at random, this only needs to change if# another application happens to collide with ra-multiplex.listen = ["127.0.0.1", 27631] # localhost & some random unprivileged port# listen = "/var/run/ra-mux/ra-mux.sock" # unix socket# ip address and port to which ra-multiplex will connect to# or unix socket path on *nix operating systems## this should usually just match the value of `listen`connect = ["127.0.0.1", 27631] # same as `listen`# connect = "/var/run/ra-mux/ra-mux.sock" # same as `listen`# default log filters## RUST_LOG env variable overrides this option, both use the same syntax which# is documented in the `env_logger` documentation here:# <https://docs.rs/env_logger/0.9.0/env_logger/index.html#enabling-logging>log_filters = "info"# environemnt variable names passed from `ra-multiplex client` to the server## by default no variables are passed. and all servers are spawned in# the same environment as the `ra-multiplex server` is. when a name like# "LD_LIBRARY_PATH" is specifified the proxy reads the variable value from its# environment and passes it to the server which then passes it on to the server# executable.## if "PATH" is specified here then the PATH from the client environment is# going to be used for looking up a relative `--server-path`.pass_environment = []
The text was updated successfully, but these errors were encountered:
Hello, when using
ra-multiplex
withrustaceanvim
it spawnN
rust-analyzers
for each project.rs
file opened.Is this the expected behaviour?
ps --long | where name == ra-multiplex
ps --long | where name == rust-analyzer
rustaceanvim
config:ra-multiplex
config:The text was updated successfully, but these errors were encountered: