tdTrX@lemmy.ml to Linux@lemmy.mlEnglish · 4 days agoHow to run firefox -p command and have firefox opened after closing the terminal like WIndows Run box.message-squaremessage-square18fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1message-squareHow to run firefox -p command and have firefox opened after closing the terminal like WIndows Run box.tdTrX@lemmy.ml to Linux@lemmy.mlEnglish · 4 days agomessage-square18fedilink
minus-squaretdTrX@lemmy.mlOPlinkfedilinkEnglisharrow-up0·4 days ago~$ firefox -p &; disown bash: syntax error near unexpected token `;’
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up0·4 days agojust omit the ; firefox -p & disown
minus-squarefelsiq@piefed.ziplinkfedilinkEnglisharrow-up0·4 days agoLooks like I’ve gotten too spoiled with zsh, I guess that doesn’t work with bash. Doing it in two separate commands should work tho, ie firefox -p & and then disown
minus-squarealiceitc@lemmy.blahaj.zonelinkfedilinkarrow-up0·4 days agoit should be enough to put a space between & and ; like this: firefox -p & ; disown but I’m not 100% sure. I’m also very spoiled by zsh, and I also remember encountering this issue.
minus-squarefelsiq@piefed.ziplinkfedilinkEnglisharrow-up0·4 days agoI actually started up bash to test this when op first responded, and the space had the same problem
minus-squarealiceitc@lemmy.blahaj.zonelinkfedilinkarrow-up0·edit-24 days agoThanks for the correction. I read the bash documentation and I think you simply don’t need the ;. The & is already a command separator, just like ; Tested with bash: sleep 100 & echo test prints right away. https://www.gnu.org/software/bash/manual/bash.html#Lists
~$ firefox -p &; disown bash: syntax error near unexpected token `;’
just omit the
;firefox -p & disownLooks like I’ve gotten too spoiled with zsh, I guess that doesn’t work with bash. Doing it in two separate commands should work tho, ie
firefox -p &and thendisownit should be enough to put a space between
∧like this:firefox -p & ; disownbut I’m not 100% sure.I’m also very spoiled by zsh, and I also remember encountering this issue.
I actually started up bash to test this when op first responded, and the space had the same problem
Thanks for the correction.
I read the bash documentation and I think you simply don’t need the
;. The & is already a command separator, just like ;Tested with bash:
sleep 100 & echo testprints right away.https://www.gnu.org/software/bash/manual/bash.html#Lists