SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi everyone! I'm using Slackware 14.1 & have encountered a couple of issues with gvim that I haven't seen before on other systems.
1. When I open it from an xterm in KDE ("gvim $MY_FILE &"), gvim pops up in full screen mode, & I have to click on the widget to reduce it to a reasonable size. (Hmm. Maybe there's a flag I need to invoke at the command line?)
2. In a lot of the text I'm editing, I have extra long lines. When I add some text to one of those extra long lines, gvim decides to be "helpful" by breaking the left-most part of the line into 55-character long lines. Which means I have to go back & rejoin them.
I've spent a few hours reading thru the man page & online articles about how to customize gvim & .gvimrc, but I haven't seen anyone mention these two issues. I don't remember seeing this with gvim on other distros, so I have to wonder if they are caused by a compile flag -- & when I get to thinking that, I know I'm more likely missing something simple.
Any clues where I should look for an answer to either or both of these 2 issues?
Sounds like config issue. To see default settings, location of default rc files, and configure-time build arguments, do:
Code:
vim --version
and
Code:
gvim --version
in a terminal. The gvim one will require to be run in an xterm or some such like rxvt, st, etc...
I'm betting the rc files in /usr/share/vim/{vimrc,gvimrc} are the ones that will be the source for your answer(s).
The default rc files are well commented, so it shouldn't be to much effort to find your culprit.
Regarding the full-screen issue, I can't repro on Slack 14.1 + Xfce + xterm. Do you have a custom .vimrc/.gvimrc?
My setup is Slack 14.1 + KDE. It occurs when I launch from rxvt; when I launch from xterm, it doesn't happen. Interesting. (And no, I haven't created a custom .vimrc/.gvimrc. I haven't had the time to tweak my system very much due to the demands of Real Life, darn it. That's one of the reasons I went with Slack this time around.)
Quote:
Regarding the line breaks, you can put set fo-=t in ~/.vimrc or ~/.gvimrc.
--mancha
I'll investigate this & other suggestions. Thanks for the responses.
My setup is Slack 14.1 + KDE. It occurs when I launch from rxvt; when I launch from xterm, it doesn't happen. Interesting.
rxvt/gvim under kde does have some strange issues.
I have a ~/.[g]vimrc and all works fine except gvim, when launched from rxvt, gvim starts up behind rxvt. Since I have gotten konsole to a somewhat usable state so I use that now when in kde.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.