From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: dmantipov@yandex.ru, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: 'struct window' cleanup #2
Date: Tue, 26 Jun 2012 18:32:34 +0300 [thread overview]
Message-ID: <83a9zq9jhp.fsf@gnu.org> (raw)
In-Reply-To: <4FE9643C.1090201@gmx.at>
> Date: Tue, 26 Jun 2012 09:26:52 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> Emacs development discussions <emacs-devel@gnu.org>
>
> >> How about window_end_pos, window_end_vpos and window_end_valid?
> >
> > xdisp.c assigns w->buffer to w->window_end_valid, so it may be tricky.
> > I suppose window_end_valid may be a bitfield; so, NILP
> > (W->window_end_valid)
> > becomes !W->window_end_valid, EQ (w->window_end_valid, w->buffer)
> > becomes W->window_end_valid, etc.
>
> Indeed. Looks like a hack to detect whether the window still shows the
> same buffer.
Why a "hack"? Lisp object are good precisely for this reason: that
you can give them values of different types of object.
> Anyway, window_end_pos and window_end_vpos are the more
> promising candidates (if Eli agrees).
I don't object. But if we think that Lisp integers cause any
significant slowdown during GC, we could special-case them in
mark_object, because that is a no-op for integers. That would be less
work and less potential bugs.
> Can you see whether the part
>
> /* When splitting windows or for new windows, it happens that
> redisplay is called with a nil window_end_vpos or one being
> larger than the window. This should really be fixed in
> window.c. I don't have this on my list, now, so we do
> approximately the same as the old redisplay code. --gerd. */
> && INTEGERP (w->window_end_vpos)
>
> in xdisp.c still makes sense?
No, there's no code anymore that sets it to nil.
next prev parent reply other threads:[~2012-06-26 15:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 8:56 'struct window' cleanup #2 Dmitry Antipov
2012-06-25 14:22 ` John Wiegley
2012-06-25 14:42 ` Dmitry Antipov
2012-06-25 14:27 ` Paul Eggert
2012-06-25 14:53 ` Stefan Monnier
2012-06-25 16:30 ` Dmitry Antipov
2012-06-25 16:35 ` martin rudalics
2012-06-25 16:49 ` Dmitry Antipov
2012-06-26 7:26 ` martin rudalics
2012-06-26 9:06 ` Dmitry Antipov
2012-06-26 15:37 ` Eli Zaretskii
2012-06-26 15:32 ` Eli Zaretskii [this message]
2012-06-26 16:49 ` Dmitry Antipov
2012-06-26 17:12 ` Eli Zaretskii
2012-06-27 0:42 ` Stefan Monnier
2012-06-27 3:03 ` Eli Zaretskii
2012-06-27 7:10 ` 'struct window' cleanup #3 Dmitry Antipov
2012-06-27 13:32 ` Stefan Monnier
2012-06-27 17:37 ` Eli Zaretskii
2012-06-27 17:24 ` Eli Zaretskii
2012-06-27 17:59 ` Dmitry Antipov
2012-06-27 19:36 ` Eli Zaretskii
2012-07-01 15:05 ` Dmitry Antipov
2012-07-01 15:42 ` Andreas Schwab
2012-06-28 12:51 ` Dmitry Antipov
2012-06-27 7:06 ` 'struct window' cleanup #2 martin rudalics
2012-06-27 16:59 ` Eli Zaretskii
2012-06-25 16:39 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a9zq9jhp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.