| Summary: | Enabling Vim improvements | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Mathias Schneuwly <mathias> |
| Component: | vim | Assignee: | Michael Tremer <michael.tremer> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Balancing | ||
| Priority: | - Unknown - | CC: | michael.tremer |
| Version: | 2 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
| Attachments: |
Possible solution
Files from /usr/share/vim of the build system. Patch to activate "set ruler" |
||
Thank you for that RFE. It's totally fine to open bugs. At least for *real* enhancements and not just dumping a list of wishes. I tested the change and it finally fixes what I have been searching for a long time. It did not figure it has been this. As vim in IPFire 3.x is working fine with these settings, I would like you to have a look over the other settings and check if we should add them too: http://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=vim/vimrc;h=f8b6666dc8e326a5f19ee30f01b9a751ad38712b;hb=HEAD In case you approve this file, I will apply it for Core Update 57. Hi Michael I already played with the option syntax on, but I was not able to get it running! Vim in IPFire 2.X requires a file called syntax.vim in "/usr/share/vim/syntax". Without this file, vim prints always an error before opening a file... I tried also to copy all syntax files from my Ubuntu machine to IPFire, but without success. So if you don't have a working solution I would propose to remove the line syntax on. About the background issue; What happens if you are using putty with font color black, does then putty still shows the output? Created attachment 16 [details]
Files from /usr/share/vim of the build system.
I just uploaded a tarball with all the files in /usr/share/vim of the build system. It is not shipped with the default IPFire image. There are also the syntax files included. I got the background lines from Fedora so I thought it would be good to adapt this setting too. You will have the same appearance of vim on both systems. Yeah works great! Can you please add these files to IPFire 2.X? This highly improves the usability of Vim! Yeah works great! Can you please add these files to IPFire 2.X? This highly improves the usability of Vim! One more... set ruler enables a simple status line which shows the current position and also a line percentage. Changes applied in http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=d02a7f9d050e97714e151bb93c8f67448b743d5e Please check again when a testing version of the next core update is available. Thank you very much for you help so far. > Please check again when a testing version of the next core update is available. I'm waiting for you :-) > Thank you very much for you help so far. You're welcome! It's a pleasure to support my favorite open source project! The Core Update has been pushed to the testing tree. Please test. Created attachment 21 [details] Patch to activate "set ruler" Checked the vimrc of the testing core 57 and I'm quite happy. One little thing is missing and this is the option "set ruler" mentioned in comment 7. Also without this option, vim looks really nice now! Nevertheless, I created a patch to add this option to vimrc. It's your choice to apply it or not. In my point of view, I don't see any negative impact with this option. Woops. I completely forget about that change. So it won't make it for this core update. It is committed for the next one. http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=968d4ea400651b48672390956ae856a9f62deba0 (It still needs to be added to the filelist.) The core update is released, so this bug can be closed. http://www.ipfire.org/news/ipfire-2-11-core-update-57-released |
Created attachment 15 [details] Possible solution Vim supports many improvements in contrast to the standard vi. Nevertheless, they are turned off in the version provided by IPFire. Is it possible to enable them by default? One possible solution could be using a vimrc file in /etc which enables these improvements. I added the possible solution to this "Change request". By the way, is there any other way to provide a change request than to open a bug report? Perhaps a new severity class called "Change request"?