On 26/04/11 00:07, sc wrote:
On Monday, April 25, 2011 13:07:55 you wrote:
- in Console mode, since the crash happens at GUI startup
vim ~/.vimrc
no this was blowing vim up too, and leaving a bolixed konsole
in its wake -- i didn't remember -u NORC off the top of my
head so i grabbed kwrite -- given a second to think i might
have grabbed mc -- it's got a nice internal editor, but kwrite
was handy so i used it
sc
Oh? Well then it must be something different: I was seeing this only at
GUI startup, and in fact the gdb breakpoint at gdk_x_error was triggered
after an empty gvim screen had come up... let me see...
Ah, I see: this "set lines=99999 columns=99999" line was in the "true"
part of an "if has('gui_running')" so I could not get it in console mode
-- I don't change a console terminal's size by a statement in the vimrc;
for some terminals it works, for others not, for others part of the time
depending on the values used; see the warning near the middle of :help
'columns' and at the bottom of :help 'lines'
Best regards,
Tony.
--
The notion of a "record" is an obsolete remnant of the days of the
80-column card.
-- Dennis M. Ritchie
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
