Dear Charles, thanks for driving this.
On Mon, Dec 28, 2020 at 08:15:45AM +0900, Charles Plessy wrote: > I went ahead and uploaded to Sid mime-support version 3.68, which > provides /usr/bin/open as a symbolic link to /usr/bin/run-mailcap using > the alternatives system, at a priority of 30. I welcome other > alternatives. yay! > I also changed the behaviour of run-mailcap so that, when run as `open`, > it will not replace the file with a temporary copy when its name needs > to be escaped. As a consequence, there is no redundancy between the > `see` and `open` commands. yay! > At the moment the manual page of open is simply the one of run-mailcap, > but I plan to provide a specific one. Given the lack of answer to my > previous email (quoted below), I have not implemented URL support in > /usr/bin/run-mailcap. yay! > > Le Sat, Oct 10, 2020 at 04:27:17AM +0900, Charles Plessy a écrit : > > > > > > May I ask you for extra information on how important is it to support > > > URLs, and if anything beyond file:/, http:// and https:// would need > > > to be supported ? > > ... > > > Also, can you give me a pointer to an explanation of what file:/ URLs > > > are useful for ? I read RFC 8089, but still did not get the point. > > ... > > > Since `eog http://example.com/image.png` will open the image, > > > shouldn't an "open" program ask to the server what the media type of > > > the URL is, and pass it to the default program able to handle it, > > > instead of just visualising in the browser ? I agree, an "open" program should ask to the server what the media type of the URL is, and pass it to the default program able to handle it. Thanks, again! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C ⠈⠳⣄ There are no jobs on a dead planet.
signature.asc
Description: PGP signature
