[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21477: 24.4; Imenu - improper parse of shell function names
From: |
Stefan Kangas |
Subject: |
bug#21477: 24.4; Imenu - improper parse of shell function names |
Date: |
Wed, 12 Aug 2020 08:59:53 -0700 |
Andreas Schwab <schwab@linux-m68k.org> writes:
> It's a POSIX extension, enforced in POSIX mode:
>
> 13. Function names must be valid shell 'name's. That is, they may not
> contain characters other than letters, digits, and underscores, and
> may not start with a digit. Declaring a function with an invalid
> name causes a fatal syntax error in non-interactive shells.
Right. Well, then adding syntax highlighting here would in a way
encourage people to write non-POSIX conformant shell code, which even if
it happens to work in Bash sounds like a bad idea.
So I'm leaning towards closing this bug report as wontfix.
Any other opinions?
Best regards,
Stefan Kangas
- bug#21477: 24.4; Imenu - improper parse of shell function names, Stefan Kangas, 2020/08/12
- bug#21477: 24.4; Imenu - improper parse of shell function names, Matthew Persico (BLOOMBERG/ 919 3RD A), 2020/08/12
- bug#21477: 24.4; Imenu - improper parse of shell function names, Matthew Persico (BLOOMBERG/ 919 3RD A), 2020/08/12
- bug#21477: 24.4; Imenu - improper parse of shell function names, Matthew Persico (BLOOMBERG/ 919 3RD A), 2020/08/12
- bug#21477: 24.4; Imenu - improper parse of shell function names, Matthew Persico (BLOOMBERG/ 919 3RD A), 2020/08/20
- bug#21477: 24.4; Imenu - improper parse of shell function names, Matthew Persico (BLOOMBERG/ 919 3RD A), 2020/08/20