TPDD1: `ls` leaves the drive in an unexpected state, requires `smack` to recover about pdd.sh

[bkw777]

A better way to remove the problem is comment out the last 4 lines of lcmd_ls()

	#((${#err_msg[*]})) && return
	#_sleep 0.01 ;quiet=true get_condition || return $?
	#((operation_mode==0)) && { _sleep 0.01 ; quiet=true fcmd_mode 1 ; }
	#printf "%-32.32s %4.4s\n" "$((free_sectors*SECTOR_DATA_LEN)) bytes free" "${err_msg[-1]}" ;unset err_msg[-1]

Then you can run ls without weirdness.
It shouldn't be complicated or a mystery to just switch back out of fdc-mode and to properly keep track of what state the drive should be in, and this used to work fine, but apparently I lost something somewhere in all the recent changes.

[bkw777]

seems to be fixed or never was a bug in the published versions

I reverted a few wip changes in a local unpublished branch and then git bisect showed no problem all the way to the current head. oh well false alarm.