unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vasilij Schneidermann <v.schneidermann@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 25778@debbugs.gnu.org
Subject: bug#25778: 25.1; [PATCH] Drastically simplify xdg-open check
Date: Sun, 19 Feb 2017 14:06:50 +0100	[thread overview]
Message-ID: <20170219130650.GA647@odonien.localdomain> (raw)
In-Reply-To: <4ak28nyqa5.fsf@fencepost.gnu.org>

> As you can see from that above report, they don't show any signs of
> fixing it.

Well, fine.  I'm sorry for not noticing a five year old piece of code
that got mistakenly removed without anyone complaining.  What I don't
understand is why my patch (removing IMHO unnecessary DE detection) is
related to using nohup to work around a problem with xdg-open and
gnome-open/gvfs-open.  If you consider fixing the nohup problem a
prerequisite before this patch can be applied, OK, do that then, I can
wait until that's done and recommence discussion on the other issue.

That aside, I cannot reproduce any weird behavior, be it with or without
nohup and gvfs-open.  Both `(call-process "gvfs-open" nil 0 nil
"foo.pdf")` and `(call-process "nohup" nil 0 nil "gvfs-open"
"foo.pdf")` spawn my PDF reader successfully and don't do anything weird
after closing it.  Same if I pass "http://ix.de/" as last argument.  I
therefore consider the nohup issue a case of cargo-culting and would
like to drop its discussion entirely as it does not help with the
current issue.





  reply	other threads:[~2017-02-19 13:06 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
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 [this message]
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=20170219130650.GA647@odonien.localdomain \
    --to=v.schneidermann@gmail.com \
    --cc=25778@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /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).