From owner-freebsd-questions@freebsd.org Fri May 15 21:18:24 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AFD922D9E0D for ; Fri, 15 May 2020 21:18:24 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 49P1V75bbTz4TCC for ; Fri, 15 May 2020 21:18:23 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id E98074E740; Fri, 15 May 2020 14:18:22 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-questions@freebsd.org Subject: (character) Conversion error (in vi) ? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <67157.1589577502.1@segfault.tristatelogic.com> Date: Fri, 15 May 2020 14:18:22 -0700 Message-ID: <67158.1589577502@segfault.tristatelogic.com> X-Rspamd-Queue-Id: 49P1V75bbTz4TCC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com X-Spamd-Result: default: False [-4.37 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[tristatelogic.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-3.07)[ip: (-8.06), ipnet: 69.62.128.0/17(-4.03), asn: 14051(-3.21), country: US(-0.05)]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; MIME_TRACE(0.00)[0:+] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2020 21:18:24 -0000 Ever since my last system upgrade, some months ago now, vi has been behaving badly/differently. Sometimes it gets a bee in its bonnet over something that, I guess, it is trying to interpret as a (malformed?) Unicode or utf-8 character or something, and in such cases it refuses to allow me to edit the file in question. How can I return it to the old/prior behavior, under which it could tolerate any old sequence of eight bit bytes without having a hissy fit? There must be some option to tell it "don't do that", yes? (For the life of me, I don't know why the old/prior behavior wasn't maintained as the default behavior. But I wonder the same thing about a *lot* of different software "upgrades".)