Re: Can't trace script not in PATH

[Peter Stephenson <pws@xxxxxxx>]

On Mon, 15 Mar 2010 12:59:23 +0000
Peter Stephenson <pws@xxxxxxx> wrote:
> +    /* sets INTERACTIVE, SHINSTDIN and SINGLECOMMAND */
> +    parseargs(argv, &runscript);
>  
>      SHTTY = -1;
>      init_io();
>      setupvals();
> +    setupshin(runscript);
> +
>      init_signals();
>      init_bltinmods();
>      init_builtins();

ackshly, the new code should be after run_init_scripts(), just off the
bottom of the hunk, to ensure PATH has been set up, so I will move it.
(Remember all I'm changing is how we find the file, I'm not changing
anything to do with where code is executed, although it will now execute
start-up files even if can't find the script which didn't happen before.)

-- 
Peter Stephenson <pws@xxxxxxx>            Software Engineer
Tel: +44 (0)1223 692070                   Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom