Re: Fwd: Tabs for console.

[Stefan Monnier <monnier@iro.umontreal.ca>]

> True. If you keep the variables, you need not to wonder about the order.
> With variables you can keep buffer2 on the first position of :data, and
> buffer2 on the second, or vice versa. Or you can conceive :data as an
> obarray, as I wanted initially.

The :data solution still allows that: the data can be a defstruct
(hence named slots), a has-table, or an obarray if you so wish.

>> >> >> So it will need to change.  But does `make-tab' create a new tab or
>> >> >> a tabbar?  If a tab, then I don't understand any more why the
>> init-code
>> >> >> is needed.
>> >> > Yes, tabs must be separate from frames, and keep indepedent of every
>> >> > other thing.  A frame/window can subscribe to tabs, and show them when
>> >> > it is activated/etc.
>> >> That doesn't answer my question: does `make-tab' create a new tab or
>> >> a tabbar?
>> > Your idea of (make-tab-bar PLACE) was very good. The tab bar existed
>> without
>> > initialization inside a frame.
>> 
>> Not sure why you don't want to answer the question directly, but IIUC
>> you're indirectly here saying that makr-tab indeed creates a tab rather
>> than a tabbar.
> For me, make-tab adds an element to the list f->tab_bar_items, and
> display_tab_bar will display the :name of that element on tab-bar.

That's called "adds a tab to the tabbar".


        Stefan