Bug 2166860
| Summary: | Mouse click no longer position cursor in shell command line in XTerm after activation with control sequence | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matouš Jan Fialka <mjf> |
| Component: | xterm | Assignee: | Tomas Korbar <tkorbar> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | dickey, mjf, tkorbar |
| Target Milestone: | --- | Keywords: | Desktop, Regression, UserStory |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | xterm-378-3.fc38 xterm-378-3.fc36 xterm-378-3.fc37 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-02-08 09:48:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Matouš Jan Fialka
2023-02-03 09:02:12 UTC
The 2001-2006 codes are xterm features for bracketed-paste and readline.
The readline ones were not well-documented, as mentioned here:
https://invisible-island.net/xterm/xterm-paste64.html#background
Fedora 18 would be early 2013, while Fedora 36 was mid-2022.
In between that, bash (readline) added support for bracketed-paste - in 2016:
https://invisible-island.net/xterm/xterm-paste64.html#by_shells
You could be seeing bash interfering, which can be disabled
bind 'set enable-bracketed-paste off'
However, except for the 2004 (bracketed paste),
the others have been a configure option of xterm since 2005,
which was never enabled by default (because of the documentation issue).
You can see the configure option here
https://github.com/ThomasDickey/xterm-snapshots/blame/master/configure.in#L846
looking at the variable enable_readline_mouse
Assuming that
https://src.fedoraproject.org/rpms/xterm
reflects the history of xterm in Fedora, I don't see that the option was ever used.
Given all of that, I suppose the xterm executable in Fedora 18 was recompiled to provide the readline feature.
Hello. Thank you for your detailed response... and I must say you are completely right! :-) Well, I feel ashamed. I still have the original disk image, so I inspected it and realized that I must had recompiled XTerm. I found it in my $HOME/bin directory that used to take precedence to the system-wide directories using the $PATH setting (and forgot about it completely, but the reason to re-compile it in $HOME may had been exactly the mouse support for the readline). So, as a workaround for now I will certainly recompile XTerm again and hopefully get the feature back (and try to remember doing so this time). ;-) But from point of view as a user much better way would be to (finally) enable the readline mouse support in the RPM package to let people to switch it on freely if they need it without the need of recompiling. The feature is really extremely helpful in some situations. Do you think this would be possible? With regards, -- mjf yes - I added a to-do item to document the feature (in ctlseqs.ms of course). If it's documented, changing the configure-script default would fix this issue. Hello. That would be splendid! I'm looking forward to it. With regards, -- mjf Confirmation in [1] (see the accepted answer). References: - [1] https://unix.stackexchange.com/questions/733933/mouse-click-stopped-positioning-cursor-in-shell-readline-in-xterm-after-upgrad Is there any chance that the we will see the re-configured XTerm in F36 as update for the XTerm package? With regards, -- mjf F37 appears to be the current "stable" version, with F38 being branched off right now. It's a configure option which the packager (not I) could easily apply in the spec-file at any point. See https://src.fedoraproject.org/rpms/xterm for the history and maintainers. But for F36, I'd suppose that it isn't important enough for someone to apply. Hi guys, this seems useful and from my point of view presents little to no chance for regression, so i will commit changes to the package and create updates for rawhide, f37 and f36. FEDORA-2023-39d89a37de has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-39d89a37de FEDORA-2023-39d89a37de has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-385b0f0af5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-385b0f0af5 FEDORA-2023-d7cb43f7f0 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d7cb43f7f0 FEDORA-2023-d7cb43f7f0 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d7cb43f7f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d7cb43f7f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-385b0f0af5 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-385b0f0af5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-385b0f0af5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Hello Tomas, I confirm that https://bodhi.fedoraproject.org/updates/FEDORA-2023-d7cb43f7f0 solves the issue for me on F36. Thank you! -- mjf FEDORA-2023-d7cb43f7f0 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-385b0f0af5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |