From: "Matthew Persico (BLOOMBERG/ 919 3RD A)" <mpersico5@bloomberg.net>
To: schwab@linux-m68k.org, stefan@marxist.se
Cc: 21477@debbugs.gnu.org
Subject: bug#21477: 24.4; Imenu - improper parse of shell function names
Date: Thu, 20 Aug 2020 18:13:19 -0000 [thread overview]
Message-ID: <5F3EBD3F005D05A6003905CC_0_68837@msllnjpmsgsv06> (raw)
In-Reply-To: <55F6D62E02050314003904F5_0_77779@p057>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
I am not sure what is going on here, but I just loaded up this file and it parsed just fine.
Now, I KNOW that this didn't work when I reported it. And Stefan was able to reproduce it.
I wonder if Stefan can still reproduce?
Since I can't reproduce, I have no issue with closing. If it regresses, I'll open a new issue, making a note of the versions of various packages, which would certainly help diagnosis.
Stefan, it's been a while - can you send me a link to my original bug report?
From: stefan@marxist.se At: 08/12/20 12:00:09To: Matthew Persico (BLOOMBERG/ 919 3RD A ) , schwab@linux-m68k.org
Cc: 21477@debbugs.gnu.org
Subject: Re: bug#21477: 24.4; Imenu - improper parse of shell function names
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
[-- Attachment #2: Type: text/html, Size: 3056 bytes --]
next prev parent reply other threads:[~2020-08-20 18:13 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
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) [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5F3EBD3F005D05A6003905CC_0_68837@msllnjpmsgsv06 \
--to=mpersico5@bloomberg.net \
--cc=21477@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).