Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Nick Cameron
    @nrc
    aiui, it uses the Atom highlighting, so you could make PRs to both with little effort
    Jesper HÃ¥kansson
    @drager
    My editor thinks otherwise :P
    Nick Cameron
    @nrc
    Is it an old editor? There may be a requirement for a recent version in 0.4.4
    Jesper HÃ¥kansson
    @drager
    That might be it, I'll test to get the latest vscode. Thanks @nrc!
    Taryn
    @Phrohdoh
    When implementing go-to-def was there anything special the vscode extension had to do? My VSCode is continuously doing (unknown) work so never takes the user to the location specified by the server.
    Igor Matuszewski
    @Xanewok
    @Phrohdoh are you using https://www.npmjs.com/package/vscode-languageclient package by any chance?
    if so, it should work out of the box, assuming the server is behaving as per spec
    doing unknown work (specifically having Loading... tooltip on hover) means it didn't get the correct response for the goto-def request
    Taryn
    @Phrohdoh
    Yes I'm using that package. There is no tooltip, just the indeterminate progress bar at the top of the file.
    I'm having issues with trailing newlines so started using print! but am wondering if I need to do ^ too.
    Igor Matuszewski
    @Xanewok
    Maybe to be sure that the output is not buffered?
    and we always flush after a message? Not sure myself
    David Saltares
    @saltares
    Hi, this may be a silly question but just trying the VS code extension for rust: https://marketplace.visualstudio.com/items?itemName=rust-lang.rust and can't get the autocomplete to work, ctrl+space seems to just show text based autocomplete, racer is installed
    Yuji Kanagawa
    @kngwyu
    @saltares
    RLS uses racer via static linking so I think it's racer's problem.
    Could you please let me know the word you're trying to complete?
    Nick Cameron
    @nrc
    We have an ides-and-editors channel on Discord now; invite: http://discord.gg/rust-lang
    Raj2032
    @Raj2032
    Hey guys
    rust-lang-nursery/rls#932
    I am having an issue in installing The extension
    I did install the Rust rls extension
    but then I was prompted to install toolchian and when I clicked yess then I got this error
    Raj2032
    @Raj2032
    Sorry this is the link
    rust-lang-nursery/rls#935
    To the issue
    Jakub Tesinsky
    @gorn
    Is there a reccomended IDE for Rust?
    Lucas Bullen
    @LucasBullen

    Either use the VSCode RLS plugin [1] as because of it's minimal size, any issues with it are most likely with the RLS itself. If you are looking for a complete development experience, you can use the one-click-download Rust IDE based on Eclipse. Download: [2] and The Corrosion Project: [3]. However as it has more built on top of the RLS, there may be more issues, but we are always looking for improvements.

    [1] https://github.com/rust-lang-nursery/rls-vscode
    [2] https://www.eclipse.org/downloads/packages/release/photon/r/eclipse-rust-photon-r-incubation
    [3] https://github.com/eclipse/corrosion

    Nicholas
    @Bujiraso
    @gorn also check out https://areweideyet.com/
    Damir Vandic
    @dvic

    Hi! I have a small question regarding the Visual Code plugin.

    Is the goto definition feature supposed to work also outside the current crate? E.g., when you click on a method from an external crate, you cannot use goto definition from there. However, if I open that external crate folder and make RLS index it (by opening a .rs file), then it works. Is this the way it's supposed to work or is there something wrong with my configuration? Thanks!

    Damir Vandic
    @dvic
    FYI, submitted a github issue with this question: rust-lang-nursery/rls-vscode#391
    Jakub Tesinsky
    @gorn
    Hi, I am not sure if this is the right place to get some helpt with VS Code rust debuging
    I have problem to get the rust debuging working in VS Code
    I am getting:
    warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
    Sasa Cocic-Banjanac
    @sasacocic
    Hi. I'm having issues with RLS for my project. Neither go to definition or find all references is work.
    Pretty much all of the functionality isn't work
    I have rust nightly and have the extension for vscode (I'm using vscode)
    veruma
    @veruma
    Hi, I am using atom as IDE. is there anyway to run/build rust programs from atom. I could not see any button or shortcut
    Naja Melan
    @najamelan
    does anyone use sublime text with lsp and rls?
    Naja Melan
    @najamelan
    ok, nevermind i found the enable rls globally. Now it works!
    Chandrahmuki
    @Chandrahmuki_twitter
    hi guys just a small question trying out rust through coc.nvim seems to work find but i cant get completion on everything it seems i'm using nvim and coc.nvim
    Iulian Barbu
    @iulianbarbu
    Hello, guys. I am using vim 8.0 and I can not figure out why jumpRefeferences from coc.nvim returns References not found for a function symbol used all over the place. Also, when using rename, I get No information for the symbol. Does coc.nvim needs tags to work properly? I want to mention that go to definition or show documentation works properly.
    Kelly Thomas Kline
    @kellytk
    For RLS users, how can rust-lang/rls#1560 be worked around?
    Stephen Waits
    @swaits
    Hey folks. Any tips on debugging why I'm not seeing error squiggles?
    Annis Monadjem
    @Annis-Monadjem

    Hello! I'm trying to figure out how to use coc-rls.
    I have setup cargo, have updated (:CocCommand rls.update) coc-rls latest version @1.1.4, neovim :checkhealth is all ok, but when try to run .rs file i get this nasty message:

    [coc.nvim] Command error: request error nvim_call_function - Vim(let):E15: Invalid expression: 'ps -o state= -o comm= -t '#{pane_tty}'  
     | grep -iqE '^[^TXZ ]+ +(\S+\/)?g?(view|n?vim?x?)(diff)?$''

    CocInfo:

    vim version: NVIM v0.5.0-139-g610755ff6
    node version: v12.16.1
    coc.nvim version: 0.0.75-d5e12d81b2
    term: screen-256color
    platform: linux
    
    [coc.nvim] Setting sysroot to/home/sky/.rustup/toolchains/stable-x86_64-unknown-linux-gnu
    [coc.nvim] running: rustup run stable-x86_64-unknown-linux-gnu rls, at /home/sky/rust_learning/a3_rust-by-example
    
    ## Output channel: prettier
    ## Output channel: snippets

    CocOpenLog (selected printout of Error message):

    2020-03-08T22:33:53.834 ERROR (pid:19851) [commands] - Error: request error nvim_call_function - Vim(let):E15: Invalid expression: 'ps -o state= -o comm= -t '#{pane_tty}'   | grep -iqE '^[^TXZ ]+ +(\S+\/)?g?(view|n?vim?x?)(diff)?$''
        at /home/sky/.config/nvim/plugged/coc.nvim/build/index.js:14243:32
        at NvimTransport.parseMessage (/home/sky/.config/nvim/plugged/coc.nvim/build/index.js:10847:17)
        at DecodeStream.<anonymous> (/home/sky/.config/nvim/plugged/coc.nvim/build/index.js:10817:18)
        at DecodeStream.emit (events.js:311:20)
        at addChunk (_stream_readable.js:294:12)
        at readableAddChunk (_stream_readable.js:275:11)
        at DecodeStream.Readable.push (_stream_readable.js:209:10)
        at DecodeStream.Transform.push (_stream_transform.js:152:32)
        at DecodeBuffer.DecodeStream.decoder.push (/home/sky/.config/nvim/plugged/coc.nvim/build/index.js:13767:12)
        at DecodeBuffer.flush (/home/sky/.config/nvim/plugged/coc.nvim/build/index.js:12757:12)

    Anyone, how to fix the above problem ?

    Albert Cervin
    @abbec
    Hi, I get this all the time trying to use rls from coc.vim:
    {"message":"linking with `cc` failed: signal: 9","code":null,"level":"error","spans":[],"children":[{"message":"\"cc\" \"-m64\" \"-L\" \"/nix/store/s5b2y200x8xaa1wj4ncd3xcvs9nrs8pa-rust-1.44.0-nightly-2020-04-19-dbf8b6bf1/lib/rustlib/x86_64-apple-darwin/lib\" ...
    {"message":"dyld: lazy symbol binding failed: Symbol not found: _LLVMInitializeAMDGPUTargetInfo\n  Referenced from: /nix/store/gp6qcqvyd7zibws6jyqrgh38bnm2vr49-clang-7.1.0/bin/clang\n  Expected in: /nix/store/s5b2y200x8xaa1wj4ncd3xcvs9nrs8pa-rust-1.44.0-nightly-2020-04-19-dbf8b6bf1/lib/libLLVM.dylib\n\ndyld:
    however rls --cli works fine
    Albert Cervin
    @abbec
    Oh, it actually seems to be the setting of DYLD_LIBRARY_PATH that the coc-rls plugin is doing...
    niilz
    @niilz
    I use coc-rls in neovim. When I switch to the nightly-toolchain and open a rust file with nvim, I see a message: "rls is not installed".
    With the stable-toolchain, rls seems to work just fine.
    Is that normal? Or should it be possible to get coc-rls to work on nightly?