Incidentally, I discovered that running (from the Terminal) ./love works where love does not. The latter seems to make it look for a command or bash script, where the former tells it to open the file as an executable. Just in case that's helpful to anyone.

It's standard practice in Linux that commands are ONLY looked for in the path, and not in the current directory. That will happen with each and every program that is not in your path, e.g. 'configure', unless you run 'sudo make install' and it's installed to a directory in your path (e.g. /usr/bin or /usr/local/bin; try ./configure --help to see or change the defaults). You can add . to your path but that's really not recommended.

As the developer of love-release, I'm confused.
You have dropped the "patch" version number (11.1 instead of 11.0), and the filename is love-11.1-win64.zip (without the patch number), but inside the zip file, you kept the patch number: love-11.1.0-win64/love.exe, which forces me to make a special case for this.

function love.load()
end
function love.draw()
love.graphics.setColor(1,1,1,1)
love.graphics.print("This is text",0,0)
end
function love.update()
end
function love.keypressed(key)
if key == "escape" then
love.event.quit()
end
end

Update
Updated to 11.1 in another computer and it works fine, it must be something wrong about my pc