From: Maxim Nikulin <firstname.lastname@example.org>
Subject: bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824
Date: Sat, 3 Jul 2021 18:29:30 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
I am giving up with this issue.
My summary. New function `mailcap-view-file' has a problem similar to
Bug#44824 (kde-open5 and "gio open" called directly or through xdg-open
are unreliable in Emacs, I consider it as fixed in Org mode) that was
reported by several users and refused by developers as not reproducible
at first. I tried my best to draw attention to this problem and then to
suggest a change that fixes the obscure problem and improves error
handling. I am unaware of any real negative consequences of my patch. It
is up to Emacs developers to leave the new bug as is or to fix it in a
way they like
On 03/07/2021 00:28, Eli Zaretskii wrote:
>> From: Maxim Nikulin Date: Fri, 2 Jul 2021 23:24:23 +0700
>> On 02/07/2021 19:37, Eli Zaretskii wrote:
>>>> From: Maxim Nikulin Date: Fri, 2 Jul 2021 19:21:55 +0700
>>>>> And with other handlers, this could be an
>>>>> incompatible behavior change if the handler behaves differently when
>>>>> its standard handles are connected to a pipe rather than a terminal
>>>> Example of such handler, please.
>>> Why do you need one?
>> Because of I can not imagine such case for mailcap handler in Emacs yet
>> and, accordingly to you, "this could be an incompatible behavior change".
> You don't need to imagine it, you just need to trust me that I know
> what I'm talking about: it would be an incompatible change.
Is it a kind of Church of Emacs that I have to just believe in you?
Previous time you were trying to convince me that unconditional 'pipe is
perfectly safe when I was unsure concerning behavior on Windows.
You prefer to keep reasons of your objections unveiled. I see no issue
with the patch. It can be by a few lines shorter but the price is worse
user experience. I have no idea how to move further.
Finally, the patch touches month-old unreleased code, so I see no point
to discuss that it is "incompatible".
P.S. It was my fault to use `make-process' in Org since the function is
not available in Emacs-24. I'm sorry for that incompatibility.
next prev parent reply other threads:[~2021-07-03 11:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F3C1A7E58B2441F7A674239043AC031A@us.oracle.com>
2021-06-01 6:56 ` bug#12972: 24.3.50; Move `org-open-file' and associated code out of Org mode Lars Ingebrigtsen
[not found] ` <firstname.lastname@example.org>
2021-06-02 16:20 ` Maxim Nikulin
2021-07-01 17:01 ` bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824 Maxim Nikulin
2021-07-01 18:38 ` Eli Zaretskii
[not found] ` <email@example.com>
2021-07-02 12:21 ` Maxim Nikulin
2021-07-02 12:37 ` Eli Zaretskii
[not found] ` <firstname.lastname@example.org>
2021-07-02 16:24 ` Maxim Nikulin
2021-07-02 17:28 ` Eli Zaretskii
[not found] ` <email@example.com>
2021-07-03 11:29 ` Maxim Nikulin [this message]
2021-07-03 11:56 ` Eli Zaretskii
[not found] ` <firstname.lastname@example.org>
2021-07-04 13:37 ` Maxim Nikulin
2021-07-04 13:49 ` Eli Zaretskii
2021-07-05 13:12 ` Maxim Nikulin
2021-07-05 15:23 ` Eli Zaretskii
2021-07-30 12:01 ` bug#12972: 24.3.50; Move `org-open-file' and associated code out of Org mode Lars Ingebrigtsen
2021-07-30 12:24 ` Maxim Nikulin
2021-07-30 12:42 ` Lars Ingebrigtsen
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 \
* 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).