Re: On removing sequence_number from window structure

[Juri Linkov]

> It's much simpler to think of windows in terms of sequence numbers
> than in terms of pointers.

Are window sequence numbers necessary from the user's point of view?

For frames simple sequence numbers are necessary on terminals
where creating new frames increments the frame number starting from 1
to give frame names like "F1", "F2", "F3" displayed on the modeline.
It's important for the users to know which frame is current by number.
Is the same true for windows?

For frames these sequence numbers are included in frame names.
Should windows have names that could include sequence numbers
like "W1", "W2", "W3"?

Please address these questions as a user since as a developer
you can add something like this for debugging purposes:

(set-window-parameter nil 'window-number (incf global-window-counter))

to a hook run during window creation.