From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 10365 invoked from network); 1 Dec 2023 18:23:13 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 1 Dec 2023 18:23:13 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20210803; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Content-Type:Subject:Cc:To:From:Date: References:In-Reply-To:Message-Id:MIME-Version:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=l2eYLO2Vs1ANpQZQtTyq1CvuW+ornycMqKZzbbdGFtM=; b=lKj3BkuPaVlKZ1ps1fJFS5GQY4 WB6wVbRKlfrp53OCE3JsMaJCCJkPSNp9fBY7xb6CXf4L8yJ7HVRSMWwiHht3+moQnWK+ZBqK0qktf AVq4/ngnnh5tZRYYNaxD4IKwZuIBe0swjrUUBfBuSibdf3GgptnmOc6LZw+1wbQouAXNZEdK/Dlyx pRJdumtf1W4ADsEag5k9beiY/+ZU67Wx1zdDHlABdCqC02ntD0eh/MaGgHJz6bDalIezKzFzqEMeh 79fsy4ZCX68iiHA2+5LDPz+W7lz04ZNlBE+rqa7hf+ClsWpMSWqc30POSxCbrpdYA+q4qbCSqT+aB w6jSgfaQ==; Received: by zero.zsh.org with local id 1r98AR-000E7a-9a; Fri, 01 Dec 2023 18:23:11 +0000 Received: by zero.zsh.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) id 1r989o-000Dok-SI; Fri, 01 Dec 2023 18:22:33 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailauth.nyi.internal (Postfix) with ESMTP id 431AA27C005B; Fri, 1 Dec 2023 13:22:31 -0500 (EST) Received: from imap48 ([10.202.2.98]) by compute2.internal (MEProxy); Fri, 01 Dec 2023 13:22:31 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeiledgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvfevufgtse httdertderreejnecuhfhrohhmpefnrgifrhgvnhgtvgcugggvlhojiihquhgviicuoehl rghrrhihvhesiihshhdrohhrgheqnecuggftrfgrthhtvghrnhepieegffelkeekgeevue dvfeejuddujeegffefkedugefhudehtdfgvdffveejieeunecuffhomhgrihhnpehhrghn ughlvgdrtggunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homheplhgrrhhrhihvodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhithihqdduudeh udekjeejtdegqdduudelvdejfeekhedqlhgrrhhrhihvpeepiihshhdrohhrghesfhgrsh htmhgrihhlrdgtohhm X-ME-Proxy: Feedback-ID: iaa214773:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id EB62F31A0064; Fri, 1 Dec 2023 13:22:30 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1178-geeaf0069a7-fm-20231114.001-geeaf0069 MIME-Version: 1.0 Message-Id: <72dcfda2-9b2b-4c76-8e53-ee3332553edc@app.fastmail.com> In-Reply-To: <3uINOrbo4IXmuxTPyOMY6U_gv4-qULOThBv5Hd01KcO76FK9AvEFOOIo02fy5VQBIrudqP7rz__wEo1FOG2X2cMLkJzV1wp-1fYkCKYID_8=@protonmail.com> References: <3uINOrbo4IXmuxTPyOMY6U_gv4-qULOThBv5Hd01KcO76FK9AvEFOOIo02fy5VQBIrudqP7rz__wEo1FOG2X2cMLkJzV1wp-1fYkCKYID_8=@protonmail.com> Date: Fri, 01 Dec 2023 13:21:34 -0500 From: =?UTF-8?Q?Lawrence_Vel=C3=A1zquez?= To: "Julian Prein" Cc: zsh-workers@zsh.org Subject: Re: [PATCH] cd: Append 2nd argument to CWD if 1st is empty Content-Type: text/plain X-Seq: 52352 Archived-At: X-Loop: zsh-workers@zsh.org Errors-To: zsh-workers-owner@zsh.org Precedence: list Precedence: bulk Sender: zsh-workers-request@zsh.org X-no-archive: yes List-Id: List-Help: , List-Subscribe: , List-Unsubscribe: , List-Post: List-Owner: List-Archive: On Fri, Dec 1, 2023, at 8:32 AM, Julian Prein wrote: > My motivation to submit this patch was primarily the assumption that specifying > an empty argument is an edge case that is not well defined in the documentation > and that the current behaviour is limited in its use cases. To me an appendix > seems more flexible in the ways a user can utilize this. FWIW the current behavior -- while undocumented -- is aligned with that of ksh, and this change would break that alignment and become one more thing for ksh emulation to handle. % cd /bin % ksh -c 'print "$KSH_VERSION"; cd "" /usr' Version AJM 93u+ 2012-08-01 /usr/bin % mksh -c 'print "$KSH_VERSION"; cd "" /usr' @(#)MIRBSD KSH R59 2020/10/31 /usr/bin The old behavior is not a bug, and the new behavior doesn't strike me as particularly useful, so it's not clear to me that this would be worth it (either as a breaking change or one hidden behind yet another option). -- vq