From nobody Sat Jun 3 17:47:48 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QYS5J0Xfsz4ZG3k for ; Sat, 3 Jun 2023 17:48:04 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QYS5H47W1z3NfP for ; Sat, 3 Jun 2023 17:48:03 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-96fab30d1e1so689773666b.0 for ; Sat, 03 Jun 2023 10:48:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685814480; x=1688406480; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=t8lv3PZmfYD7rPAyCuYd1JYWzk3Ufjvpwko7ExVlvt8=; b=HIItE/GkhWJqkDf6Fn4WMKl9l9mgKTc1T/ChhWT1ALZk4Py60Sb9BRN7m0P8WU7cZs qZOVyxh0sKMGbndgnHWRvAdYUevd51kX16/FwASJfDe3AWRAwuYsn5j8D9JJsdY70NMg 5R03OURqJroWzWzTjBd5Z/Cdx7nek59+3u5+cMMqRLBQr6SaIi1AnHZHRSYD9IpCBRA8 VHwvJMYABXT11Cem8XyKNm/F1V8oiB0GtaDj3CWCyuaMRjRFkQg29meV4xvaPZ1NdNo0 wr4pv1UpmQRrknGK5vFWN9C86GSoJwyeo0zBksp1L4ZnQljC/mfv/UdUhuHinoIEncJh OlOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685814480; x=1688406480; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=t8lv3PZmfYD7rPAyCuYd1JYWzk3Ufjvpwko7ExVlvt8=; b=LsQyBlRVMakYc+BQmiPk1VCWyoOSu2Cbf4Y4+JItkUT+Dr48BZGmUb6l6rKVN2DcDo Qm+4sJc0fJ84TmNRDstDiSED+o4cIS/ULsTW/LnEnsl0+akIu7JzNtHJb7w0P+42ultf efLEboUCd3hEf8H1qLAnDzwHvcDgBT1YTwbJwDbyDU6k4BbhxU+fAVD56bvX8JOoMRiM zGFqrR7QR5RFZ/tOOe4PFFIRtk671nV6vUs+yrCy9yd1E4B2SqidpFqHgICNbLUZlZ4+ 1vlf5LwnMNJqm3t+cubbiJckfy0M6UKYz050YYNQLhM4wL+P0pyfsdPox2k/MAJuopPs UyWg== X-Gm-Message-State: AC+VfDz+zopKl9LbhpwaWbZwLB93twUsuS6uEZyPZUVdW6zUO1FxbPr3 eSWHjWeWSy9uo14sXw2q0crI2dQNmofgk2hJOXU= X-Google-Smtp-Source: ACHHUZ6/jT/stgLYL48qNNiiGeBcT8Lz4JgFZYOBEJqgoXzPl8K2jZ4UKlsE5PmZTt9uH5CxmPt57NbopI23s6qfrzs= X-Received: by 2002:a17:907:3da1:b0:969:e993:6ff0 with SMTP id he33-20020a1709073da100b00969e9936ff0mr1861889ejc.25.1685814480039; Sat, 03 Jun 2023 10:48:00 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <20230603120016.803642b5e7d4c56b4725e7cc@sohara.org> In-Reply-To: From: Aryeh Friedman Date: Sat, 3 Jun 2023 13:47:48 -0400 Message-ID: Subject: Re: totally OT: How to prevent Linux guest from clearing screen entering/leaving vim To: Holger Sebert Cc: questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QYS5H47W1z3NfP X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sat, Jun 3, 2023 at 10:36=E2=80=AFAM Holger Sebert wrote: > > > > On 6/3/23 14:34, Aryeh Friedman wrote: > > On Sat, Jun 3, 2023 at 7:00=E2=80=AFAM Steve O'Hara-Smith wrote: > >> > >> On Sat, 3 Jun 2023 06:40:21 -0400 > >> Aryeh Friedman wrote: > >> > >>> 1) The terminal clears (thus ruining any possibility of scrolling bac= k > >>> to stuff I want to reference) when I enter and leave vi.... i.e. > >>> command line stuff is not visible inside vim and vim is not visible > >>> (with no amount of scrolling back) if I am in command line mode.. . > >>> this makes fixing compiler errors ***VERY*** annoying since I have an > >>> increased cognitive load from having to remember the line number and > >>> the error... It also make cutting and pasting next to impossible > >> > >> This one I also hate. and kn ow how to fix :) add this to > >> your .vimrc > >> > >> :set t_te=3D > > > > Still doesn't completely solve it because once I leave vim (or am in > > vim) I still can not scroll back before the start of the vim session > > (i.e. still can't see the compiler [javac] errors).... it does help in > > being able to cut and paste stuff from vim to other places but not the > > other way around > > > > I think the (mis-)feature you are experiencing is called > =E2=80=9Calternate screen=E2=80=9D. May this here helps? Never would of found that searching on my own (chatGPT also had no idea) > > https://www.shallowsky.com/linux/noaltscreen.html Now my question: what *MORON* thought this "feature" was a good idea?!?!? --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org