> > This makes no sense alone ; it is in connection with the same tab .  This
> > is just other event for the same tab.
>
> What are the events you envision for one and the same tab ...
>
>
Almost the same events as the events the notebook widget of GTK responds.

Quite so, one cannot attach all events of gtk+.

In this case, the 'response' must be defined as a lambda.

What is to be done: to insert C code , minimally, that execute the events
when needed.

For console only, I did myself. For GTK and motif it should be even easier.



>
> >> In which sense do your tabs differ from menu or toolbar elements?  You
> >> can easily add a menu element to save the current window configuration
> >> or pick one of a list of earlier saved configurations to restore that.
> >>
> >>
> > You cannot at all define menu or toolbar buttons which respond to
> standard
> > events , at which tab widgets shoud respond.
>
> ... and what is a "standard event" in this context?  And why can a
> toolbar button not react to such a standard event in the same way?


Initialize tab, hide tab, show tab, kill tab, at least.





>
> >>From what you say, it is worth seeing how to define the tabs as
> > tab-objects, as I said, such that they can be buffue-local when desired.
>
> And window-local.  I think that for two different windows the sets of
> buffers you might want to switch to would differ according to the
> buffers shown in the respective window before.



Ya, right. A tab structure should be added alone , and a ponter to a such
tab struct must be present in every structure of frame, buffer, window.