emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-open-file immediately termininates when calling xdg-open that calls emacsclient
Date: Sun, 22 May 2022 15:13:41 +0700	[thread overview]
Message-ID: <t6crbm$ao9$1@ciao.gmane.io> (raw)
In-Reply-To: <87ee0mp4hb.fsf@localhost>

On 22/05/2022 11:37, Ihor Radchenko wrote:
> I have a problem with the following commits:
> 869b7a21b org-open-file: Avoid make-process for Emacs 24 compatibility
> 5db61eb0f org.el: Avoid xdg-open silent failure
> They both set process-connection-type to nil/'pipe. Somehow, this change
> breaks org-open-file for me when org-open-file calls xdg-open and xdg is
> confugured to open the file with emacsclient. I only see a flicker and
> the file does not open. Sometimes, Emacs even crashes.

I can not reproduce a problem, however I tried to factor-out xdg-open. 
Emacs-27.1, a minimal LXC container, so "&" to simulate kde-open5 
starting process in background. On the other hand I consider behavior 
when emacsclient is called from emacs as confusing due to requirement of 
C-x # to notify emacs about completion.

---- >8 ----
#+begin_src elisp
   (push '("\\.txt\\'" . "emacsclient %s &") org-file-apps)

---- 8< ----

Nothing happens if emacs server is not started, but error handling was 
sacrificed for compatibility with old emacs versions.

Do you see the same problem for a function from mailcap.el in the 
development emacs version?

Eli Zaretskii suspected some compatibility issue, but he successfully 
resisted my attempts to pull some details from him. I know how to create 
a MIME handler that will cause 100% CPU consumption by Emacs for pipe 
processes, but he does not consider it as a real problem.

> If I change the process type back to default tty value, things work
> again as expected.

You might try `call-process' with 0 as DESTINATION (attention! not nil!).

See #+begin_comment snippet from the following patch (this part was not 
committed since Robert convinced me that it is confusing):
Max Nikulin to emacs-orgmode. [PATCH v3] Fix FAQ entry about mailto 
links. Mon, 14 Feb 2022 20:22:14 +0700. 

I do not know a way to reliably launch external MIME handler from Emacs. 
All means I am aware of have some caveats.

  reply	other threads:[~2022-05-22  8:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22  4:37 [BUG] org-open-file immediately termininates when calling xdg-open that calls emacsclient [9.5.3 (release_9.5.3-508-ge268e4 @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
2022-05-22  8:13 ` Max Nikulin [this message]
2022-05-26 14:24   ` [BUG] org-open-file immediately termininates when calling xdg-open that calls emacsclient Ihor Radchenko
2022-05-26 16:14     ` Max Nikulin
2022-05-27  6:19       ` Ihor Radchenko
2022-05-27 12:03         ` Max Nikulin
2022-05-27 15:18           ` Ihor Radchenko
2022-06-02 17:04             ` [PATCH] org.el: Use `call-process' to launch external viewers (was: Re: [BUG] org-open-file immediately termininates when calling xdg-open that calls emacsclient) Max Nikulin
2022-07-24  5:51               ` Ihor Radchenko

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='t6crbm$ao9$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).