public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/16059] wordexp(3) -- A[0]='a b' gives error Date: Thu, 24 Oct 2013 13:30:00 -0000 [thread overview] Message-ID: <bug-16059-131-TIbrbgNIKm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16059-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=16059 --- Comment #4 from Andreas Schwab <schwab@linux-m68k.org> --- There are a lot of problems with quoting in wordexp parsing. - quoted glob meta characters need to be requoted for glob, but the result must undergo quote removal if no file was matched - unterminated quoting needs to be diagnosed - the check to distinguish $((foo)) from $((foo);(bar)) doesn't handle quoted parens - parse_comm doesn't handle backslash quoting -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-24 13:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-17 18:54 [Bug libc/16059] New: " opengeometry at yahoo dot ca 2013-10-18 15:09 ` [Bug libc/16059] " opengeometry at yahoo dot ca 2013-10-18 15:22 ` neleai at seznam dot cz 2013-10-24 13:30 ` schwab@linux-m68k.org [this message] 2014-06-13 12:39 ` fweimer at redhat dot com 2015-08-27 22:17 ` [Bug glob/16059] " jsm28 at gcc dot gnu.org
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=bug-16059-131-TIbrbgNIKm@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).