Re: alias expansion bug with matching { ... }

Steffen Nurpmeso dixit: >Would you mind re-allowing hyphen-minus again? That really has Sure, done. Although I kinda follow the idea of not letting them start with a hyphen-minus and have enacted that as well. bye, //mirabilos -- 21:12⎜ sogar bei opensolaris haben die von der community so

Re: alias expansion bug with matching { ... }

Hallo! Thorsten Glaser wrote: |Dixi quod… |>Commit ID: 10058E5A1067AFA1BBA ... |Oh well. For the sake of consistency. But fixing this DID uncover |a re-entrancy bug in 'typeset -f' ouput (which IS also used in some |other places internally): ... |When deferring alias

Re: alias expansion bug with matching { ... }

Martijn Dekker dixit: >Define "legit" and "weird" (and explain how they're mutually exclusive). ;-) ;-) >What I'm doing is this: >https://github.com/modernish/modernish#use-varsetlocal #user-content-use-varsetlocal by the way. I see. I can also see the benefit of expanding the aliases at the

Re: alias expansion bug with matching { ... }

Op 04-04-17 om 02:26 schreef Thorsten Glaser: > That’s no excuse… pdksh does simple search for a matching ) > in command substitutions, failing $(case x in y) ;; esac ). Yeah, I've run into that. It even parses quote marks in comments within command substitutions, requiring them to be balanced

Re: alias expansion bug with matching { ... }

Martijn Dekker dixit: >It works on every other shell, even pdksh. That’s no excuse… pdksh does simple search for a matching ) in command substitutions, failing $(case x in y) ;; esac ). >But this does not: > >$ var=$({ OPEN echo hi; CLOSE }) && echo "$var" >mksh: syntax error: ')' unexpected I