zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Zle redisplay bug in pws-24
Date: Sun, 27 Jun 1999 09:38:15 +0000	[thread overview]
Message-ID: <990627093815.ZM9764@candle.brasslantern.com> (raw)

It's probably present in other versions too ... yup, 3.0.6-pre-5 has it ..

It happens with a multiline buffer, and appears to have something to do with
killing a line that is exactly one character shorter than the width of the
terminal.  Here's how I reproduced it:

Start with a prompt string that's ten characters long (e.g. "zagzig<2> " was
mine at the time).  In netscape, go to article 6850 in the zsh-workers
archive; drag-select the patch at the end (from "---" through "sleep(1);").
Back in your zsh terminal, start a here-document ("patch -p0 -R <<'EOF'")
and then paste in the text.  Finish with EOF and hit return.  Note that
the patch fails because of whitespace differences (sigh).  Hit ctrl-P to
call back the here-document and move up to edit the "patch" line.  Decide
that's not what you want to do after all and idly begin tapping ctrl-K
until you see:

zagzig<2>             while ((ttpgrp = gettygrp()) != -1 && ttpgrp != mypgrp) {
                sleep(1);

EOF

The cursor at this moment is right after the prompt.  Hit ctrl-K again and
you see (cursor represented by an underscore):

          _
zagzig<7>       sleep(1);                                                      
                
EOF

Whoops, the prompt moved down to the "sleep(1);" line, but the cursor is
still on the line above it!

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


             reply	other threads:[~1999-06-27  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-27  9:38 Bart Schaefer [this message]
1999-06-27 20:17 ` Geoff Wing

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=990627093815.ZM9764@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).