all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: 33193@debbugs.gnu.org
Subject: bug#33193: vim tests break terminal output
Date: Mon, 29 Oct 2018 15:46:35 +0100	[thread overview]
Message-ID: <87sh0ovmic.fsf@lassieur.org> (raw)

Hi,

While build vim tests, the terminal gets weird and its output is broken.

--8<---------------cut here---------------start------------->8---
<ng0> [...] some build (no idea which one, I'm in a long series of
      builds) just broke the output in a way that I'm only getting
      gibberish for the renmaining tail of buildlogs. iirc vim builds
      (specifically: the testsuite) would do something similar to your
      open terminal.
      [15:22]
*** mbuf (~Shakthi@45.251.33.79) has quit: Quit: Leaving  [15:24]
<ng0> "but what do I mean by gibberish?"
<ng0> well:
<ng0> ⎻▒▒⎽e ◆b┤☃┌d' ⎽┤cceeded ▒°├e⎼ 1↓3 ⎽ec⎺┼d⎽
<ng0>
      ├e⎽├/e┼±☃┼e/├e⎽├_⎻⎺⎺┌↓⎻≤::P⎺⎺┌E┴e┼├⎽Te⎽├::├e⎽├_c⎺┼┼ec├_⎺┼_⎽┤b⎽e─┤e┼├┌≤_⎼ec⎼e▒├ed
      PASSED [ 2▮%]
<ng0> etc
<roptat> oh yes, vim tests :/  [15:25]
<roptat> is that with guix build or guix package?  [15:26]
<ng0> build
<roptat> I haven't seen anything like that before and I'm not familia with UI
	 code  [15:27]
<ng0> wiht building vim you'd get no problems a while back. it would just
      continue building and only when builds finish make your terminal act
      funny
--8<---------------cut here---------------end--------------->8---

Cheers,
Clément

             reply	other threads:[~2018-10-29 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 14:46 Clément Lassieur [this message]
2018-11-03 13:58 ` bug#33193: vim tests break terminal output Ludovic Courtès
2018-11-12 18:12   ` Efraim Flashner
2020-06-11  4:05 ` Royce Strange

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=87sh0ovmic.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=33193@debbugs.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/guix.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.