From nobody Mon Sep 16 20:17:19 2024 X-Original-To: freebsd-current@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 4X6x6F36sPz5WsD3 for ; Mon, 16 Sep 2024 20:17:25 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X6x6D3KVPz3wmd for ; Mon, 16 Sep 2024 20:17:24 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=OnREncCj; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 48GKHJAu069171 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Mon, 16 Sep 2024 16:17:21 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1726517841; bh=WHieNW1FHD884kwVj/URPW590D4OajxHKfqWOvd3Jsk=; h=Date:Subject:To:References:From:In-Reply-To; b=OnREncCjyK0t9mda+f/gQKeQt6LntlJ4b43K7NosNUFa0Se8UkZ5+L2lPBbObLha5 43HhI7K4UwGxrQ9xDzBj/kd1h94Hm/2ZS2jFcP+MfsoCXpp7ZGiMUh+tmyGQ8nICIA mJjoBqFWXLPTCwqxgc+8bSSsDOvyOFk6BWaiyosEzN9T3KvnaG79KDVT1jwKmRdFnz vA7VDASfjOuR6hyB+FV38O1wBYGlPDRQbXiZWx+SPRLeT7Qw7wDOwEj90AjgkC7Rpd CvTQy92LmeGtmkBYzYgLSUArPX7aOeQP28SQAJa9I37rxCqkC2wOZj+l14i2NdHPxg //e7Jq1nA08og== Message-ID: Date: Mon, 16 Sep 2024 16:17:19 -0400 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: change in /usr/bin/bc with CTRL-d no longer exit Content-Language: en-CA To: freebsd-current@freebsd.org References: <1e614684-1cba-ef01-34dc-d9300db2d927@macktronics.com> <20240916141330.995C554A@slippy.cwsent.com> From: Dennis Clarke Organization: GENUNIX In-Reply-To: <20240916141330.995C554A@slippy.cwsent.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 48GKHJAu069171 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.69 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4X6x6D3KVPz3wmd On 9/16/24 10:13, Cy Schubert wrote: > In message , void writes: >> On Sun, Sep 15, 2024 at 03:16:46PM -0500, Dan Mack wrote: >>> On 14.1 and prior, a CTRL-d will exit a bc session. >>> >>> Today I noticed that on 3 different 15-CURRENT systems, it appears to >>> be ignored. Works fine otherwise and I can exit the bc session with >>> the 'quit' command okay. >>> >>> I re-tested this on the system console on fresh login just to rule out >>> any terminal madness. >>> >>> Here's a paste of what I see: >>> >>> https://tpaste.us/VYya >>> >>> I did a fresh install of 14.1 and it works as it did previously. >>> >>> No biggie, just wondering if anyone else on -CURRENT can confirm/deny >>> this change on their system. >> >> [void@vm5 ~ ] uname -KU >> 1400504 1400504 >> [void@vm5 ~ ] echo 2+2 | bc -l >> 4 >> >> [void@vm3 ~ ] uname -KU >> 1500023 1500023 >> [void@vm3 ~ ] echo 2+2 | bc -l >> 4 > > Of course the above works because the regression only affects tty users. Here is some paint on the bikeshed : enceladus# uname -apKU FreeBSD enceladus 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n271918-d7c87526b1c3-dirty: Mon Sep 2 09:55:54 UTC 2024 root@enceladus:/usr/obj/usr/src/riscv.riscv64/sys/GENERIC riscv riscv64 1500023 1500023 enceladus# enceladus# bc -lq scale=36 a(1)*4 3.141592653589793238462643383279502884 ^D ^C interrupt (type "quit" to exit) ready for more input quit enceladus# Yep. That is borked. > bc(1) now ignores EOF on the terminal while the above still works. You can > circumvent this by putting "export BC_TTY_MODE=0" into your .profile. The > side effect is that line editing will no longer work. > > I will have to try that. However why would bc change at all? -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken