From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: missing "/" in value of user-emacs-directory when using
 --init-directory flag
Date: Mon, 12 Dec 2022 20:13:28 +0200
Message-ID: <83edt4qylz.fsf@gnu.org>
References: <CAJddU=rTA9YxXJA98b0Yp5bBkLCFH=r1jxOqXngQ9JX3tccimQ@mail.gmail.com>
 <83sfi1lj1h.fsf@gnu.org> <47dca941-bf75-455b-f8b2-07b6574cbc79@dasyatidae.com>
 <CAJddU=oBe7Z9JgHGM7YE0tf1rp95Pvua7+t2CKTo9-Ddz1JcUA@mail.gmail.com>
 <83mt7sstd0.fsf@gnu.org>
 <CAJddU=ox+atrgHTJmJkksrKPV=eRRLteno0HqF5EHDk+1W1ggA@mail.gmail.com>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="18438"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: rtt@dasyatidae.com, emacs-devel@gnu.org
To: Yilkal Argaw <yilkalargawworkneh@gmail.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 12 19:13:45 2022
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1p4nJB-0004YY-Km
	for ged-emacs-devel@m.gmane-mx.org; Mon, 12 Dec 2022 19:13:45 +0100
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1p4nIu-0001Kj-0p; Mon, 12 Dec 2022 13:13:28 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1p4nIs-0001Ka-GZ
 for emacs-devel@gnu.org; Mon, 12 Dec 2022 13:13:26 -0500
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1p4nIs-0000aw-5n; Mon, 12 Dec 2022 13:13:26 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=Nsqf6SOkXCFvApzd/6RzSJWzvx1yFyPYn3K1T3fLhwQ=; b=bHOdc035EWQ9
 271b5UGnhpG/6Qd1JNf4wBtsdZhbivpGJYBXIllP5IWEROOVBM/9x1CLdkm1DOyZa5PjiRcmL2Q2s
 gH1dfdOu93/K6C8V/xKOCwFSaU9yZVX/OsqHPtZStLxui1rWWg2DhHCkKvYIfVM6zYK2d6r+c+d1F
 12ii+ng0wLWJekhou3xym93/yR26Pz46maaR3GxY+z3N3QKhjOZW3Y9iI7nn/OP2zfCoQOZ1+rwG1
 BtZY33v2PIxYK9K/irpa1CDNOD+d23bCLPCn8WfU60C77igK5LkAi2iV+tx7RuacBF9Gi0GXjBLJd
 PDqXlltgSLjoN9tXucj7vQ==;
Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1p4nIr-0006EP-Ma; Mon, 12 Dec 2022 13:13:26 -0500
In-Reply-To: <CAJddU=ox+atrgHTJmJkksrKPV=eRRLteno0HqF5EHDk+1W1ggA@mail.gmail.com>
 (message from Yilkal Argaw on Mon, 12 Dec 2022 18:04:10 +0000)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.devel:301263
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/301263>

> From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
> Date: Mon, 12 Dec 2022 18:04:10 +0000
> Cc: rtt@dasyatidae.com, emacs-devel@gnu.org
> 
>  The issue was fixed more than a week ago, so I'm unsure what is the
>  purpose of this post.  We are consistent.
> 
> Sorry I didn't see anything regarding a patch or a commit to fix the issue in the thread. Sorry about that.

See commit 401f76cc3d.