` ... :169:47: warning: Did you forget to close this double quoted string? [SC1078]`
The SG1078 message indicates the belief there is a missing double quote. In my case this is often a mismatched bracket such as (...} or [...} already coded inside of double quotes when referencing a variable in bash. Should there be a consideration for improving this message or when it is used? Thanks for allowing me to submit this.
Bash version appears to be 1.38 Sulimar built after 2023-12-05; Using GTK+ v3.24.38 and GLib v2.74.6 runtime libraries. Running on a 64 bit Raspberry PI OS 6.6.51+rpt-rpi-v8.
`SC1078` is a shellcheck error: https://www.shellcheck.net/wiki/SC1078. It does not originate in Geany.
You don't mention how or where you get this warning, so I'll assume it is by running some (possibly predefined) build action for a bash file. If you think the error is not incorrect or misleading, you'll have to speak to shellcheck maintainers instead. Their issue tracker is here: https://github.com/koalaman/shellcheck/issues
Closed #4041 as completed.
As @dolik-rce mentioned it's not a Geany issue, but I still have a couple remarks: * not showing some code, it's hard to understand the details of what incorrect code is triggering the issue. * given that you have a fairly old version of Geany, you might also have a fairly old version of shellcheck; thus this potentially has already been improved -- or not, I don't know.
At any rate, realize that understanding invalid code to give meaningful errors is very hard, so we need to indulge shellcheck 🙂
`SC1078` is a shellcheck error: https://www.shellcheck.net/wiki/SC1078. It does not originate in Geany.
You don't mention how or where you get this warning, so I'll assume it is by running some (possibly predefined) build action for a bash file. If you think the error is not incorrect or misleading, you'll have to speak to shellcheck maintainers instead. Their issue tracker is here: https://github.com/koalaman/shellcheck/issues
Sorry my mistake will try an appropriate forum.
Thanks, my mistake -- submitted to the proper people. Thanks again.
On Tuesday, November 12, 2024 at 01:09:28 PM EST, Colomban Wendling ***@***.***> wrote:
As @dolik-rce mentioned it's not a Geany issue, but I still have a couple remarks:
- not showing some code, it's hard to understand the details of what incorrect code is triggering the issue. - given that you have a fairly old version of Geany, you might also have a fairly old version of shellcheck; thus this potentially has already been improved -- or not, I don't know.
At any rate, realize that understanding invalid code to give meaningful errors is very hard, so we need to indulge shellcheck 🙂
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
github-comments@lists.geany.org