Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Harry Felton
    @hbomb79_gitlab
    No config files found huh... weird because there is DEFINITELY one present, and it checked that location
    Info 12 [18:7:15.857] ConfigFilePresence:: Current Watches: :: File: /home/HarryF/ImportProcessor/tsconfig.json Currently impacted open files: RootsOfInferredProjects: OtherOpenFiles: /home/HarryF/ImportProcessor/src/classes/Application.ts Status: File added to open files impacted by this config file
    On my Mac machine, the log looks pretty similar except instead of No config files found, it actually comes back with the correct path and all is well
    Jesse Atkinson
    @jsatk
    Sometimes the gutter for ALE continues to show errors however there are no errors and when I move my cursor to those lines or run ALELint there are no errors reported. Is there a way to 1. Prevent this or 2. Force the gutter to re-draw?
    w0rp
    @w0rp
    If that's a bug, report it on GitHub.
    w0rp
    @w0rp
    Now ALE is under a GitHub Organization so more people can contribute by managing issues. :+1:
    w0rp
    @w0rp
    I still haven't fixed my home server and I'm too busy/lazy to set up IRC on my laptop. I'll sort it out eventually.
    Christian Maniewski
    @chmanie
    Is it somehow possible to debug the commands that ale is running somehow? I have a problem where just in a particular project the fixing doesn't work for typescript while the linting itself works
    Christian Maniewski
    @chmanie
    Never mind. I had a faulty version of eslint installed
    A Man Of Science
    @jad-b
    Hi :wave: - I've been struggling to use a linter executable that's "wrapped" by another executable. Doing so allows the executable to be re-used across multiple projects. In my case, the linter is "hlint", the wrapper is stack. stack exec hlint [file] works from the CLI, but setting let b:ale_haskell_hlint_executable = "'stack exec -- hlint'" errors with: (executable check - failure) 'stack exec hlint'. Any ideas about how to do this?
    w0rp
    @w0rp
    You could try setting the _executable to 'stack', and the _options to 'exec -- htlint'. I can't guarantee that will work forever, but it will probably work for now.
    @chmanie For future reference, you can see what ALE is running by using :ALEInfo.
    A Man Of Science
    @jad-b
    @w0rp Thanks for the suggestion - I managed to get it to work, but it took one more step that I don't quite understand. By :ALEInfo, that actually ran 'stack exec hlint -- exec hlint'. Setting hlint_executable = 'stack' and hlint_options = ''actually ran (executable check - success) stack (finished - exit code 1) ['/bin/bash', '-c', '''stack'' exec ''hlint'' -- --color=never --json - < ''/tmp/nvimNImjwE/1/APISpec.hs'''], so it works, but I don't know why...Anyway, maybe you'll find that curious.
    w0rp
    @w0rp
    I remember now. That's because someone already added support for setting the executable to 'stack'. If the executable path ends in 'stack' for most of the Haskell linters, if not all of them, it will execute the linters via stack. You can see this in autoload/ale/handlers/hlint.vim.
    A Man Of Science
    @jad-b
    What a visionary. Thanks for the help!
    Christian Rapp
    @crapp
    Hi, currently ale overwrites the signs in the signcolumn of the ones youcompleteme provides. Can I somehow control this? I found something about a priority that can be used but unsure if ale supports this
    w0rp
    @w0rp
    Look at recent pull requests. There's an open pull request for that.
    Bashar Harfoush
    @basharh
    Hello, I'm not sure if this is an issue with ALE or eslint6. eslint@6 now looks for plugins using the current working directly and not the locations of the eslint.js script. I believe they did this to support loading local modules even when using a global eslint.js. The downside is that if you run eslint6 from any other location outside the project(which means PWD is not a sub-directory of the project), then eslint6 fails to find the required plugins. ALE fails in this case because it relies on absolute paths to run eslint6. For example running something like this fails which what ALE runs: /Users/bashar/work/projects/adl/adl-backend/node_modules/eslint/bin/eslint.js /Users/bashar/work/projects/adl/adl-backend/src/app.ts if PWD is /Users/bashar/. Is there a way we can set the PWD explicitly when running eslin6?
    Bashar Harfoush
    @basharh
    I reached out about this issue in https://gitter.im/eslint/eslint. It seems there might be a workaround but a better solution might be to set CWD in the job options in ALE to the buffer or linter directory.
    cxgslegend
    @cxgslegend
    Hey guys, I am trying to get rls to work with my setup. I have never used ale before, so forgive me if I am doing something obviously wrong. But nothing is happening visually when I put an obvious error in my rust file. When I run ALEInfo it gives me Available Linters: ['cargo', 'rls', 'rustc'] Enabled Linters: ['rls']. Also it gives me (executable check - success) rls (started) ['/bin/zsh', '-c', '''rls''']. And I can use ale-go-to-definition. So am I missing something? Shouldn't it be putting errors in the gutter?
    cxgslegend
    @cxgslegend
    Okay, so I figured out the answer to my last question. But I have a new one. I really don't like the autocomplete preview window that opens. I have info in dropdown. So how can I get rid of the preview window? Thanks
    w0rp
    @w0rp
    @cxgslegend You can disable the preview window by changing your completion options in Vim.
    See :help completeopt. If you don't have preview in your setting there, ALE won't show the preview window.
    cxgslegend
    @cxgslegend
    Thank you @w0rp. But if I turn off preview in the completeopt, then ale_detail wont work anymore. It would be nice to be able to have a keybinding for ale_detail, so I can use it when I need to, but still get ride of the live preview while typing.
    w0rp
    @w0rp
    The preview window for completion is separate from the preview window usage for :ALEDetail, so that shouldn't be an issue.
    cxgslegend
    @cxgslegend
    You are right, I was doing something dumb again. Thanks @w0rp!
    physkets
    @physkets
    Hi! According to the following gcc doc:
    https://gcc.gnu.org/onlinedocs/gfortran/Preprocessing-Options.html
    The options should include a '-cpp' preprocessor flag for certain file extensions.
    Is there any way to add that?
    Jesse Atkinson
    @jsatk
    Hm. I'm having trouble getting Typescript working with Ale out of the box. I looked at the docs but didn't see anything diving into it. The main features I want to use are :ALEHover and :ALEGoToDefinition. Any help/tips getting Typescript support in ALE?
    Christian Maniewski
    @chmanie

    @jsatk hmm, it does work for me. I have an ftplugin file set up for typescript:

    let b:ale_fixers = {'typescript': ['prettier', 'eslint']}

    Also I think TS should be installed in your project and you will need a tsconfig.json

    Oh wait you don't need the fixing part, then you shouldn't need the ftplugin file either
    Jesse Atkinson
    @jsatk
    Hm. Will try on a diff project.
    Ryan Delaney
    @rpdelaney
    Two questions: (1) Any way to get ale to give me some kind of error when it's not running any linters because I screwed up something in my config? (2) What did I screw up to explain why it's not running any linters?
    Seth Bromberger
    @sbromberger
    anyone using vim + ale + gopls ?
    I'm running into some weird completion issues.
    Ryan Delaney
    @rpdelaney
    Using shellcheck with ale I commonly get "The mentioned syntax error was in this expression" but the rest of the error is missing. ALEDetail does not improve the information I have access to, so I have to background vim and run it manually to find out the rest. Any suggestions?
    Ryan Delaney
    @rpdelaney
    I will make a github issue for this one
    Ryan Delaney
    @rpdelaney
    I see what's going on. I have to move my cursor deeper into the line to get the messages
    I suppose that makes this a feature and not a bug