From: Stephen Berman <Stephen.Berman@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Display text property problem
Date: Thu, 14 Jun 2007 15:38:13 +0200 [thread overview]
Message-ID: <87ir9qpsfu.fsf@escher.local.home> (raw)
In-Reply-To: 89CCD019-6CBE-4446-B5E2-9124A5EB841C@Web.DE
On Thu, 14 Jun 2007 14:50:11 +0200 Peter Dyballa <Peter_Dyballa@Web.DE> wrote:
> Right. Going to describe it as detailed as possible. I am doing my
> tests in ``Text´´ mode buffers.
Thanks for the detailed feedback!
> Terminal
> ========
>
> After step 3 the cursor is at line #2 column #5 (beginning of word
> test). In mode-line the position is tracked as (1,70), where it was
> before. In the echo are a ``nil´´ has appeared.
>
> After evaluating step 4 nothing changes, except: the echo area now
> contains: ``End of buffer´´.
I can only reproduce this (your last sentence), if I do `M-:
(scroll-up)' (same as pressing the NEXT (Page Down) key). When I
instead do `M-: (scroll-up 1), I get what I reported in my OP (but I
neglected to add that, with emacs -Q -nw, after step 4 the cursor is
now at column 83 instead of 70).
> X client
> ========
>
> After step 3 the cursor is at line #2 column #5 (beginning of word
> test). In mode-line the position is tracked as (1,70), where it was
> before. In the echo are a ``nil´´ has appeared.
>
> After evaluating step 4 the first line disappears, and so do the
> spaces before the first word ``test´´ in line #2. Mode-line has not
> changed, the echo area contains a ``nil´´. When I now press up GNU
> Emacs makes a quak sound (indicating some error has occurred) and I
> see both lines complete. The cursor is in the first line first
> column. Mode-line shows (1,0).
OK, this is just what I originally described, except that I hear the
beep only if I press PageUp a second time, which is just Emacs
signalling that the invocation of scroll-up was a no-op, since the
beginning of the buffer is already visible.
> *Messages* contains:
>
> nil
> Auto-saving...
> nil
>
>
> On Mac OS X 10.4.9, and no GTK+!
Maybe there's a difference in the terminal version under Mac OSX, if
you really did (scroll-up 1) and not (scroll-up). Otherwise, you've
confirmed the display bug, at least under X. So now it remains to
figure out how to fix it...
Steve Berman
next prev parent reply other threads:[~2007-06-14 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 10:00 Display text property problem Stephen Berman
2007-06-14 10:24 ` Peter Dyballa
2007-06-14 11:10 ` Stephen Berman
2007-06-14 11:48 ` Peter Dyballa
2007-06-14 12:06 ` Stephen Berman
2007-06-14 12:50 ` Peter Dyballa
2007-06-14 13:38 ` Stephen Berman [this message]
2007-06-14 14:55 ` Peter Dyballa
2007-06-14 14:58 ` Peter Dyballa
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=87ir9qpsfu.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=help-gnu-emacs@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 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.