Bug 1653853
| Summary: | Cursor disappears after gvim window vertical split | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | charles harris <charlesr.harris> |
| Component: | vim | Assignee: | Karsten Hopp <karsten> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 29 | CC: | charlesr.harris, gchamoul, karsten, zdohnal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-27 22:37:04 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
charles harris
2018-11-27 18:24:21 UTC
Hi Charles, there is new version of Vim in the updates testing, would you mind checking it if it helps? Does not fix the problem VIM - Vi IMproved 8.1 (2018 May 18, compiled Nov 27 2018 11:41:09) Included patches: 1-549 Can you reproduce the issue when you run gvim as: $ gvim -u NONE -U NONE -N -i NONE ? The cursor is back, but the theme is gone It is expected - this way we can check if the error is in Vim itself or in used scripts - a plugin/viminfo/vimrc/gvimrc files. The answer is - there is a problem in used scripts or your setup. You can check: http://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5 Would you mind investigating the issue according the link and share the results? I was able to fix this by changing the number of lines in my .vimrc file. I had lines set to 59 to get full screen, changing it to 49 fixed the problem. This is with Fedora 30, which seems to have the testing version you previously suggested. I'm not sure what changed in between vim versions, the 59 used to work... Oops, that only worked for opening two files on startup with `-O`. With a single file and splitting the screen manually, lines set in .vimrc needs to be 42, using 43 lines (which is not full screen), shows me 49 numbered lines and the cursor problem. I can set the lines manually once gvim is running and things work fine, so there seems to be something wrong with the way setting lines in the .vimrc is handled. Also, starting with fewer lines, then maximizing followed by vertical splitting causes a problem, but vertical splitting followed by maximizing works. Hopes this helps :) This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |