From: Dmitry Antipov <dmantipov@yandex.ru>
To: emacs-devel@gnu.org
Subject: Some obsolete/unused/garbage things around window code?
Date: Tue, 10 Jan 2012 10:29:44 +0400 [thread overview]
Message-ID: <4F0BDAD8.6030201@yandex.ru> (raw)
1) last_mark_x and last_mark_y fields of 'struct window' aren't used anywhere
except initialization in make_window - is it reasonable to drop them at all?
2) What's an idea behind sequence_number of window objects? It's initialized
within make_window and make_parent_window, but used only in printing code.
Dmitry
next reply other threads:[~2012-01-10 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 6:29 Dmitry Antipov [this message]
2012-01-10 8:40 ` Some obsolete/unused/garbage things around window code? Eli Zaretskii
2012-01-10 10:20 ` martin rudalics
2012-01-10 11:00 ` Dmitry Antipov
2012-01-10 12:14 ` 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=4F0BDAD8.6030201@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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).