Thread: Re: [cream] can't open many files with tabs
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Steve H. <dig...@da...> - 2007-08-28 14:25:32
|
From: Elias Pschernig <elias users sf.net>, Tue, August 28, 2007 10:03 am > > how can I get more than about 10 tabs with tabbed mode? (I'm > assuming this is a setting I can change somewhere.) Cream displays complete filenames in tabs without shortening. If the sum of the filenames exceeds the window width, a small pair of buttons [<][>] appears at the end of the tab line to go to those not shown. But Vim imposes a default limitation of 10 tabs with the &tabpagemax option. This is imposed upon :tab ball used by Cream's tab refresh function. I suppose Cream could bump this up, although I'm not sure what a reasonable limit should be. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Steve H. <dig...@da...> - 2007-08-28 17:01:38
|
From: Elias Pschernig <elias users sf.net>, Tue, Aug 28, 2007 11:27am > On Tue, 2007-08-28 at 07:25 -0700, Steve Hall wrote: > > From: Elias Pschernig <elias users sf.net>, Tue, Aug 28, 2007 10:03am > > > > > > how can I get more than about 10 tabs with tabbed mode? > > > > But Vim imposes a default limitation of 10 tabs with the &tabpagemax > > option. > > Thanks, I added this to cream-user.vim: > > set tabpagemax=100 > > But still, when I start with more than 10 files, I get this: > > http://allefant.googlepages.com/Screenshot-Vim.png It looks like the error relates to there not being enough room for all the windows based on the number of vertical scroll bars. Vim relates tabs and windows somehow, see :help ball. Also, how are you opening multiple windows, via command line? > (btw., is there a way to re-display and copy&paste error messages?) :messages > Anyway, I assume cream-user.vim was the wrong file to place this? If you're passing in multiple filename arguments via command line, I think the issue is coordinating those and Cream autocmds. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Elias P. <el...@us...> - 2007-08-28 17:24:43
|
On Tue, 2007-08-28 at 10:01 -0700, Steve Hall wrote: > It looks like the error relates to there not being enough room for all > the windows based on the number of vertical scroll bars. Vim relates > tabs and windows somehow, see :help ball. Hm. Sounds too complicated for me, all I want is one file per tab. > Also, how are you opening multiple windows, via command line? > > > (btw., is there a way to re-display and copy&paste error messages?) > > :messages Thanks, I must remember that. > > Anyway, I assume cream-user.vim was the wrong file to place this? > > If you're passing in multiple filename arguments via command line, I > think the issue is coordinating those and Cream autocmds. > Yes, they are all passed via command line. I can "work around" this for now by not using tabs at all (with 100 files they aren't really useful anyway) - but when editing only a few files, I'm missing them. And in case I get that error messages, also the selection over the Window menu won't work any longer - so can't just ignore it when opening many files. -- Elias Pschernig <el...@us...> |
From: Steve H. <dig...@da...> - 2007-08-28 18:12:39
|
From: Elias Pschernig <elias users sf.net>, Tue, August 28, 2007 1:24 pm > On Tue, 2007-08-28 at 10:01 -0700, Steve Hall wrote: > > > > If you're passing in multiple filename arguments via command line, I > > think the issue is coordinating those and Cream autocmds. > > Yes, they are all passed via command line. I can "work around" this > for now by not using tabs at all (with 100 files they aren't really > useful anyway) - but when editing only a few files, I'm missing > them. And in case I get that error messages, also the selection over > the Window menu won't work any longer - so can't just ignore it when > opening many files. The original &tabpagemax option default is probably logical then. Did you mean you still saw the error with the default value or just that no more than 10 tabs were indicated? Cream is not really designed to manage 100 open files at a time. I'm not sure how anyone can edit more than about 10 or so, but surely 20 is a practical design limit? -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Elias P. <el...@us...> - 2007-08-28 18:19:28
|
On Tue, 2007-08-28 at 11:12 -0700, Steve Hall wrote: > > > > Yes, they are all passed via command line. I can "work around" this > > for now by not using tabs at all (with 100 files they aren't really > > useful anyway) - but when editing only a few files, I'm missing > > them. And in case I get that error messages, also the selection over > > the Window menu won't work any longer - so can't just ignore it when > > opening many files. > > The original &tabpagemax option default is probably logical then. Did > you mean you still saw the error with the default value or just that > no more than 10 tabs were indicated? The option made no difference at all - if I have tabs enabled, and want to open many files, it breaks. > Cream is not really designed to manage 100 open files at a time. I'm > not sure how anyone can edit more than about 10 or so, but surely 20 > is a practical design limit? > Well, I like to have all files of a project in the Window menu, for quick navigation, so even > 100 would make sense. Think "cream src/*.py src/*/*.py" :P It seems to work well enough without tabs.. but as I said, while I wouldn't use tabs when doing the above, I still like to keep tabs enabled in general, for cases where I have < 10 files and use the Window menu.. -- Elias Pschernig <el...@us...> |
From: Steve H. <dig...@da...> - 2007-08-29 10:45:12
|
On Tue, 2007-08-28 at 20:19 +0200, Elias Pschernig wrote: > On Tue, 2007-08-28 at 11:12 -0700, Steve Hall wrote: > > > > Did you mean you still saw the error with the default value or > > just that no more than 10 tabs were indicated? > > The option made no difference at all - if I have tabs enabled, and want > to open many files, it breaks. Ok, I'll have to add this to the ToDo list. > > Cream is not really designed to manage 100 open files at a time. > > I'm not sure how anyone can edit more than about 10 or so, but > > surely 20 is a practical design limit? > > Well, I like to have all files of a project in the Window menu, for > quick navigation, so even > 100 would make sense. Think "cream > src/*.py src/*/*.py" :P I guess I've gotten into the habit of leaving open the file manager to do this. Then opening any file is just a simple right-click, V (Windows) or right-click, pick "Cream" in GNOME. Not that opening 100 files in a text editor is necessarily wrong, I just know there has to be some limitations in Cream since it is a script environment rather than a binary one. -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net |
From: Elias P. <el...@us...> - 2007-08-28 15:27:44
|
On Tue, 2007-08-28 at 07:25 -0700, Steve Hall wrote: > From: Elias Pschernig <elias users sf.net>, Tue, August 28, 2007 10:03 am > > > > how can I get more than about 10 tabs with tabbed mode? (I'm > > assuming this is a setting I can change somewhere.) > > Cream displays complete filenames in tabs without shortening. If the > sum of the filenames exceeds the window width, a small pair of buttons > [<][>] appears at the end of the tab line to go to those not shown. > > But Vim imposes a default limitation of 10 tabs with the &tabpagemax > option. This is imposed upon :tab ball used by Cream's tab refresh > function. I suppose Cream could bump this up, although I'm not sure > what a reasonable limit should be. > Thanks, I added this to cream-user.vim: set tabpagemax=100 But still, when I start with more than 10 files, I get this: http://allefant.googlepages.com/Screenshot-Vim.png (btw., is there a way to re-display and copy&paste error messages?) Anyway, I assume cream-user.vim was the wrong file to place this? -- Elias Pschernig <el...@us...> |