SkullHex2@lemmy.ml to Linux@lemmy.mlEnglish · edit-219 days agoAAAAlemmy.mlexternal-linkmessage-square19fedilinkarrow-up177arrow-down14file-text
arrow-up173arrow-down1external-linkAAAAlemmy.mlSkullHex2@lemmy.ml to Linux@lemmy.mlEnglish · edit-219 days agomessage-square19fedilinkfile-text
minus-squareeverett@lemmy.mllinkfedilinkarrow-up2·edit-211 months agoHappy to hear if there are glaring problems with this approach, but if you can assume files named with version numbers, you can use a script to always launch the newest… #!/bin/bash cd ~/Downloads chmod +x $(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) ./$(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) Or you could change the script to sort by file modified date and launch the newest. edit: Discovered an issue with version numbering like .10 and learned about the sort -V switch that fixes it!
Happy to hear if there are glaring problems with this approach, but if you can assume files named with version numbers, you can use a script to always launch the newest…
#!/bin/bash cd ~/Downloads chmod +x $(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) ./$(ls | grep Appname.*AppImage$ | sort -rV | head -n 1)
Or you could change the script to sort by file modified date and launch the newest.
edit: Discovered an issue with version numbering like
.10
and learned about thesort -V
switch that fixes it!