GNU nano - Bugs: bug #64320, something goes wrong when editing...
You are not allowed to post comments on this tracker with your current authentication level.
bug #64320: something goes wrong when editing on a Linux console in 4K on Slackware
Submitter: | David Chmelik <darwin> | ||
Submitted: | Tue 20 Jun 2023 07:34:16 AM UTC | ||
Severity: | 3 - Normal | Status: | Need Info |
Assigned to: | None | Open/Closed: | Open |
Jump to the original submission
Thu 06 Jul 2023 09:28:07 AM UTC, comment #16: |
David Chmelik <darwin> |
Thu 06 Jul 2023 09:04:14 AM UTC, comment #15: Another good test would be: to boot into another system (say Debian or Gentoo) and then chroot into the Slackware system. If the problem does not occur then, it shows that there is nothing wrong with nano and ncurses, but that somehow the Slackware kernel has an issue. Maybe the upstream kernel code has a bug and the way that Slackware configures and/or compiles it exposes the bug. Or maybe Slackware miscompile or misconfigures the kernel. |
Benno Schulenberg <bens>![]() |
Wed 05 Jul 2023 02:58:04 AM UTC, comment #14: Okay, I booted openSUSE, some Debian-/Ubuntu-based OSs, Fedora, Gentoo, and it didn't happen in those... this may just be a Slackware problem but I'm unsure. I can still test NetBSD, FreeBSD, DragonFlyBSD later... |
David Chmelik <darwin> |
Tue 04 Jul 2023 01:05:15 PM UTC, comment #13: You're still not providing a reproduction recipe. The phrase "just adding a few lines of unique letters and/or numbers to the bottom until all lines were filled, and then saved" is way too vague.
|
Benno Schulenberg <bens>![]() |
Tue 04 Jul 2023 03:33:31 AM UTC, comment #12: Well, I have the same kernel in Slackware and Gentoo so I think chrooting is fine. This has been happening since late Linux kernel 4, all through 5, and dozens in 6; probably 100+ kernels overall, so they're not really the problem.
|
David Chmelik <darwin> |
Mon 26 Jun 2023 09:40:44 AM UTC, comment #11: Chrooting is not a good way to try and reproduce the problem: you are actually using the kernel (and thus the console-driver code) from your base Slackware system. To really try and reproduce the issue on other systems, you need to boot into them.
|
Benno Schulenberg <bens>![]() |
Thu 22 Jun 2023 09:55:42 AM UTC, comment #10: I also tested for you in an X terminal and didn't have a problem in a chroot of one that had severe problems on a pure terminal. However, if I'm in X I uually use KDE Advanced Text Editor (KATE) and expect terminal text editors to work well on pure terminals. |
David Chmelik <darwin> |
Thu 22 Jun 2023 09:47:29 AM UTC, comment #9: On nano 7.2, I noticed similar/worse problems when I chrooted into Fedora, Gentoo, openSUSE (using defaults on all, and no ~/.nanorc) but not when chrooted in Debian-/Ubuntu-based.
|
David Chmelik <darwin> |
Thu 22 Jun 2023 12:20:55 AM UTC, comment #8: I don't run tabs command in any ~/.*rc nor ~/.*profile nor system initialization. |
David Chmelik <darwin> |
Wed 21 Jun 2023 01:55:23 PM UTC, comment #7: One thing to watch out for when trying to reproduce the issue: maybe it only happens when using nano after having used another program first, one which leaves the terminal in a subtly strange state.
|
Benno Schulenberg <bens>![]() |
Wed 21 Jun 2023 10:30:35 AM UTC, comment #6: The output of that command you asked for was just: TERM=linux. There was no $TAB, so it's default I guess.
|
David Chmelik <darwin> |
Wed 21 Jun 2023 09:43:56 AM UTC, comment #5: It would be great if you could test your editing also on the console of two other distros. If you can't reproduce the problem there, then it's something in Slackware. If you can reproduce it there, then we have a problem. But it will also mean that you know more or less how to reproduce the problem, and can tell me how.
|
Benno Schulenberg <bens>![]() |
Wed 21 Jun 2023 07:34:36 AM UTC, comment #4: I had a second typographical error; the stty size is 135 480.
|
David Chmelik <darwin> |
Wed 21 Jun 2023 07:33:24 AM UTC, comment #3: I had a typographical error; the stty size is 134 480. |
David Chmelik <darwin> |
Wed 21 Jun 2023 07:32:24 AM UTC, comment #2: Okay. As described, the tty command certainly shows a /dev/ttyn for some n=1 to 12, but I rarely if ever edit in 4K on a terminal emulator so don't know if the same problem happens there, but am willing to test xterms as well.
|
David Chmelik <darwin> |
Tue 20 Jun 2023 02:02:52 PM UTC, comment #1: Sorry, the description of your problem is too vague. What I understand is that something goes wrong when you edit on Linux console (a VT, 'tty' reports /dev/ttyn), but it works fine on any terminal emulator ('tty' reports /dev/pts/n), right?
|
Benno Schulenberg <bens>![]() |
Tue 20 Jun 2023 07:34:16 AM UTC, original submission:
Often I edit in nano on a 4K pure (non-X) terminal/shell, and the number of lines or something is handled wrong. Some many not be counted near the bottom, so text starts being offset. You might end up deleting stuff above a line on the wrong line, and you won't even see that displayed right until you exit and reopen. If you saved, you may find the file was messed up because of the wrong count and text offset being not displayed right. I haven't figured out the exact details but something went wrong. It works fine to edit on pure terminals in 1600x1200 and 1080p. When editing in 4K I can only save small sections at a time if done carefully/right before I have to exit and restart to see/do any more. |
David Chmelik <darwin> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-07-06 | bens | Summary | something goes wrong when editing on a Linux console in 4K | ![]() |
something goes wrong when editing on a Linux console in 4K on Slackware |
2023-06-21 | darwin | Attached File | - | ![]() |
Added nanorc, #54851 |
2023-06-20 | bens | Status | None | ![]() |
Need Info |
Summary | nano can't handle editing in terminals/shells in 4K | ![]() |
something goes wrong when editing on a Linux console in 4K |
You changed it too soon. I was unable to reproduce the bug on Slackware the same way I recently tested on other GNU/Linux. I have to do a different sort of test, again. It's hard to explain. I just know if you fill up the screen with lines, and move it around, and save, and maybe do it again, something will go wrong, and most likely on Gentoo and others too. Slackware doesn't compile the kernel wrong because it just compiles the kernel the way it is: no patches.