From: Maxim Nikulin <m.a.nikulin@gmail.com>
To: 44824@debbugs.gnu.org
Subject: bug#44824: 27.1; Org export as pdf and open file does not open it
Date: Thu, 28 Jan 2021 23:10:14 +0700 [thread overview]
Message-ID: <3c4f6517-7cfa-bbeb-0eae-e9bc2a7f972d@gmail.com> (raw)
In-Reply-To: <108399a5-66ad-eee6-572b-b3f2181e4e6c__47986.5006914892$1611843550$gmane$org@gmail.com>
On 28/01/2021 18:31, gbiotti@gmail.com wrote:
>
> If I try in eshell buffer 'xdg-open /tmp/test.pdf && sleep 3' my cursor
> blinks
> with the Okular icon for a few seconds and then nothing happens.
If I correctly get what you describe as "blinks", it could last for some
time after process failure. On the other hand I am surprised that no
other diagnostics is shown as a KDE dialog or as an error message in the
eshell buffer. In the case of eshell, it is likely another problem, not
killing handler with SIGHUP due to instantly closed pty.
What happens if you run the following commands in the Emacs *eshell
buffer* (with an existing PDF file, of course)? In particular I am
interested in output appeared in the buffer.
1. okular /tmp/test.pdf
2. kde-open5 /tmp/test.pdf
3. sh -x /usr/bin/xdg-open /tmp/test.pdf
I'm almost sure that okular is configured as the handler, but just to
confirm it:
4. xdg-mime query default application/pdf
I assume that PDF file is a valid one (not corrupted, not empty, not
accessible due to file permissions, etc.) since okular is able to report
such problems.
You could also attach to emacs process with strace, try to launch
handler, kill strace, and inspect log file which processes are spawned
("execve" lines) and their exit codes. Run strace from ordinary terminal
(not from emacs) with proper process ID:
strace -o /tmp/emacs.strace -f -s 128 -tt -p PID_OF_EMACS_PROCESS
next prev parent reply other threads:[~2021-01-28 16:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFbX=UpDN9XtTr3osTC6B=V0trvatayw5WF0gMjGWAWfQQkAXg@mail.gmail.com>
[not found] ` <f395c79a-c3e3-52c7-3fbb-608e94868e8e@gmail.com>
2021-01-27 3:36 ` bug#44824: 27.1; Org export as pdf and open file does not open it Lars Ingebrigtsen
2021-01-27 8:33 ` gbiotti
2021-01-28 3:02 ` Lars Ingebrigtsen
2021-01-28 11:20 ` gbiotti
2021-01-28 11:31 ` gbiotti
2021-01-29 4:51 ` Lars Ingebrigtsen
2021-01-29 6:59 ` Geraldo Biotti
2021-01-30 6:09 ` Lars Ingebrigtsen
2021-01-30 7:50 ` Geraldo Biotti
2021-01-30 8:42 ` Eli Zaretskii
2021-01-30 13:31 ` Maxim Nikulin
2021-01-30 13:49 ` Eli Zaretskii
2021-01-30 15:58 ` Maxim Nikulin
2021-01-30 16:28 ` Eli Zaretskii
2021-01-31 11:15 ` Maxim Nikulin
2021-01-31 11:37 ` tomas
2021-01-31 15:05 ` Eli Zaretskii
2021-01-31 15:17 ` Andreas Schwab
2021-01-31 15:34 ` Eli Zaretskii
2021-01-31 15:21 ` Lars Ingebrigtsen
2021-01-31 15:57 ` Maxim Nikulin
2021-01-31 16:33 ` Eli Zaretskii
2021-01-31 17:07 ` Maxim Nikulin
[not found] ` <83o8h56p7o.fsf__8661.17158891342$1612110869$gmane$org@gnu.org>
2021-02-18 12:56 ` [PATCH] org.el: Avoid xdg-open silent failure Maxim Nikulin
2021-02-18 14:48 ` bug#44824: " Eli Zaretskii
[not found] ` <83a6s15t51.fsf__31631.6350990505$1613659778$gmane$org@gnu.org>
2021-02-19 12:29 ` Maxim Nikulin
2021-02-19 14:54 ` Eli Zaretskii
2021-02-19 16:45 ` Maxim Nikulin
2021-03-19 3:50 ` Kyle Meyer
2021-03-20 15:45 ` Maxim Nikulin
2021-03-21 15:01 ` Kyle Meyer
2021-01-30 16:39 ` bug#44824: 27.1; Org export as pdf and open file does not open it gbiotti
2021-01-30 18:50 ` Bhavin Gandhi
2021-01-31 7:17 ` Lars Ingebrigtsen
2021-01-31 7:39 ` Tim Cross
2021-01-31 9:09 ` tomas
[not found] ` <108399a5-66ad-eee6-572b-b3f2181e4e6c__47986.5006914892$1611843550$gmane$org@gmail.com>
2021-01-28 16:10 ` Maxim Nikulin [this message]
[not found] ` <87y2gfcape.fsf_-___1545.58022493205$1611718675$gmane$org@gnus.org>
2021-01-27 12:14 ` Maxim Nikulin
2021-01-27 13:33 ` Maxim Nikulin
[not found] ` <0f4437bc-3e40-fe47-d6e7-d33c2fb7965a__46427.8968678386$1611759102$gmane$org@gmail.com>
2021-01-27 16:21 ` Glenn Morris
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c4f6517-7cfa-bbeb-0eae-e9bc2a7f972d@gmail.com \
--to=m.a.nikulin@gmail.com \
--cc=44824@debbugs.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/org-mode.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).