everett, 1 year ago (edited 11 months ago) 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… <span style="color:#323232;">#!/bin/bash </span><span style="color:#323232;">cd ~/Downloads </span><span style="color:#323232;">chmod +x $(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) </span><span style="color:#323232;">./$(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) </span> 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…
<span style="color:#323232;">#!/bin/bash </span><span style="color:#323232;">cd ~/Downloads </span><span style="color:#323232;">chmod +x $(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) </span><span style="color:#323232;">./$(ls | grep Appname.*AppImage$ | sort -rV | head -n 1) </span>
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!
.10
sort -V