unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Vinicius Jose Latorre <viniciusjl@ig.com.br>
Cc: emacs-pretest-bug@gnu.org, rms@gnu.org
Subject: Re: 23.0.50; Display bug with vline.el and viper
Date: Wed, 23 Jan 2008 23:37:19 +0100	[thread overview]
Message-ID: <4797C19F.40000@gmail.com> (raw)
In-Reply-To: <4797C8AC.1080602@ig.com.br>

Vinicius Jose Latorre wrote:
> 
>> Strange. I just tested again with the latest vline.el from EmacsWiki 
>> and inserted (redisplay t) as the last thing in vline-show. Same bug.
>>
>> When I tested I had (window-height) => 4, ie 3 lines are shown, and 
>> (window-height) => 46. I had vline.el in the buffer. Cursor at left 
>> side (is it column 0 or 1?;-). Just hold down arrow-down.
>>
>> It does not get past the row starting with
>>
>>  ;; Author: Taiki SUGAWARA <buzz.taiki@gmail.com>
> 
> The vline.el that I'm using is attached to this email.
> 
> Please, check if we are using the same file and patch.
> 
> I'm using:
> 
> GNU Emacs 23.0.50.2 (i686-pc-linux-gnu, GTK+ Version 2.12.1)
> of 2008-01-12 on debian-hillux
> 
> These are the steps I've done:
> 
> 
> 1. emacs -Q vline.el
> 
> 2. shrink Emacs until display 27 columns;
>    (So you have a lot of long lines)
> 
> 3. M-x eval-buffer RET
> 
> 4. M-x vline-mode RET
> 
> 5. C-n (several, well, you can hold the key pressed)
>     It's all right until here.
> 
> 6. shrink Emacs until display 3 lines;
> 
> 7. C-n (several, again, you can hold the key pressed)
>    Continue all right.
> 
> 
> Without the patch, it has some problems.

Hm, you placed (redisplay t) inside the (save-excursion ...) form. That 
cures the bug I reported, but it gives other very strange bugs. Maximize 
the window and then press up and down arrows. Instead of just moving the 
point at least up arrow much of the time scrolls the window.

  reply	other threads:[~2008-01-23 22:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 10:30 23.0.50; Display bug with vline.el and viper Lennart Borgman (gmail)
2008-01-22 22:30 ` Richard Stallman
2008-01-22 23:02   ` Drew Adams
2008-01-22 23:24   ` Lennart Borgman (gmail)
2008-01-23  0:45     ` Vinicius Jose Latorre
2008-01-23  0:13       ` Lennart Borgman (gmail)
2008-01-23  0:17         ` Lennart Borgman (gmail)
2008-01-23 16:20       ` Richard Stallman
2008-01-23 16:31         ` Lennart Borgman (gmail)
2008-01-23 19:49           ` Vinicius Jose Latorre
2008-01-23 19:06             ` Lennart Borgman (gmail)
2008-01-23 23:07               ` Vinicius Jose Latorre
2008-01-23 22:37                 ` Lennart Borgman (gmail) [this message]
2008-01-24  0:48                   ` Vinicius Jose Latorre
2008-02-01 15:31 ` Lennart Borgman (gmail)
2008-02-27 23:18 ` Lennart Borgman (gmail)

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=4797C19F.40000@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=rms@gnu.org \
    --cc=viniciusjl@ig.com.br \
    /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).