From nobody Sun Nov 02 01:48:56 2025 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 4czd183LNlz6FfZ5 for ; Sun, 02 Nov 2025 01:49:00 +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 (prime256v1) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E8" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4czd17536sz3KBv for ; Sun, 02 Nov 2025 01:48:59 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=iXT6pU98; 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 5A21mucj050484 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Sat, 1 Nov 2025 21:48:56 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1762048137; bh=vUEWgzbwuJA/vLFlOTAvwzfmBWYx/qQM1LOC4+OAhNA=; h=Date:Subject:To:References:From:In-Reply-To; b=iXT6pU984KxK9udYdwfHhKu8gpOfaViTRQ77lMouUTdh8tdtGo6IOGScDw1ybQcKa v3kqPQBKl0ZDyLuSAdOzNCGfJotWorTh3OyQOyxg0I9qwMTJdZbHKxZFtFZLdUzkDD vWG9hRa8YAM9br1hM5ekMAcXbU8CmF5ctqfvTcn3s6GchlsNDf2PXeEfEfv2RodK3Q 3TBS1yZYjyETMna6vnfMJBRM5DuooFGZrFuM75yEXcA4OOgrmN07C+iL84YMnz+ifu Rn/dJk4rgrLQyoRBjOH6RGXEa16f/JfQMn1M99ZbG1YYBWbOdtHnSvrkq/u+0dGnjr 9IjmYyNmuQ/Cg== Message-ID: <0c09c6fa-7071-4119-b97e-fc6d83f9fc3f@blastwave.org> Date: Sat, 1 Nov 2025 21:48:56 -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: a really big question : why not "^C" for a CTRL-C with default /bin/sh ? Content-Language: en-CA To: freebsd-current@freebsd.org References: <864EE1FC-1533-47D4-A395-C24F25269EE0@freebsd.org> <342c6a91-a8a1-483d-861e-8e8c6d79998f@blastwave.org> <9ea41e44-7160-40eb-9d80-b8bf13a7f396@mm.st> From: Dennis Clarke Organization: GENUNIX In-Reply-To: <9ea41e44-7160-40eb-9d80-b8bf13a7f396@mm.st> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 5A21mucj050484 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 [-3.70 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; R_SPF_ALLOW(-0.20)[+mx:c]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4czd17536sz3KBv On 11/1/25 21:22, cyric@mm.st wrote: > Dennis Clarke wrote: >> On 11/1/25 20:30, Michael Gmelin wrote: >>> >>> >>>> On 2. Nov 2025, at 00:34, Dennis Clarke wrote: >>>> >>>>  >>>> This is about as annoying as a small sharp stone stuck in a shoe : >>>> >> ... >>> Wasn‘t this always the default behavior in /bin/sh? >>> >> >> If it was and if it is then it is broken and always has been. >> >> No UNIX shell *ever* behaves this way in at least the last four decades. > > zsh does, ksh93 (illumos) does. > Those both hide the CTRL-C "^C" chars ? Oracle Solaris 11.4.81.193.1 Assembled April 2025 n$ n$ uname -a SunOS neptune 5.11 11.4.81.193.1 sun4v sparc sun4v non-virtualized n$ echo $SHELL /usr/xpg4/bin/sh n$ n$ ls la la la la la ^C n$ n$ which ksh93 /usr/bin/ksh93 n$ n$ ksh93 dclarke@neptune:~$ dclarke@neptune:~$ and then we have Dave Korn dclarke@neptune:~$ well look ... no CTRL-C ^C chars ? dclarke@neptune:~$ Nice one. I did not recall the ksh93 issue. Must be something in the stty options being set or unset. -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken