From nobody Sun Nov 02 16:03:31 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 4czzzH58S8z6G0N8 for ; Sun, 02 Nov 2025 16:03:39 +0000 (UTC) (envelope-from cyric@mm.st) Received: from fhigh-a3-smtp.messagingengine.com (fhigh-a3-smtp.messagingengine.com [103.168.172.154]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4czzzG6H7sz43WB for ; Sun, 02 Nov 2025 16:03:38 +0000 (UTC) (envelope-from cyric@mm.st) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mm.st header.s=fm3 header.b=J86XC3BZ; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=0dirvX3H; dmarc=pass (policy=none) header.from=mm.st; spf=pass (mx1.freebsd.org: domain of cyric@mm.st designates 103.168.172.154 as permitted sender) smtp.mailfrom=cyric@mm.st Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfhigh.phl.internal (Postfix) with ESMTP id C3D2F14000F5 for ; Sun, 2 Nov 2025 11:03:37 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Sun, 02 Nov 2025 11:03:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mm.st; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1762099417; x=1762185817; bh=LC+Pvv0d8tXHqZ6dRqioP/5tt6hpXN8XVEtc5YVTpQI=; b= J86XC3BZAeiv94HGx2NPwkNxJQg7OGTP4wly1T7PvarVBrK8EBFY06SXX/uYtlSD EJMXmpywuPU63hLFcMeRzB+TaN/cd1VhZtctY3nVQmA+QOeEqJS2nuZeLCtEFTh6 cxJ9HMy+54/nv3D1Ex+ugHoxNipdPD4F8u8FuBSpYLNhdhgn2GgDK9P+7DWBNl9L aAEXp6ML7TaBn1AbTsB2I2sub6LHg3mMtK8NfdiRAKXpYO5fyr23/8MTij8tyakQ wBZwCLu1fi07TS19QPM1p9iarIBvfUNbHkAisFpgr0WPsSLctlq9NxrCNIrdnXWu hMpY587coKNG8JbKC1nbRA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1762099417; x=1762185817; bh=L C+Pvv0d8tXHqZ6dRqioP/5tt6hpXN8XVEtc5YVTpQI=; b=0dirvX3HfpvDG6ovL tTjkyKVkBKI9Bts/Xau8VYpVZTiwWlecAT4mxk4hN4JZSDjv8C2cHKpWoqXO7O9u tYxpuI0EMKn64nxEa+PRjszIQ06A+AEkAYYNYHCiS8bRPjKkwJSsJiqZFEWn+M7S 7SE3mGnonb7rMgPgZUdma65BWZJpxsmEjo+6QdPZ0ZaANMkbxcfggIYxcJiF7RhW uuKYFLjIuDINf9Oxx+mGBIqqkLRpxG3uSsErMrWRxr1BnpYmuLBQiP2y+BZM4ZG7 BZs0/r1GAS2YKj4uRic/Tca2DBtch98hbP/GrJhi5hszXY7wzzXgDDP+8m/+QRdP G+7YQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddujeehieejucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertd dtvdejnecuhfhrohhmpegthihrihgtsehmmhdrshhtnecuggftrfgrthhtvghrnhepteel ueduteefgfehgeetgffgvdejgfdvveekieekhfffhffgvdeuvddtleffiedtnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptgihrhhitgesmhhm rdhsthdpnhgspghrtghpthhtohepuddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtoh epfhhrvggvsghsugdqtghurhhrvghnthesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: icc3648d4:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 2 Nov 2025 11:03:36 -0500 (EST) Message-ID: <7b3acdda-0837-4cb6-a94c-ea79cabef6c6@mm.st> Date: Sun, 2 Nov 2025 23:03:31 +0700 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 ? 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> <4c330c49-1c45-46cf-9d1e-afce745e8f88@smo.de> Content-Language: en-US From: cyric@mm.st In-Reply-To: <4c330c49-1c45-46cf-9d1e-afce745e8f88@smo.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[mm.st,none]; R_DKIM_ALLOW(-0.20)[mm.st:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.154:from]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[mm.st]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[mm.st]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[mm.st:+,messagingengine.com:+]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:151847, ipnet:103.168.172.0/24, country:AU]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_NO_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4czzzG6H7sz43WB Philipp Ost wrote: > On 11/2/25 02: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. > > ksh93 from ports (shells/ksh93) does not. I guess my answer was ambiguous, "does" here was meant to be "does behave that way", i.e. "does not print ^C when editing the line". >>> Perhaps three decades. As far back as I can recall and that includes >>> using paper terminals. It may be the libedit library there has a borked >>> way of dealing with a SIGINT.