From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: hw Newsgroups: gmane.emacs.help Subject: Re: how to force auto-save of buffers not visiting files, right now? Date: Mon, 21 Mar 2022 04:55:22 +0100 Message-ID: <2555abdd3813f67d08230e809526bc4c6f45087b.camel@adminart.net> References: <87wngsmdwp.fsf@web.de> <9f32ac59eb1bc186b015c0b6c5b94822e70d4135.camel@adminart.net> <87y2164u5p.fsf@web.de> <9c3935a33573d50e595f37103434db5e29c21063.camel@adminart.net> <87ilsa61tn.fsf@web.de> <37e890d9c251b30d0caf83aa590bca1ad92ec5d4.camel@adminart.net> <87wngqclgk.fsf@gmx.de> <95f0e96687187c20086bf9f85a031a7271401407.camel@adminart.net> <4486cbd26d1c5c4587507212bfbb7ca34c5d92ea.camel@adminart.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24225"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.42.4 (3.42.4-1.fc35) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 21 04:56:06 2022 Return-path: Envelope-to: geh-help-gnu-emacs@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 1nW99K-000649-CM for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 21 Mar 2022 04:56:06 +0100 Original-Received: from localhost ([::1]:58826 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nW99I-0001eH-LP for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 20 Mar 2022 23:56:04 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:50384) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nW98k-0001am-OU for help-gnu-emacs@gnu.org; Sun, 20 Mar 2022 23:55:30 -0400 Original-Received: from mo4-p00-ob.smtp.rzone.de ([85.215.255.25]:43191) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nW98f-0004V4-NZ for help-gnu-emacs@gnu.org; Sun, 20 Mar 2022 23:55:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1647834923; s=strato-dkim-0002; d=adminart.net; h=References:In-Reply-To:Date:To:From:Subject:Message-ID:Cc:Date:From: Subject:Sender; bh=UuRq1zHYpxkMZQV7jJBSOT+J+0uWQqLLue3p2pFLHLs=; b=mKBghPOZa+Ov2rXY5+ZTD2XrCg78ZyG7qhUoXQBB6uvkLlQK7hC+ip2IjI5kpzLTRP Sjv0SjOhEXHaXjqvo60BnqdQVGIZWHdgQgdWKOYu4+OUYG+qWtIGLOYWi7wBp2krF2Ke xEqVKaOdABp2SZkgGgQge3SJqHqAIiWDnuyfyb4WRp2rvkzqpYLZRTyecQ3conqMLCCE f+PoAhYTd25yBMCr9VQK220xyJIlgAHLSvV8Hu73+ZZyu9gXE0sk80emNa83tAUrV0Og dL9dZxdBrOjV3XBR44DXLXD33vHiGxsyCIx0DZm79aRfJ6m6nOApr9wz9BG4MJ1KPYcF VB8w== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":JHskdESlcvGJlcww5P8kEdDfB60eDdbwg2z1BLI60U5wCzf09BLZZsSKYxPQaavhGO/kap91D/OoCoP2QrxBY8ct0jBjyQ6QTgS1" X-RZG-CLASS-ID: mo00 Original-Received: from [IPv6:2a09:8e40:1b4d:a200:156a:299a:44c4:5337] by smtp.strato.de (RZmta 47.41.1 AUTH) with ESMTPSA id U40bf1y2L3tMCCt (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Mon, 21 Mar 2022 04:55:22 +0100 (CET) In-Reply-To: Received-SPF: none client-ip=85.215.255.25; envelope-from=hw@adminart.net; helo=mo4-p00-ob.smtp.rzone.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:136700 Archived-At: On Sun, 2022-03-20 at 11:30 +0100, tomas@tuxteam.de wrote: > On Sun, Mar 20, 2022 at 11:19:52AM +0100, hw wrote: > > > > On Sun, 2022-03-20 at 08:29 +0100, tomas@tuxteam.de wrote: > > > On Sun, Mar 20, 2022 at 07:36:42AM +0100, hw wrote: > > [...] > > > > > Its value is > > > > (("\\`/[^/]*:\\([^/]*/\\)*\\([^/]*\\)\\'" "/tmp/\\2" t)) > > [...] > > > Yes --- I didn't see that because that expression is so unreadable. > > To some it is readable, to some not. It takes some practice. I'm sure there are 5 people for whom it's easily readable. For others, it would be helpful if the description would explain what the default is supposed to match and if it would have same useful examples. > > Forcing remote auto-save files into being saved into a volatile > > directory is worse than not saving them at all. > > Are you always so absolute in your assessments? I am always am what I am. > > How do I change that /tmp to not being volatile and keep it that way? > > Look into the files in /etc/init.d (or, if you are a systemd person, > ask around in your distribution's mailing list: I know very little > about systemd). Typically, there's code there to wipe /tmp clean > on boot. Then, you'll have to make sure /tmp is not mounted from > tmpfs (as is customary these days) but from a regular directory. > > > > Careful. You can change that, too, if you want. Someone thought > > > it to be useful. > > > > Like how? > > See above. Try > > find /etc/init.d -type f -exec egrep "\" {} + > > or ask around if you're on systemd (i guess it'll have one unit > to mount tmpfs on /tmp, perhaps another to clean up /tmp -- > unless they rely on always using tmpfs, where the latter would > be unnecessary. But don't believe me on things systemd. Actually > I've no clue :) See, that's one problem, and there are others, like keeping things changed the way you changed them. Who says that when you make /tmp persistent, that the change will persist over the next software or distribution update or upgrade? When you start changing things like that, there are likely to be more and more things over time and it will be difficult or impossible to maintain that. So don't say "you can change it". You can't, really. > > > I'm around for long enough that I remember the > > > time before [...] > > > Some things, like making /tmp volatile, are still stupid. > > OK, I think I'll stop here. We are off-topic anyway. Hm, quite a bit, yes.