From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30544@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
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 11:08:32 -0700 [thread overview]
Message-ID: <CAHyO48xiHxvM8udz3brk9pT6Tr=0D24gKGF-_TqsYvL3zJYT9g@mail.gmail.com> (raw)
In-Reply-To: <83vadyr278.fsf@gnu.org>
On Wed, Mar 14, 2018 at 10:34 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Aaron Jensen <aaronjensen@gmail.com>
>> Date: Wed, 14 Mar 2018 08:59:55 -0700
>> Cc: Noam Postavsky <npostavs@gmail.com>
>>
>> I saw that you've been doing some term.el work recently. Do you have
>> an idea what could be causing this?
>
> See Glenn's message with bisection: as expected, this is due to the
> telling the shell to resize its window.
I don't know if this was directed at Noam or myself, but one
interesting thing is that iTerm also has artifacts when resizing, but
only if resizing to be horizontally smaller. term.el appears to have
artifacts every time any size change is made (horizontal or vertical).
next prev parent reply other threads:[~2018-03-14 18:08 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHyO48xiHxvM8udz3brk9pT6Tr=0D24gKGF-_TqsYvL3zJYT9g@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=30544@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@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 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.