From: Noam Postavsky <npostavs@gmail.com>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30544@debbugs.gnu.org
Subject: bug#30544: 26.0.91; ansi-term duplicates 2 line zsh prompts any time windows change (maybe other times)
Date: Wed, 14 Mar 2018 21:06:00 -0400 [thread overview]
Message-ID: <87d106w3k7.fsf@gmail.com> (raw)
In-Reply-To: <CAHyO48x+Tda8o-+dmw1ZH6X0S==9Gb6i4Ad6z_mGzDDw9Cpu5w@mail.gmail.com> (Aaron Jensen's message of "Wed, 14 Mar 2018 17:54:22 -0700")
Aaron Jensen <aaronjensen@gmail.com> writes:
> On Wed, Mar 14, 2018 at 4:49 PM, Noam Postavsky <npostavs@gmail.com> wrote:
>> Odd. I have urxvt here, and it seems to be able to resize both width
>> and height without getting any duplicated prompts. Could it be that zsh
>> always repaints the prompt on a resize, but term.el (and iTerm for width
>> adjustments) don't put point where zsh is expecting after a resize?
>
> Just to be clear, you're seeing that w/ a two line prompt? This is
> really only an issue w/ a two line prompt for me.
Yes, I did PROMPT=$'one\ntwo' (by the way, I found I had to remove
'prompt adam1' from my .zshrc (the default setup puts it in), otherwise
setting PROMPT has no effect). I can reproduce the problem in term.el,
but urxvt doesn't have any problems no matter how I resize.
next prev parent reply other threads:[~2018-03-15 1:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 2:07 bug#30544: 26.0.91; ansi-term duplicates 2 line zsh prompts any time windows change (maybe other times) Aaron Jensen
2018-02-20 20:25 ` Glenn Morris
2018-03-14 15:59 ` Aaron Jensen
2018-03-14 17:34 ` Eli Zaretskii
2018-03-14 18:08 ` Aaron Jensen
2018-03-14 18:30 ` Eli Zaretskii
2018-03-14 20:25 ` Aaron Jensen
2018-03-14 23:49 ` Noam Postavsky
2018-03-15 0:54 ` Aaron Jensen
2018-03-15 1:06 ` Noam Postavsky [this message]
2018-03-15 1:33 ` Aaron Jensen
2018-03-15 1:42 ` Noam Postavsky
2018-03-15 2:41 ` Aaron Jensen
2018-04-02 2:39 ` Noam Postavsky
2018-04-02 5:46 ` Eli Zaretskii
2018-04-02 11:04 ` Noam Postavsky
2018-04-02 19:17 ` Aaron Jensen
2018-03-14 18:33 ` Glenn Morris
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=87d106w3k7.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=30544@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
/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).