I canāt test this right now, but will do as soon as I am back. But Iām a bit confused, as I donāt think we changed something on how Picard is being launched. What operating system are you using and how exactly have you installed Picard?
That ā[6] 27157ā indicates that itās bash itself that put the job with process id into the background, not picard itself. You can check with alias picard, declare -f picard, type -t picard whether picard is an alias, function, or something else entirely. Whatever it is, itās very likely that picard is not just the picard binary on your system
$ which picard ; alias picard ; type -t picard
/usr/bin/picard
alias picard='picard &'
alias
$ \picard . &
[6] 99282
The second command works as expected; embarrassed I didnāt catch thisā¦and I donāt remember adding it but my ~/.bash_aliases is ca. 150 lines so who knows. I probably got tired of having to ^Z $ bg and didnāt consider the consequences.
On that note, more CLI support for Picard would be niceā¦though off the top of my head I canāt think of any ideas except maybe a -y to automatically save fully-matched releases and exit, e.g.,
$ picard -y FILE
would automatically tag and save āFILEā then exit.