From: Eli Zaretskii <firstname.lastname@example.org>
To: Maxim Nikulin <email@example.com>
Subject: bug#12972: [PATCH] Avoid regression in mailcap-view-file similar to Bug#44824
Date: Sat, 03 Jul 2021 14:56:20 +0300 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (message from Maxim Nikulin on Sat, 3 Jul 2021 18:29:30 +0700)
> From: Maxim Nikulin <firstname.lastname@example.org>
> Date: Sat, 3 Jul 2021 18:29:30 +0700
> I am giving up with this issue.
That's too bad. I see no reason to give up, and I urge you to
> >> 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?
It isn't a church, but some kind of trust cannot harm.
> Previous time you were trying to convince me that unconditional 'pipe is
> perfectly safe when I was unsure concerning behavior on Windows.
It is indeed safe for Windows, because Emacs on Windows always uses
pipes (as PTYs are not available there).
My concern here is for systems other than Windows and other than those
where you saw the issue.
Your patch unconditionally assumes that every handler will immediately
exit, and that it doesn't care about the connection type with the
parent Emacs process, but that is not guaranteed to be true. What I'm
asking is to let some kind of "fire escape" for users who could be
adversely affected by this assumption. Ideally, some automatic
detection of the handlers that need pipes would be the best. If that
is not feasible, at least an option to control process-connection-type
would be enough.
> 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.
I explained the issue I have with unconditionally changing the
interface. I have explained it above again. I hope it is clear
> Finally, the patch touches month-old unreleased code, so I see no point
> to discuss that it is "incompatible".
Hmm... that's true. So I guess an option to use PTYs should be good
> 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.
Great, thanks. So I think it should be easy to adjust your patch to
have a variable that controls process-connection-type, and then it
could be installed.
next prev parent reply other threads:[~2021-07-03 11:57 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] ` <email@example.com>
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] ` <firstname.lastname@example.org>
2021-07-02 12:21 ` Maxim Nikulin
2021-07-02 12:37 ` Eli Zaretskii
[not found] ` <email@example.com>
2021-07-02 16:24 ` Maxim Nikulin
2021-07-02 17:28 ` Eli Zaretskii
[not found] ` <firstname.lastname@example.org>
2021-07-03 11:29 ` Maxim Nikulin
2021-07-03 11:56 ` Eli Zaretskii [this message]
[not found] ` <email@example.com>
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).