From: Andreas Schwab <schwab@linux-m68k.org>
To: "Matthew Persico (BLOOMBERG/ 919 3RD A)" <mpersico5@bloomberg.net>
Cc: stefan@marxist.se, 21477@debbugs.gnu.org
Subject: bug#21477: 24.4; Imenu - improper parse of shell function names
Date: Wed, 12 Aug 2020 16:54:35 +0200 [thread overview]
Message-ID: <874kp7zzh0.fsf@igel.home> (raw)
In-Reply-To: <5F33F3F000D2020C00390369_0_31281@msllnjpmsgsv06> (Matthew Persico's message of "Wed, 12 Aug 2020 13:51:44 -0000")
On Aug 12 2020, Matthew Persico (BLOOMBERG/ 919 3RD A) wrote:
> I can reproduce this behaviour, but is it really a bug? Aren't the
> names with '-' invalid?
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.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-08-12 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 14:14 bug#21477: 24.4; Imenu - improper parse of shell function names Matthew Persico (BLOOMBERG/ 731 LEX)
2020-08-12 4:15 ` Stefan Kangas
2020-08-12 13:51 ` Matthew Persico (BLOOMBERG/ 919 3RD A)
2020-08-12 14:08 ` Stefan Kangas
2020-08-12 14:54 ` Andreas Schwab [this message]
2020-08-12 15:59 ` Stefan Kangas
2020-08-12 14:36 ` Matthew Persico (BLOOMBERG/ 919 3RD A)
2020-08-12 15:59 ` Stefan Kangas
2020-08-12 15:57 ` Matthew Persico (BLOOMBERG/ 919 3RD A)
2020-08-20 18:13 ` Matthew Persico (BLOOMBERG/ 919 3RD A)
2020-08-20 18:41 ` Stefan Kangas
2020-08-20 18:42 ` Matthew Persico (BLOOMBERG/ 919 3RD A)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kp7zzh0.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=21477@debbugs.gnu.org \
--cc=mpersico5@bloomberg.net \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.