4 ms·

Flymake is my biggest gripe with eglot. Sadly you cant really switch it out with flycheck

• tptacek 4y ago
  I thought this would annoy me, since I had a custom flycheck setup for years and years prior to eglot, but I haven't noticed any differences in my workflow; it just works.
  • morelisp 4y ago
    Was `flycheck-list-errors` not part of your workflow, or do you have a decent replacement for it? Its lack is my one gripe with flymake.
    • mickeyp 4y ago
      Have you tried `M-x flymake-show-project-diagnostics'?
      • morelisp 4y ago
        Yes; as far as I can tell it runs afoul of unresolvable project.el incompatibilities unless you're using at least Emacs 28.
        • BaculumMeumEst 4y ago
          It seems odd to complain about an issue that doesn’t exist in the latest stable version.
          • josteink 4y ago
            Some people run Emacs from their local system package-managers instead of building from source. They will be stuck on older versions and experience those problems as current problems.
          • morelisp 4y ago
            It's been an issue since before it was the latest stable version, and if the packages needed that version they should be declaring dependencies on it. And project.el is still today marked experimental, so this will probably happen again. Version management in Emacs is hard but a) lots of the community runs Emacs versions much older than 1y old and at least few years of compatibility is (used to be?) a strong cultural norm, b) it's common to offer fallbacks to e.g. `locate-dominating-file` or similar primitive cases especially when using relatively new features, c) I don't think project.el is very good in general.