"Axel Liljencrantz" <[EMAIL PROTECTED]> writes: Hi Axel,
> Adding a $job_id varaible or a --last-job switch to the 'status' > builtin that tells you the job id of the last command to execute would > be a simple thing to add. Is it a good idea? Which one? I'm inclined > to like the status solution better, since I generally feel that a > variable should not be something magical. status --last-job would be as good as $job_id, so if you like the former better, I'm happy with it. ;-) Bye, Tassilo -- Do you know why Baskin Robbins only has 31 flavors? Because Chuck Norris doesn't like Fudge Ripple. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
