unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Cc: rms@gnu.org, schwab@suse.de, teirllm@dms.auburn.edu,
	deego@glue.umd.edu, emacs-devel@gnu.org
Subject: Re: Redisplay bug
Date: 22 Aug 2002 23:21:17 +0200	[thread overview]
Message-ID: <sgdy9ayh9o2.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <5xlm6yzp3b.fsf@kfs2.cua.dk>

storm@cua.dk (Kim F. Storm) writes:

> storm@cua.dk (Kim F. Storm) writes:
> 
> > Richard Stallman <rms@gnu.org> writes:
> > 
> > > I keep meaning to work on debugging this, but keep being too busy.
> > > I would be really grateful if you would try it.  It surely relates
> > > to one of the places I changed a call to make_cursor_line_fully_visible.
> > > The first question is, which one?
> > 
> > Ok, I'll look into this over the next week or so.
> 
> I've spent quite some time trying to track this bugger down....
> 
> I found a specific part of Richard's change to xdisp.c which seems
> to cause the redisplay problem, so I have reverted that change.
> 
> But now the redisplay again has a habit of leaving the cursor on
> partially visible lines at the top or bottom of the window (which
> I believe is what Richard tried to fix).  

There seems to be some confusion as to what Richard was trying to
implement with his change to xdisp.c which is causing the redisplay
bug.  It is my understanding that he was trying to implement the
following.

  http://mail.gnu.org/pipermail/emacs-devel/2002-June/009864.html

Richard, if I'm mistaken, please correct me.  Sorry for the noise in
that case.

Regards,

  Lute.

-- 
Lute Kamstra  <Lute.Kamstra@cwi.nl>
CWI  department PNA4
Room M233  phone (+31) 20 592 4214
[Echelon material: codes benelux Defcon]

  reply	other threads:[~2002-08-22 21:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18 21:14 Redisplay bug Andreas Schwab
2002-08-18 21:19 ` D. Goel
2002-08-18 21:45   ` Luc Teirlinck
2002-08-18 21:52     ` Andreas Schwab
2002-08-18 22:09       ` Andreas Schwab
2002-08-18 23:40       ` Kim F. Storm
2002-08-19 18:39         ` Richard Stallman
2002-08-20  0:07           ` Kim F. Storm
2002-08-22 19:10             ` Kim F. Storm
2002-08-22 21:21               ` Lute Kamstra [this message]
2002-08-22 23:17                 ` Kim F. Storm
2002-08-24 12:11               ` Richard Stallman
2002-08-25 23:10                 ` Kim F. Storm
2002-08-26  5:04                   ` Eli Zaretskii
2002-08-26 21:51                     ` Richard Stallman
2002-08-31 16:58                   ` Richard Stallman
2002-09-02  6:24                     ` Juanma Barranquero
2002-09-02  6:40                       ` Miles Bader
2002-09-02  7:06                         ` Juanma Barranquero
2002-08-18 22:49 ` Simon Josefsson

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=sgdy9ayh9o2.fsf@occarina.pna.cwi.nl \
    --to=lute.kamstra@cwi.nl \
    --cc=deego@glue.umd.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=schwab@suse.de \
    --cc=teirllm@dms.auburn.edu \
    /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).