From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Suppressing native compilation (short and long term) Date: Sat, 15 Oct 2022 20:25:44 +0300 Message-ID: <83ilkl578n.fsf@gnu.org> References: <87bkqxf1ij.fsf@tethera.net> <834jwnbi6c.fsf@gnu.org> <87mtafnun5.fsf@trouble.defaultvalue.org> <83sfk6ahty.fsf@gnu.org> <8735c6b0wo.fsf@gnus.org> <87y1ty9lha.fsf@gnus.org> <87lepym6ok.fsf@trouble.defaultvalue.org> <877d1i9h7k.fsf@gnus.org> <83edvqyr3q.fsf@gnu.org> <874jwl8e4p.fsf@gnus.org> <87pmf64beo.fsf@gnus.org> <87h70i4a46.fsf@gnus.org> <83tu4irzl1.fsf@gnu.org> <87y1ttsrve.fsf@yahoo.com> <83r0zlqxcr.fsf@gnu.org> <87fsfqi95f.fsf@trouble.defaultvalue.org> <87wn915t5r.fsf@gnus.org> <87czatgfza.fsf@trouble.defaultvalue.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3339"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, luangruo@yahoo.com, akrl@sdf.org, monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org To: Rob Browning Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 15 19:26:53 2022 Return-path: 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 ) id 1ojkw0-0000gH-GI for ged-emacs-devel@m.gmane-mx.org; Sat, 15 Oct 2022 19:26:52 +0200 Original-Received: from localhost ([::1]:34062 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ojkvz-00048c-E3 for ged-emacs-devel@m.gmane-mx.org; Sat, 15 Oct 2022 13:26:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojkv4-0003IM-0P for emacs-devel@gnu.org; Sat, 15 Oct 2022 13:25:54 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48136) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojkv3-00057k-44; Sat, 15 Oct 2022 13:25:53 -0400 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=8ut7vaJWBu3p6HMDTv9VdAj7A9GAcHHxePJVtD4MSVM=; b=ed1PRVxndqbI pPrqxyHoquh40G2oSOm+LXHMqx/OCAfAwIaEzucewtXlolyB6LaJy9g0DqoTkyVCtMHI7LQpyds7P Zemb9jrzbGCsjRg12OHWFDaeeBfbVE//dWCLK2TyV1Ycx5+jSxnAQjPHKKbWEYqz9NyklLz9xsZhI l+J4dMbZ+ip+NSgdULnuj1PwIClOPTo39vYNaETjxbmjvwVYqsC3/rTGwBnU8BXfFCwy7Ov5AO7Bn cF4WZ1aUs//leci8USDaJ1G58DD+SW1oyqlYIfdo8iWSKngW4Gif6rYYzh40laNhdTvro3h7Wt2Fm Z9m20H2C1we4SC2QEsPX4A==; Original-Received: from [87.69.77.57] (port=2255 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojkv0-0005kn-OU; Sat, 15 Oct 2022 13:25:52 -0400 In-Reply-To: <87czatgfza.fsf@trouble.defaultvalue.org> (message from Rob Browning on Sat, 15 Oct 2022 12:21:29 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:297806 Archived-At: > From: Rob Browning > Cc: Eli Zaretskii , Po Lu , akrl@sdf.org, > monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org > Date: Sat, 15 Oct 2022 12:21:29 -0500 > > > Emacs should work with an unwritable file system, but there's probably > > code that bugs out in that situation -- but those things should be > > fixed. > > > > If you have a test case that demonstrates the problem, please open a bug > > report for that, so that we can get fixin'. > > OK, so if there is (or we come to) an upstream consensus that > HOME=/does-not-exist should work (would that be considered a subset of > the unwritable filesystem case?), then I think that's likely sufficient > for Debian packaging. (That's what we were initially attempting.) It should work, yes. And note that the message cited here, i.e. > Warning (initialization): Unable to create `user-emacs-directory' (~/.emacs.d/). > Any data that would normally be written there may be lost! > If you never want to see this message again, > customize the variable `user-emacs-directory-warning'. is just a warning, it shouldn't prevent Emacs from running. And yes, features that want to save files under ~/.emacs.d will be unable to do so, and could signal errors, unless you redefine the variables which hold the respective file names to point to some other place. This is the intended behavior, I believe.