From: Stefan Kangas <stefan@marxist.se>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: 14473@debbugs.gnu.org
Subject: bug#14473: 24.3; emacs locks up when eshell attempts to display a dialog
Date: Tue, 8 Oct 2019 16:05:54 +0200 [thread overview]
Message-ID: <CADwFkmkOjY1iVkAcmsADPC1TU84FN1FGQ5k3-16dSE6szHrNjg@mail.gmail.com> (raw)
In-Reply-To: <8636g4crpc.fsf@phe.ftfl.ca>
Hi Joseph,
Joseph Mingrone <jrm@ftfl.ca> writes:
> >> It's still a problem (26.3 and 2019-09-15 master-branch build) in that the dialog is not displayed, but the Emacs process no longer consumes 100% CPU.
>
> > Thanks for reporting back.
>
> >> Here is a simple recipe to reproduce the problem. It assumes the FreeBSD ports tree is installed in the default location, which is /usr/ports.
>
> > Can you think of any way to reproduce this if you are not using
> > FreeBSD? Is there some particular command run by "make config" that
> > makes eshell freeze for example? It seems to me that very few Emacs
> > developers are using FreeBSD, and I personally don't have access to
> > any FreeBSD systems for debugging.
>
> I would guess any GNU/Linux command that also presents these curses
> dialogs would have problems. If you or any Emacs developer wants a
> FreeBSD shell account, I can provide one.
Thank you, noted. There are indeed (a small number of) open bugs
regarding *BSD systems, so I'm hoping that someone will take you up on
that offer. I might if I find the time.
> https://invisible-island.net/dialog/dialog-figures.html
>
> To be clear, it seems like less of a freeze now and more like an
> inability to display the dialog and the point becomes lost requiring
> users to kill eshell. So, it is much less severe of a problem than in
> the past.
Yes, after installing "dialog", I'm able to reproduce the problem on
my system using this command:
dialog --yesno "foobar" 10 50
In my case, hitting RET brings me back to the eshell prompt.
I think the problem is that eshell just doesn't support the control
characters that ncurses is producing, meaning that it has to switch to
term-mode to get that to work. Luckily, there are user options you
could set to make eshell do that automatically.
I created a Makefile with:
config:
dialog --yesno "foobar" 10 50
Using that Makefile, saying "make config" in eshell opens it in
term-mode automatically after I evaluate:
(add-to-list 'eshell-visual-subcommands '("make" "config"))
Does setting that option solve the issues you're seeing too?
If so, I think we can just write this up as a limitation in eshell,
and recommend users to configure this variable. Also see
eshell-visual-commands and eshell-visual-options for more.
One final thing, is running "make config" common on FreeBSD? I guess
it's part of the "ports" system that pretty much everyone uses,
including people on OpenBSD? If so, perhaps it would be worth
changing the default of eshell-visual-subcommands from nil to
something like:
(when (equal system-type 'berkeley-unix) '(("make" "config")))
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-10-08 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 17:19 bug#14473: 24.3; emacs locks up when eshell attempts to display a dialog Joseph Mingrone
2019-09-30 15:47 ` Stefan Kangas
2019-09-30 16:10 ` Eli Zaretskii
2019-10-03 15:48 ` Joseph Mingrone
2019-10-03 16:48 ` Stefan Kangas
2019-10-07 18:53 ` Joseph Mingrone
2019-10-08 14:05 ` Stefan Kangas [this message]
2019-10-14 17:53 ` Joseph Mingrone
2019-10-14 19:34 ` Stefan Kangas
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=CADwFkmkOjY1iVkAcmsADPC1TU84FN1FGQ5k3-16dSE6szHrNjg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=14473@debbugs.gnu.org \
--cc=jrm@ftfl.ca \
/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).