Bugzilla Bug 32941

Both Sash 3.4 ( 3.4-r5 ) and sash 3.6 ( 3.6 ) cannot be used to execute script
files. The result is that sash just hangs, until Ctrl-C is pressed or the
process is killed. Compiling sash's package manually fixes this ( without
applying the diff files )

Reproducible: Always
Steps to Reproduce:
1. In sash 3.6, execute 'sash -f <filename>'
2. In sash 3.4, execute sash, and from within it, execute 'source <filename>'

Actual Results:  
sash hangs

Expected Results:  
Execution of commands in the file

What patch would this happen to be? The '-all-static' patch or the readline
patch?

I don't know, but I guess it has to do with the readline patch, since manually
compiling sash also resulted in a static executable ( That worked correctly
). Unfortunately, I'm unable to verify this for the next couple of days.

Can you try syncing your tree, upgrading readline and sash and see if you still
get this? Thanks.

Still a no go.

Updated to readline-4.3-r5, then emerged sash-3.6, and still the following file hangs:

#!/bin/sash -f
echo Hello

Fixed - it should hit the Portage tree within an hour, so it should go away
once you sync and re-merge 3.6; or merge 3.7. Thanks!