#flycheck — Public Fediverse posts

@cks wow - #FlyCheck is whole different interface to python linters etc https://www.flycheck.org/en/latest/languages.html#python for #emacs and a tonne of other languages.

Do you happen to know if they play nice with the local project’s configuration (eg .flake8 file in the parent folder?)

@cks wow - #FlyCheck is whole different interface to python linters etc https://www.flycheck.org/en/latest/languages.html#python for #emacs and a tonne of other languages.

Do you happen to know if they play nice with the local project’s configuration (eg .flake8 file in the parent folder?)

@cks wow - #FlyCheck is whole different interface to python linters etc https://www.flycheck.org/en/latest/languages.html#python for #emacs and a tonne of other languages.

Do you happen to know if they play nice with the local project’s configuration (eg .flake8 file in the parent folder?)

@cks wow - #FlyCheck is whole different interface to python linters etc https://www.flycheck.org/en/latest/languages.html#python for #emacs and a tonne of other languages.

Do you happen to know if they play nice with the local project’s configuration (eg .flake8 file in the parent folder?)

@cks wow - #FlyCheck is whole different interface to python linters etc https://www.flycheck.org/en/latest/languages.html#python for #emacs and a tonne of other languages.

Do you happen to know if they play nice with the local project’s configuration (eg .flake8 file in the parent folder?)

A nice milestone for #Flycheck (notice the number of the closed issues :D )

A nice milestone for #Flycheck (notice the number of the closed issues :D )

A nice milestone for #Flycheck (notice the number of the closed issues :D )

A nice milestone for #Flycheck (notice the number of the closed issues :D )

A nice milestone for #Flycheck (notice the number of the closed issues :D )

I use #WriteGood for prose analysis in #Emacs for #Org_mode files and #markdown. I consider myself a competent writer that mostly appreciates flagging passive sentences (from command line utility that doesn't require an online service).

New team uses #just, and write-good flags that word as a weasel word. Fair enough, but I don't want to see a slew of red lines. So I use #remark to strip words in backtick quotes before write-good analysis.

Connected to #flycheck ftw:
https://howardabrams.com/git/howard/hamacs/src/branch/main/ha-programming.org#headline-36

I use #WriteGood for prose analysis in #Emacs for #Org_mode files and #markdown. I consider myself a competent writer that mostly appreciates flagging passive sentences (from command line utility that doesn't require an online service).

New team uses #just, and write-good flags that word as a weasel word. Fair enough, but I don't want to see a slew of red lines. So I use #remark to strip words in backtick quotes before write-good analysis.

Connected to #flycheck ftw:
https://howardabrams.com/git/howard/hamacs/src/branch/main/ha-programming.org#headline-36

I use #WriteGood for prose analysis in #Emacs for #Org_mode files and #markdown. I consider myself a competent writer that mostly appreciates flagging passive sentences (from command line utility that doesn't require an online service).

New team uses #just, and write-good flags that word as a weasel word. Fair enough, but I don't want to see a slew of red lines. So I use #remark to strip words in backtick quotes before write-good analysis.

Connected to #flycheck ftw:
https://howardabrams.com/git/howard/hamacs/src/branch/main/ha-programming.org#headline-36

I use #WriteGood for prose analysis in #Emacs for #Org_mode files and #markdown. I consider myself a competent writer that mostly appreciates flagging passive sentences (from command line utility that doesn't require an online service).

New team uses #just, and write-good flags that word as a weasel word. Fair enough, but I don't want to see a slew of red lines. So I use #remark to strip words in backtick quotes before write-good analysis.

Connected to #flycheck ftw:
https://howardabrams.com/git/howard/hamacs/src/branch/main/ha-programming.org#headline-36

I use #WriteGood for prose analysis in #Emacs for #Org_mode files and #markdown. I consider myself a competent writer that mostly appreciates flagging passive sentences (from command line utility that doesn't require an online service).

New team uses #just, and write-good flags that word as a weasel word. Fair enough, but I don't want to see a slew of red lines. So I use #remark to strip words in backtick quotes before write-good analysis.

Connected to #flycheck ftw:
https://howardabrams.com/git/howard/hamacs/src/branch/main/ha-programming.org#headline-36

Hello #emacs friends: on some relatively recent update, #flycheck stopped displaying error messages reliably. After some investigation, I have discovered that the culprit seems to be `(customize-set-variable flycheck-display-errors-function 'flycheck-display-errors-via-eldoc) ; after switching to `(customize-set-variable flycheck-display-errors-function 'flycheck-display-error-messages it works again as expected but (obviously) with no colors any more. Is this an issue with eldoc or flycheck?

Hello #emacs friends: on some relatively recent update, #flycheck stopped displaying error messages reliably. After some investigation, I have discovered that the culprit seems to be `(customize-set-variable flycheck-display-errors-function 'flycheck-display-errors-via-eldoc) ; after switching to `(customize-set-variable flycheck-display-errors-function 'flycheck-display-error-messages it works again as expected but (obviously) with no colors any more. Is this an issue with eldoc or flycheck?

Hello #emacs friends: on some relatively recent update, #flycheck stopped displaying error messages reliably. After some investigation, I have discovered that the culprit seems to be `(customize-set-variable flycheck-display-errors-function 'flycheck-display-errors-via-eldoc) ; after switching to `(customize-set-variable flycheck-display-errors-function 'flycheck-display-error-messages it works again as expected but (obviously) with no colors any more. Is this an issue with eldoc or flycheck?

Hello #emacs friends: on some relatively recent update, #flycheck stopped displaying error messages reliably. After some investigation, I have discovered that the culprit seems to be `(customize-set-variable flycheck-display-errors-function 'flycheck-display-errors-via-eldoc) ; after switching to `(customize-set-variable flycheck-display-errors-function 'flycheck-display-error-messages it works again as expected but (obviously) with no colors any more. Is this an issue with eldoc or flycheck?

Hello #emacs friends: on some relatively recent update, #flycheck stopped displaying error messages reliably. After some investigation, I have discovered that the culprit seems to be `(customize-set-variable flycheck-display-errors-function 'flycheck-display-errors-via-eldoc) ; after switching to `(customize-set-variable flycheck-display-errors-function 'flycheck-display-error-messages it works again as expected but (obviously) with no colors any more. Is this an issue with eldoc or flycheck?

An FYI to #Flycheck users out there.

For a few days I've doing a massive cleanup on the issues, the docs and the codebase, and I've been aggressive closing tickets (with or without fixing them) and removing support for obsolete linters.

As you can imagine - that's a preparation step for the next release, so adventurous folks are invited to play with the latest snapshots from MELPA.

#Emacs

An FYI to #Flycheck users out there.

For a few days I've doing a massive cleanup on the issues, the docs and the codebase, and I've been aggressive closing tickets (with or without fixing them) and removing support for obsolete linters.

As you can imagine - that's a preparation step for the next release, so adventurous folks are invited to play with the latest snapshots from MELPA.

#Emacs

An FYI to #Flycheck users out there.

For a few days I've doing a massive cleanup on the issues, the docs and the codebase, and I've been aggressive closing tickets (with or without fixing them) and removing support for obsolete linters.

As you can imagine - that's a preparation step for the next release, so adventurous folks are invited to play with the latest snapshots from MELPA.

#Emacs

An FYI to #Flycheck users out there.

For a few days I've doing a massive cleanup on the issues, the docs and the codebase, and I've been aggressive closing tickets (with or without fixing them) and removing support for obsolete linters.

As you can imagine - that's a preparation step for the next release, so adventurous folks are invited to play with the latest snapshots from MELPA.

#Emacs

An FYI to #Flycheck users out there.

For a few days I've doing a massive cleanup on the issues, the docs and the codebase, and I've been aggressive closing tickets (with or without fixing them) and removing support for obsolete linters.

As you can imagine - that's a preparation step for the next release, so adventurous folks are invited to play with the latest snapshots from MELPA.

#Emacs

flycheck-eglot 1.0 was recently tagged. (see https://github.com/flycheck/flycheck-eglot) The project has been in a stable state for a while now and the version 1.0 reflects this. I know most Eglot users are probably using Flymake these days, but in the land of Emacs it's good to have options. ;-)

#Emacs #LSP #Flycheck

flycheck-eglot 1.0 was recently tagged. (see https://github.com/flycheck/flycheck-eglot) The project has been in a stable state for a while now and the version 1.0 reflects this. I know most Eglot users are probably using Flymake these days, but in the land of Emacs it's good to have options. ;-)

#Emacs #LSP #Flycheck

flycheck-eglot 1.0 was recently tagged. (see https://github.com/flycheck/flycheck-eglot) The project has been in a stable state for a while now and the version 1.0 reflects this. I know most Eglot users are probably using Flymake these days, but in the land of Emacs it's good to have options. ;-)

#Emacs #LSP #Flycheck

flycheck-eglot 1.0 was recently tagged. (see https://github.com/flycheck/flycheck-eglot) The project has been in a stable state for a while now and the version 1.0 reflects this. I know most Eglot users are probably using Flymake these days, but in the land of Emacs it's good to have options. ;-)

#Emacs #LSP #Flycheck

flycheck-eglot 1.0 was recently tagged. (see https://github.com/flycheck/flycheck-eglot) The project has been in a stable state for a while now and the version 1.0 reflects this. I know most Eglot users are probably using Flymake these days, but in the land of Emacs it's good to have options. ;-)

#Emacs #LSP #Flycheck

It includes .dir-locals.el setting Teensyduino defaults for Flycheck/Emacs...

#emacs #teensy #teensyduino #flycheck

https://codeberg.org/zabuxx/Fontsy/src/branch/main/Fontsy/.dir-locals.el

It includes .dir-locals.el setting Teensyduino defaults for Flycheck/Emacs...

#emacs #teensy #teensyduino #flycheck

https://codeberg.org/zabuxx/Fontsy/src/branch/main/Fontsy/.dir-locals.el

It includes .dir-locals.el setting Teensyduino defaults for Flycheck/Emacs...

#emacs #teensy #teensyduino #flycheck

https://codeberg.org/zabuxx/Fontsy/src/branch/main/Fontsy/.dir-locals.el

Why is setting up #Rust with #flycheck on #emacs so complicated? I'm using the rustc, cargo, clippy and rust-analyzer packages from oxalica's rust-overlay repo.


My Emacs config is over at gitlab.com/zstg/nixos-config/-/blob/main/hosts/Krypton/programs/rice/stigmacs/stigmacs.org.

Any #rustaceans facing this predicament?

flycheck-mode returns a 101.

Why is setting up #Rust with #flycheck on #emacs so complicated? I'm using the rustc, cargo, clippy and rust-analyzer packages from oxalica's rust-overlay repo.


My Emacs config is over at gitlab.com/zstg/nixos-config/-/blob/main/hosts/Krypton/programs/rice/stigmacs/stigmacs.org.

Any #rustaceans facing this predicament?

flycheck-mode returns a 101.

Why is setting up #Rust with #flycheck on #emacs so complicated? I'm using the rustc, cargo, clippy and rust-analyzer packages from oxalica's rust-overlay repo.


My Emacs config is over at gitlab.com/zstg/nixos-config/-/blob/main/hosts/Krypton/programs/rice/stigmacs/stigmacs.org.

Any #rustaceans facing this predicament?

flycheck-mode returns a 101.

Why is setting up #Rust with #flycheck on #emacs so complicated? I'm using the rustc, cargo, clippy and rust-analyzer packages from oxalica's rust-overlay repo.


My Emacs config is over at gitlab.com/zstg/nixos-config/-/blob/main/hosts/Krypton/programs/rice/stigmacs/stigmacs.org.

Any #rustaceans facing this predicament?

flycheck-mode returns a 101.

Why is setting up #Rust with #flycheck on #emacs so complicated? I'm using the rustc, cargo, clippy and rust-analyzer packages from oxalica's rust-overlay repo.


My Emacs config is over at gitlab.com/zstg/nixos-config/-/blob/main/hosts/Krypton/programs/rice/stigmacs/stigmacs.org.

Any #rustaceans facing this predicament?

flycheck-mode returns a 101.

What's your favorite #emacs, #python, and #orgmode setup?

Preferably with #LSP and #flycheck, but I can adapt.

I'm going to be using #msfabric soonish, but my experience and opinion is that it's too slow to really work with for quick iterations and poking at things.

What's your favorite #emacs, #python, and #orgmode setup?

Preferably with #LSP and #flycheck, but I can adapt.

I'm going to be using #msfabric soonish, but my experience and opinion is that it's too slow to really work with for quick iterations and poking at things.

What's your favorite #emacs, #python, and #orgmode setup?

Preferably with #LSP and #flycheck, but I can adapt.

I'm going to be using #msfabric soonish, but my experience and opinion is that it's too slow to really work with for quick iterations and poking at things.

What's your favorite #emacs, #python, and #orgmode setup?

Preferably with #LSP and #flycheck, but I can adapt.

I'm going to be using #msfabric soonish, but my experience and opinion is that it's too slow to really work with for quick iterations and poking at things.

I gave up on #emacs #lsp-mode. I am an emacs fan, still. But this got out of hand. It was already hard to get 3 non-gradle/maven projects in, configure key bindings and non-intrusive #flycheck reporting, code suggestions/refactorings as provided by eclipse. Then I tried a small gradle project and got weird error messages: "...is not on the classpath of project , only syntax errors are reported". For fun see the extra-weirdo fixes proposed on the net. 🤦‍♀️ For now I am out.😢 ❓

I gave up on #emacs #lsp-mode. I am an emacs fan, still. But this got out of hand. It was already hard to get 3 non-gradle/maven projects in, configure key bindings and non-intrusive #flycheck reporting, code suggestions/refactorings as provided by eclipse. Then I tried a small gradle project and got weird error messages: "...is not on the classpath of project , only syntax errors are reported". For fun see the extra-weirdo fixes proposed on the net. 🤦‍♀️ For now I am out.😢 ❓

I gave up on #emacs #lsp-mode. I am an emacs fan, still. But this got out of hand. It was already hard to get 3 non-gradle/maven projects in, configure key bindings and non-intrusive #flycheck reporting, code suggestions/refactorings as provided by eclipse. Then I tried a small gradle project and got weird error messages: "...is not on the classpath of project , only syntax errors are reported". For fun see the extra-weirdo fixes proposed on the net. 🤦‍♀️ For now I am out.😢 ❓

I gave up on #emacs #lsp-mode. I am an emacs fan, still. But this got out of hand. It was already hard to get 3 non-gradle/maven projects in, configure key bindings and non-intrusive #flycheck reporting, code suggestions/refactorings as provided by eclipse. Then I tried a small gradle project and got weird error messages: "...is not on the classpath of project , only syntax errors are reported". For fun see the extra-weirdo fixes proposed on the net. 🤦‍♀️ For now I am out.😢 ❓

I gave up on #emacs #lsp-mode. I am an emacs fan, still. But this got out of hand. It was already hard to get 3 non-gradle/maven projects in, configure key bindings and non-intrusive #flycheck reporting, code suggestions/refactorings as provided by eclipse. Then I tried a small gradle project and got weird error messages: "...is not on the classpath of project , only syntax errors are reported". For fun see the extra-weirdo fixes proposed on the net. 🤦‍♀️ For now I am out.😢 ❓

> The state of Flycheck: Alive and kicking
https://metaredux.com/posts/2024/02/10/the-state-of-flycheck-alive-and-kicking.html

I guess that explains recent frequent updates :blobcatcoffee:

#lang_en #flycheck #emacs

> The state of Flycheck: Alive and kicking
https://metaredux.com/posts/2024/02/10/the-state-of-flycheck-alive-and-kicking.html

I guess that explains recent frequent updates :blobcatcoffee:

#lang_en #flycheck #emacs

> The state of Flycheck: Alive and kicking
https://metaredux.com/posts/2024/02/10/the-state-of-flycheck-alive-and-kicking.html

I guess that explains recent frequent updates :blobcatcoffee:

#lang_en #flycheck #emacs

> The state of Flycheck: Alive and kicking
https://metaredux.com/posts/2024/02/10/the-state-of-flycheck-alive-and-kicking.html

I guess that explains recent frequent updates :blobcatcoffee:

#lang_en #flycheck #emacs

There WAS an issue with #Emacs #flycheck applying #Rubocop to a #Ruby buffer with no backing file, but after 3.5 years my fix was merged 🎉

https://github.com/flycheck/flycheck/pull/1793

I encountered this problem for instance when editing an #orgmode src block with C-c ' (org-edit-special).

I think this is the longest I've ever had a successful PR wait.

There WAS an issue with #Emacs #flycheck applying #Rubocop to a #Ruby buffer with no backing file, but after 3.5 years my fix was merged 🎉

https://github.com/flycheck/flycheck/pull/1793

I encountered this problem for instance when editing an #orgmode src block with C-c ' (org-edit-special).

I think this is the longest I've ever had a successful PR wait.

There WAS an issue with #Emacs #flycheck applying #Rubocop to a #Ruby buffer with no backing file, but after 3.5 years my fix was merged 🎉

https://github.com/flycheck/flycheck/pull/1793

I encountered this problem for instance when editing an #orgmode src block with C-c ' (org-edit-special).

I think this is the longest I've ever had a successful PR wait.

There WAS an issue with #Emacs #flycheck applying #Rubocop to a #Ruby buffer with no backing file, but after 3.5 years my fix was merged 🎉

https://github.com/flycheck/flycheck/pull/1793

I encountered this problem for instance when editing an #orgmode src block with C-c ' (org-edit-special).

I think this is the longest I've ever had a successful PR wait.

There WAS an issue with #Emacs #flycheck applying #Rubocop to a #Ruby buffer with no backing file, but after 3.5 years my fix was merged 🎉

https://github.com/flycheck/flycheck/pull/1793

I encountered this problem for instance when editing an #orgmode src block with C-c ' (org-edit-special).

I think this is the longest I've ever had a successful PR wait.

A metaphor to work by. Me, once again trying (and struggling with) #latex to create a #pdf. My partner: "It's just like #lisp, with curly's instead of parentheses". Ahh. (now I remember I am working in an editor made with and for #lisp... let's slurp the eh curly braces. it works... #flycheck open helps keeping everything balanced). #emacs

A metaphor to work by. Me, once again trying (and struggling with) #latex to create a #pdf. My partner: "It's just like #lisp, with curly's instead of parentheses". Ahh. (now I remember I am working in an editor made with and for #lisp... let's slurp the eh curly braces. it works... #flycheck open helps keeping everything balanced). #emacs

A metaphor to work by. Me, once again trying (and struggling with) #latex to create a #pdf. My partner: "It's just like #lisp, with curly's instead of parentheses". Ahh. (now I remember I am working in an editor made with and for #lisp... let's slurp the eh curly braces. it works... #flycheck open helps keeping everything balanced). #emacs

A metaphor to work by. Me, once again trying (and struggling with) #latex to create a #pdf. My partner: "It's just like #lisp, with curly's instead of parentheses". Ahh. (now I remember I am working in an editor made with and for #lisp... let's slurp the eh curly braces. it works... #flycheck open helps keeping everything balanced). #emacs