This came up in https://bugzilla.redhat.com/show_bug.cgi?id=472402 but
is worth a more general discussion amongst the developer community, I
think.
The xdg-open tool is generally a good thing for the users, but at
least a couple of cases have arisen where it is not doing the right
thing. The prob
On Thursday 25 June 2009, Jerry James wrote:
> It appears to me that we either need to split xdg-open into two tools,
> representing the two modes of operation, or else give xdg-open a
> command-line switch to demand synchronous operation.
IMO the latter is clearly preferable, and would be even a
On Thu, Jun 25, 2009 at 12:32 PM, Ville Skyttä wrote:
> IMO the latter is clearly preferable, and would be even a good default. But
> then again, it might be too late to change the default as it could break stuff
> (even if the xdg-open man page doesn't document async/sync operation at the
> momen
On 07/03/2009 12:00 AM, Jerry James wrote:
>
> I am more and more of the opinion that xdg-open is simply the wrong
> tool for viewing/editing temporary files. It wasn't built for that
> use case, and the tools it invokes were not either. I think we need
> something different altogether. Should
On Thu, Jul 2, 2009 at 2:30 PM, Jerry James wrote:
>
>
> I am more and more of the opinion that xdg-open is simply the wrong
> tool for viewing/editing temporary files. It wasn't built for that
> use case, and the tools it invokes were not either.
I think the easiest fix here is for the app not t
On Thu, Jul 2, 2009 at 12:47 PM, Colin Walters wrote:
> I think the easiest fix here is for the app not to delete the
> temporary file immediately after the helper exits. Just write it in
> $TMPDIR and let tempreaper come along and eat it later.
I am an XEmacs developer, and I would like to fix t
