Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
    John Meow
    I get this if I have "clangtidy" in my g:ale_fixers.cpp
    How to fix it?
    why do I get this error
    ale#fix#ApplyFixes: line 18: The file was changed before fixing finished
    Konstantin Baierer
    Hi, is it possible to restrict linting warning level to show only real errors? I have a large codebase with lots of stylistic issues and I'm only interested in errors like missing imports, undefined variables etc.
    Konstantin Baierer
    I just realized ALENext, ALEPrevious etc. accept a -error argument that does just what I want.
    Kevin Clark
    @w0rp @neersighted @RyanSquared Hi folks - just wanted to give a heads up on dense-analysis/ale#3471 In particular, I thought what to do about the linters that have been failing name checks silently needed discussion. Please let me know if more information is needed or if there's anything I can do to help move the change along.
    I see a lot of stale and long lived PRs without review - if help is needed triaging any of that, i'm happy to chip in where I can.
    Laurent G
    Hi all
    I have a beginner question. I want to add some option to a linter command (ansible-lint). How can I do that?
    Playing with g:ale_ansible_ansible_lint_executable is the right way to do ?
    Laurent G
    hum, … let g:ale_ansible_ansible_lint_executable = 'ansible-lint -R -r ./my_rules' doesn't seem to work
    Laurent G
    Ok I tried putting my custom rules into the .ansible-lint config file. It's well taken into account if I run ansible-lint my_playbook.yml but not in vim with ALE. :-/
    Maybe something in my python rules that was ok with ansible-lint but not with ALE?
    Laurent G
    I think my issue is that my path to my custom lint rules is relative. I don't know from where is launch the linters by ALE
    but I assume it's not from my $PATH
    Laurent G
    If any one has any clue, I'm ready to hear!
    @xenlo ALE typically launches linters in a place called the "project root", which is normally identified by either a litner-specific file such as an eslintrc, or a VCS identifier such as a .git directory.
    ... however, I don't think ansible-lint has a project root option, so it would run in the PWD of the spawning process, I believe.
    (in this case, spawning process would be vim)
    Leonhard Saam
    Hello everyone,
    I am trying to switch from VSCode to Vim and was confused about the role of ALE in linting. If I understand everything correctly, ALE has a basic C++ linter. I'm not sure now what ALE actually does. Does it act as a middleman between the linter and Vim or what does it do?
    @The-personified-devil yes - ALE is a layer that takes the output from linters that typically run on the command line (or act as a language server!) and gives you editor functionality based on that.
    ALE itself is not a linter, ALE is the tool that uses linters.
    Kevin Watters
    I have my compiler sending errors to a file local to my project, like .compiler_errors
    what would be the easiest way to define an errorformat and read that file for errors? is there an existing linter i can look to that would have an example of reading from a file?
    @kevinw there's a pretty loosely defined format used by luacheck, teal, and other languages.
    test.tl:5:16: in local declaration: x: got string "hello", expected nil
    test.tl:7:6: argument 1: got <unknown type>, expected string
    So it's like, <filename>:<line>:<column>: <error message>
    Jeremy Zagorski
    Does anyone have experience using Docker Desktop + Rust with Ale? I was reading the ale-lint-other-machines help documentation to create a similar setup on a windows machine, but could not get it to work using the rust:latest image. The executable check fails. I'd be happy to provide my setup if anyone has a similar setup working (not necessarily rust)
    Alessandro Re

    Hello! I started using ALE with rust and python, and I like the experience so far! I have a problem with rust, though that I don't understand: when I create a library project, e.g. using cargo new --lib something, I will get an annoying warning for the code saying that the main is missing: 'main' function not found in crate 'something': consider adding a 'main' function at the crate level.

    How can I investigate/fix this?

    @akiross can you provide me with the output of :ALEInfo ? In general, I want to make sure that it's not rustc, as I don't think rustc actually cares whether it's a library or not.
    Alessandro Re
    Oh I didn't know about :ALEInfo, I'll take a look
    Alessandro Re
    Yeah, it was rustc. I was also missing rust-analyzer: (executable check - failure) rust-analyzer. Now I got a success there, but the message regarding main was from rustc. I removed it from my linters and now there is not that error anymore and things seems better. Thanks!
    Jonathan Birk
    Hey, been using ALE for a week now and it works great. Now i try to use it to fix stuff too but :ALEFix won't do anything. :ALEInfo is at https://pastebin.com/hH8tEak3 . Am I doing something stupid?
    Abid K
    Hi, some fixer is auto fixing my python code and messing it up.. I have setup flake8 for linting, but nothing for fixing. How would I get to know what makes the fixes?
    No fixers are enabled by default unless configured. If you didn't set a setting to do it, it probably means you installed some plugin that's setting a variable for you, that you don't know about. I don't recommend any plugins ever configure any fixers by default.
    I don't read the Gitter so much. People might find this interesting: https://github.com/dense-analysis/ale/discussions You can post threads in there now, and get answers for Q&A style posts like Stack Overflow.
    hi there! Is it somehow possible to either make ALEHover to print the text in popup/floating-window (and not just "echo" it), or, maybe, just get it's text to the variable (and prevent it from being echoed)?
    1 reply
    and, yes, I've tried to set g:ale_hover_to_floating_preview, g:ale_hover_to_preview and g:ale_floating_preview to 1, but hover text is still being echoed :-/
    // oh, I forgot to mebtion, that I'm talking about NeoVim-0.5 (and running with TUI)
    Federico Simonetta
    Hello, someone can help me with this issue? dense-analysis/ale#3695
    Kevin Morris
    Hello. I'm having a quite bizzare issue with completion: This extra "floating window" pops up when completion occurs, https://i.postimg.cc/zG14XT99/ale.png. I can't exactly capture it easily with a screen shot, but the regular old completion dialog does pop up and allow me to select. It leaves me afterward at this window floating, which, in order to remove, I must
    click it with my mouse to get focus (I guess?) and run :q.
    I'm using vim-lsp, vim-lsp-settings, vim-ale, ale and pyls backend language server
    Oh, I'm using nvim.
    latest master on all of that, except for pyls.
    The smaller window that pops up and goes away contains the content you see in that picture, just in a smaller window and fixed around my cursor.
    Kevin Morris
    Welp, it was just a repo sync issue or something. Removed everything, reinstalled, all fine.