unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: On removing sequence_number from window structure
Date: Fri, 08 Feb 2013 10:17:30 +0200	[thread overview]
Message-ID: <87obfvz0bp.fsf@mail.jurta.org> (raw)
In-Reply-To: <510CD342.8090600@gmx.at> (martin rudalics's message of "Sat, 02 Feb 2013 09:50:10 +0100")

> 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.



  parent reply	other threads:[~2013-02-08  8:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02  8:50 On removing sequence_number from window structure martin rudalics
2013-02-02 17:32 ` Dmitry Antipov
2013-02-02 17:50   ` martin rudalics
2013-02-08  8:17 ` Juri Linkov [this message]
2013-02-08  9:55   ` Eli Zaretskii
2013-02-08  9:59   ` martin rudalics
2013-02-08 15:17     ` Stefan Monnier
2013-02-08 15:33       ` Drew Adams
2013-02-09  0:30     ` Juri Linkov
2013-02-09  9:21       ` martin rudalics
2013-02-09 14:20         ` Stefan Monnier
2013-02-09 17:08           ` martin rudalics
2013-02-10  9:57             ` Juri Linkov
2013-02-10 13:33               ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obfvz0bp.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).