Bug 208391 - misc/mc SUBSHELL not working with /bin/sh
Summary: misc/mc SUBSHELL not working with /bin/sh
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Ben Woods
URL: https://www.midnight-commander.org/ti...
Depends on:
Reported: 2016-03-30 04:15 UTC by gja822
Modified: 2020-10-06 13:55 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (woodsb02)

Add pkg-message explaining the issue (1.72 KB, patch)
2020-10-06 13:55 UTC, Mateusz Piotrowski
0mp: maintainer-approval?
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description gja822 2016-03-30 04:15:18 UTC
SUBSHELL option (and usability) do not work for my ordinary users with /bin/sh login shell, either option chosen or not during port build process. This behaviour was noted for ages. And I even used to it. For my root (with csh login shel) SUBSHELL worked fine (and I use it).
But from previous (or last) upgrade, misc/mc if built with chosen SUBSHELL option do not even start for users with /bin/sh as default login shells.
Error is:

common.c: unimplemented subshell type 1
read (subshell_pty...): No error: 0 (0)
Comment 1 Ben Woods freebsd_committer 2016-06-26 11:56:37 UTC
I have reported this problem to the upstream mc project team here:
Comment 2 Patrick McMunn 2020-09-02 20:25:07 UTC
This is a longstanding bug. I would suggest that the subshell build option be disabled by default or that, at the very least, an informational message be emitted that a user either needs to use the -u option to start or that the user's default shell should be changed, if a different shell will cause it to work.
Comment 3 Mateusz Piotrowski freebsd_committer 2020-10-06 13:42:41 UTC
It looks like the ticket is still pending: https://midnight-commander.org/ticket/373

Interestingly, Debian ash and BusyBox ash are now supported: https://github.com/MidnightCommander/mc/commit/f596c916a42a0868897b3314e557b0a82df37017
Comment 4 Mateusz Piotrowski freebsd_committer 2020-10-06 13:55:14 UTC
Created attachment 218560 [details]
Add pkg-message explaining the issue

Would you mind if I commit the attached pkg-message to explain the problem to our users?