-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Console saving does not work in FreeBSD #3292
Comments
$ LC_MESSAGES=C mc -F
[System data]
[User data]
$ mc --configure-options
|
same issue(freebsd 10, mc 4.8.13), very annoying |
Are you sure this ever worked?
According to my best knowledge, although I might be wrong:
I suspect either a broken terminal emulator, or a misunderstanding of what's supposed to work and wishing for something that never worked.
Could you please provide exact details about the OS and terminal in front of which you're sitting and ssh'ing to FreeBSD? |
|
As for me, it worked all years before on all oses i've ever seen. Including any versions of freebsd. And now it stops working after update of mc to 4.8.13. |
Hmmm, this might indeed be a problem with mc.
It would be nice to see the result 'typescript' files of a run of mc inside 'script', both with working and nonworking mc. The files contain tons of hard-to-understand stuff, so it'd help if otherwise everything (e.g. directories) would be the exact same. It would be nice to do the minimal possible stuff inside mc. That is:
Run 'script', run 'mc', press Ctrl-O, press Ctrl-O again, quit mc, quit script (e.g. Ctrl-D), save the 'typescript' file.
Beware that the file might contain sensible information (list of filenames), preferably do it with empty directories on both panels.
Comparing the two typescript files (with mc-4.8.11 vs. mc-4.8.13) might reveal what's the problem.
In the mean time, if you could do a 'git bisect' to catch the malicious commit, that'd be even better :)
(Unfortunately I don't have FreeBSD, that's why I'm asking for this.) |
old mc |
new mc |
Sorry, but I can't find the differences between typescript files attached
The sequence was the same on both machines:
ctrl-o
enter (here were receive ls output) |
old mc with timestamping |
new mc with timestamping |
I've recorded all the same again, now with timestamping (script -r) |
(FreeBSD script's timing seems to be incompatible with Linux's, I don't have an option to play it back with timing :( I can do a slowcat on the raw version.)
The buggy version never prints [?47h (nor [?1047h or [?1049h), meaning it does not switch to the alternate screen.
You could also verify this by first producing more than a screenful of update (e.g. ls -l /etc) and then starting mc. With the correct mc you shouldn't be able to use the terminal's scrollbar to scroll back (when mc's panels are on). With the buggy one you'll be able to scroll back.
Looks like subshell support is not being used. (I should have thought of it at the beginning.) What does "mc --version" say about subshell?
Are you using FreeBSD packages of mc, or compiling yourself? If the former, it _could_ be a bug in FreeBSD's way of packaging it, maybe they changed something. If the latter, is 4.8.12 buggy for you too, as for the original reporter? Could you maybe please do a git bisect between .11 and .12?
What shell are you using? (There were zsh changes in .12). |
root@dedic53 [~/aa]# mc --version |
I've tried mc from ports first (compiling myself). When noticed the bug, reinstalled it from packages - nothing changed. |
I've tried zsh and bash - all the same |
"You could also verify this by first producing more than a screenful of update (e.g. ls -l /etc) and then starting mc. With the correct mc you shouldn't be able to use the terminal's scrollbar to scroll back (when mc's panels are on). With the buggy one you'll be able to scroll back."
Confirmed, things happened exactly as you describe it. Terminal's scrollbar stays usable for buggy mc, and disappears for old one. |
Let's play with portdowngrade utility =) |
At last I've found the reason.
New version:
I've replaced this new patch with old one (from 4.8.12) and build 4.8.13.
Found the solution, but have no idea what to do with this information :( |
[This comment might not be relevant seeing your most recent comment, but posting it anyway, might be useful in the future]
Replying to maxout:
Strange, this differs from the original reporter's observation.
Could you please locate the faulty change:
git clone git://github.com/MidnightCommander/mc.git
and then repeat this in a loop:
each step of the loop will take a few minutes, and you'll have around 7 steps. At the end it'll tell you the faulty mc commit. |
(Note: the "-" sign (removal of line) was converted to a bullet in your patch.)
FreeBSD's change of the patch definitely looks broken, they've modified a condition in a certain way when leaving the alternate screen, but dropped the same modification of the condition when entering it. It's their fault, please notify them.
On the other hand, we should understand why such patch is needed at all, and modify mainstream mc so that freebsd doesn't need a patch. |
Just for information, here is a bugreport: |
Important
This issue was migrated from Trac:
hempalex
egmont@….com
(@egmontkob)After update to 4.8.13 from freebsd ports (misc/mc) console saving stopped to work.
I'm tried FreeBSD 8.4, 9.1, 10.0 on about 10 different servers.
Steps to reproduce
mc -v output:
GNU Midnight Commander 4.8.13
Built with GLib 2.36.3
Using the S-Lang library with terminfo database
With builtin Editor
With subshell support as default
With support for background operations
With mouse support on xterm
With support for X11 events
With internationalization support
With multiple codepages support
Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, fish, smbfs
Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;
Strange enough, but rolling back to 4.8.12 does not solved problem!
Additionally I tried to remove a .cache/.config/.local directories, but no luck...
Note
Original attachments:
maxout
(maxout.mail@….com) onNov 21, 2014 at 6:12 UTC
maxout
(maxout.mail@….com) onNov 21, 2014 at 6:13 UTC
maxout
(maxout.mail@….com) onNov 21, 2014 at 6:38 UTC
maxout
(maxout.mail@….com) onNov 21, 2014 at 6:38 UTC
The text was updated successfully, but these errors were encountered: