LXterm on Lubuntu I have noted to not be drag-and-drop compatible when dropping folders or files in. I have no idea if this is due to LXDE being so light or if LXterm doesn't support it at all. I have not tested X or UXterm.
For now Lubuntu users can right click on the folder, and select "Copy file path" in the drop down menu. You can paste that into the script and it will take it. Sorry for the extra steps.
Also, Windows 10 users using WSL. Though WSL is fully compatible with my script, there are some WSL changes in the newer builds that allow for drag-and-drop translations. For instance, in the stable build, dragging files in will automatically write the current Windows directory:
C:\Users\[usr]\[path_to_file]
while in the Insider builds of Windows, it gets translated into something WSL can understand:
/mnt/c/Users/[usr]/[path_to_file]
This is a Windows-end bug and is best resolved by becoming an insider. I have no idea if the translation feature is present in the slow builds, but it is definitely in fast builds. I unfortunately cannot go to either due to a bug with Windows and AMD in memory handling.
LXterm on Lubuntu I have noted to not be drag-and-drop compatible when dropping folders or files in. I have no idea if this is due to LXDE being so light or if LXterm doesn't support it at all. I have not tested X or UXterm.
For now Lubuntu users can right click on the folder, and select "Copy file path" in the drop down menu. You can paste that into the script and it will take it. Sorry for the extra steps.
Also, Windows 10 users using WSL. Though WSL is fully compatible with my script, there are some WSL changes in the newer builds that allow for drag-and-drop translations. For instance, in the stable build, dragging files in will automatically write the current Windows directory:
while in the Insider builds of Windows, it gets translated into something WSL can understand:
This is a Windows-end bug and is best resolved by becoming an insider. I have no idea if the translation feature is present in the slow builds, but it is definitely in fast builds. I unfortunately cannot go to either due to a bug with Windows and AMD in memory handling.