[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tabs are ready? -> Let us give a definition of tabs.

From: Nix
Subject: Re: Tabs are ready? -> Let us give a definition of tabs.
Date: Sat, 11 Feb 2012 14:16:32 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.93 (gnu/linux)

On 9 Feb 2012, Alin Soare stated:

>> The way I'm picturing it, the tab's internal state consists of four pieces
>>> of data: a title, a window (or possibly window configuration), a function
>>> that's called when it becomes active, and another function that's called
>>> when it becomes inactive.  That *seems* like it's meeting all your
>>> requirements, as I've understood them.
> The title must also a tab-local variable.

I've already pointed out that true tab-local variables would have nasty
consequences for critical code in Emacs, confusing the semantics of
variable lookup. Look at the sad history of frame-local variables and
their interaction with buffer-local variables for an indication of the
subtle problems you'll be inviting. (The problem is simple: if a buffer
and its frame *both* declare a variable to be 'local', which takes
precedence? There is probably code that depends on *each* taking
precedence, so any answer will be wrong.)

Now a list of 'tab parameters', like frame parameters, which have to be
explicitly looked up when needed, is more likely to be accweptable.

NULL && (void)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]