unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: 25778@debbugs.gnu.org
Subject: bug#25778: 25.1; [PATCH] Drastically simplify xdg-open check
Date: Fri, 17 Feb 2017 22:39:51 -0500	[thread overview]
Message-ID: <olwpco416g.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20170217185514.GA599@odonien.localdomain> (Vasilij Schneidermann's message of "Fri, 17 Feb 2017 19:55:14 +0100")


The area seems a mess, but:

1) nohup was removed from browse-url-xdg-open in 1c0f1a199ca, with no
explanation and as part of a change that seems unrelated.

2) In https://debbugs.gnu.org/9779#20, the author of that change said

    I note that since 22-Jun-2011 browse-url-xdg-open no longer uses
    nohup.  This is either a mistake on my part (I didn't read the
    comment in browse-url-can-use-xdg-open) or it is indeed
    unnecessary and therefore isn't a requirement for xdg-open.

3) In reply, Jan said in https://debbugs.gnu.org/9779#29

    See discussion at
    http://lists.gnu.org/archive/html/emacs-devel/2009-07/msg00279.html.
    nohup is still needed for xdg-open.

And AFAICS that was the last comment about nohup. No-one ever seems to
have followed up Jan's comment.





  reply	other threads:[~2017-02-18  3:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 18:16 bug#25778: 25.1; [PATCH] Drastically simplify xdg-open check Vasilij Schneidermann
2017-02-17 18:38 ` Eli Zaretskii
2017-02-17 18:55   ` Vasilij Schneidermann
2017-02-18  3:39     ` Glenn Morris [this message]
2017-02-18  3:46       ` Glenn Morris
2017-02-18  8:55         ` Vasilij Schneidermann
2017-02-19  0:31           ` Glenn Morris
2017-02-19 13:06             ` Vasilij Schneidermann
2017-02-18  7:58     ` Eli Zaretskii
2017-02-18  8:50       ` Vasilij Schneidermann
2017-03-10  3:13 ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=olwpco416g.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=25778@debbugs.gnu.org \
    --cc=v.schneidermann@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).