From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 26898 invoked from network); 7 Oct 2022 18:38:20 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 7 Oct 2022 18:38:20 -0000 Received: from mail-vs1-f52.google.com ([209.85.217.52]) by 9front; Fri Oct 7 14:36:32 -0400 2022 Received: by mail-vs1-f52.google.com with SMTP id k6so3733066vsp.0 for <9front@9front.org>; Fri, 07 Oct 2022 11:36:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:references:in-reply-to:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=6g34VhvDu8uc70L8uBiEtL3pC1YkcsmhE9DO2hyAURA=; b=qSCPRnm3drIZH9zntm7uInmkNYIPKU8cfJ1RvGjDNScKaR/4+ZEDki7U0KIQAB5XBP CMPbkf9I798Q+Lscc2D4j+C+6uhBEe9WFels6vkE9y/URGWX4Cy8E0nKGe9Hjx61n4PG w6nv1niiWEBHnQzlihMhG0Pcd0R9kVGJcwJT6WBtb40rpwKKaP0VO0FT6weWggi3U4gc S5MuE4XKZ0RXNMmXuPqIjJhkdbnY1+KFDb6YAHnGqcIaR6N6L2iN+PtnIBOOJXkoe0Ng nOEQPt7U+GMNMCrYTXcdVKeoMhqFl1XKHX7/GHAXbUjp6/hK+27Nbq67cy0KysAhsIUR W9tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:references:in-reply-to:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6g34VhvDu8uc70L8uBiEtL3pC1YkcsmhE9DO2hyAURA=; b=V9zmsZE+lSSFOzY8RUXYnAHuYzYCgXkaTPCkylZmmgXa1rBroPU/Grkd4QZ9DYCBQ/ iH+CMO5oR0kYLZRnAacDOuhllTBhbPkL4NBSLe+6e75igHNpkb4Y1D5pkroP+NQdS/Af TaMk/KE9zlgAGnBfROrMoT+0PHB/hVHxXNUJaXG/eXVhHzMNu8iAmK9spLP0rvRkk42f VljXtUIeuNjtyCsNjf37BFJAF91bTNLQLbSquejQeXRSAc3RI5YejDq9/OGPs8Cv1kCd hMb/id0HqROj9psJ9NW44vsbLheCFa55UuKnGKh1dnoiIJnTCae/7q0X5Vjn1VRNpEGk P7tw== X-Gm-Message-State: ACrzQf1drCTmyCjUtMN5QY5RfldDiDTmOsB3sWn4H7EcirpQ5ZME3KUv cbkfMMy8EUtmNXXQRC0j76aKRTkqOLBHfatJdgBk4d/l X-Google-Smtp-Source: AMsMyM5QrnyJdzrWfO/E4Bw2bZ2dxUHz/XfZmSdX2girgRckCT1v9L9lCH/d1sxbXxKGFKBvbLE7qSyaYWxzpmtayo0= X-Received: by 2002:a67:fc5a:0:b0:3a6:a59f:5e96 with SMTP id p26-20020a67fc5a000000b003a6a59f5e96mr3779688vsq.52.1665167788863; Fri, 07 Oct 2022 11:36:28 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:2856:0:0:0:0:0 with HTTP; Fri, 7 Oct 2022 11:36:28 -0700 (PDT) In-Reply-To: <500E574000B68288364FAD993DCA8DAB@eigenstate.org> References: <1132EA054DF091104D293E57741F6906@mforney.org> <500E574000B68288364FAD993DCA8DAB@eigenstate.org> From: hiro <23hiro@gmail.com> Date: Fri, 7 Oct 2022 20:36:28 +0200 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: database hardware wrapper base Subject: Re: [9front] [PATCH] vt: fix home/end sequences in xterm mode Reply-To: 9front@9front.org Precedence: bulk > Also, on a related note -- an idea floated was to make vt compatible with > st instead of xterm, either via lifting their rendering code and porting > it, or via incremental changes. This would hopefully fix a bunch of quirks > and rendering issues we end up running into. i think vt isn't based on xterm. anyway, it was also demonstrated that some "bugs" people claimed to have found that made them prefer st (and it's slightly different bugs), came from using weird terminfo, too.