zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug in alias expansion
Date: Wed, 18 Nov 2015 10:09:58 -0800	[thread overview]
Message-ID: <151118100958.ZM4522@torch.brasslantern.com> (raw)
In-Reply-To: <20151118161431.360006a5@pwslap01u.europe.root.pri>

On Nov 18,  4:14pm, Peter Stephenson wrote:
} Subject: Re: Bug in alias expansion
}
} On Wed, 18 Nov 2015 07:52:46 -0800
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > On Nov 18,  2:13pm, Peter Stephenson wrote:
} > } Currently we expand both when parsing the entrails of the $(...)
} > } and executing it, but should possibly only do so in the latter case.
} > } I haven't look to see if this affects any tests.
} > 
} > Would not-expanding affect cmd_or_math() adversely?  Is that why we
} > expand and then backtrack?
} 
} I can't offhand think of a case.  The crucial thing about cmd_or_math()
} is to get the parentheses right.

So it turns out that dquote_parse() has almost nothing to do with the
bug (though probably still a lot to do with whether the aliases ought
to expand at all); it's skipcomm() that causes the error.  This small
change fixes the problem seen in 37128:

diff --git a/Src/lex.c b/Src/lex.c
index 81904c1..0f260d0 100644
--- a/Src/lex.c
+++ b/Src/lex.c
@@ -2022,7 +2022,9 @@ skipcomm(void)
     int new_lexstop, new_lex_add_raw;
     int save_infor = infor;
     struct lexbufstate new_lexbuf;
+    int noalias = noaliases;
 
+    noaliases = 1;
     infor = 0;
     cmdpush(CS_CMDSUBST);
     SETPARBEGIN
@@ -2140,6 +2142,7 @@ skipcomm(void)
 	SETPAREND
     cmdpop();
     infor = save_infor;
+    noaliases = noalias;
 
     return lexstop;
 #endif

All "make check" tests still pass.  And now:

torch% alias -g foo='echo xyz)$(echo zyx'
torch% print $(foo)
zsh: parse error near `)'
zsh: parse error in command substitution
torch% 


  reply	other threads:[~2015-11-18 18:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 18:03 Kynn Jones
2015-11-14  1:03 ` Bart Schaefer
2015-11-14 18:57   ` Kynn Jones
2015-11-14 19:03     ` Bart Schaefer
2015-11-14 19:19       ` Kynn Jones
2015-11-14 21:40         ` Bart Schaefer
2015-11-14 22:20           ` Kynn Jones
2015-11-15 20:03 ` Peter Stephenson
2015-11-15 21:52   ` Bart Schaefer
2015-11-15 22:26     ` Bart Schaefer
2015-11-15 22:48   ` Bart Schaefer
2015-11-16  0:50     ` Mikael Magnusson
2015-11-16  3:24       ` Bart Schaefer
2015-11-16  5:42         ` Mikael Magnusson
2015-11-18 10:42     ` Peter Stephenson
2015-11-18 14:13       ` Peter Stephenson
2015-11-18 15:52         ` Bart Schaefer
2015-11-18 16:14           ` Peter Stephenson
2015-11-18 18:09             ` Bart Schaefer [this message]
2015-11-17 17:29   ` Peter Stephenson
2015-11-18  4:55     ` Bart Schaefer
2015-11-18 10:30       ` Peter Stephenson

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=151118100958.ZM4522@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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: 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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).