From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: package-update-all from command line Date: Fri, 27 May 2022 22:33:40 +0200 Message-ID: <87bkviln4b.fsf@gnu.org> References: <87r14f9syr.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18480"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.23; emacs 29.0.50 Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 27 22:48:39 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 1nugsx-0004d5-5E for ged-emacs-devel@m.gmane-mx.org; Fri, 27 May 2022 22:48:39 +0200 Original-Received: from localhost ([::1]:55084 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nugsw-0006P3-17 for ged-emacs-devel@m.gmane-mx.org; Fri, 27 May 2022 16:48:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42836) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nugrC-0004fT-11 for emacs-devel@gnu.org; Fri, 27 May 2022 16:46:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39470) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nugrB-0002oM-LH; Fri, 27 May 2022 16:46:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-reply-to:Date:Subject:To:From: References; bh=PJInclSzduJi7XG21hCy6lrtXF6w1I13TPP2iuyHZbM=; b=l7OO9BBa78Y/S9 aWdjDLfuTho7rREFw/J3tvIXQuTzgYybc3t2gWQC0WV9s0LCobnhJsfwdYgXIeoCBdmlDD5AJ5ltE OXMY2KTs9h/6g+tFsUbYa3QyQKKUACUGbu/9K6NqfbGR1UAzSb8+u2r2pJx8qK+0ZpdKZdxQf53Lr vDn51I5To0DeWO9bQZMY+8PwoIq1g/LO+OGujj3elWk7O69GvTMecLoZMpViPSHxI314OlIl+PCHV jxTnZEbYoCKg3L34kAUMzTAfoEyf6L0p4AnqYZUzt8V3wa6bbiaoF8mry3PswAKc8LlxJQ/yJWQ8p vvenVxf+hWJ4WkcDzIkg==; Original-Received: from auth2-smtp.messagingengine.com ([66.111.4.228]:55185) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nugrB-0007qV-Ds; Fri, 27 May 2022 16:46:49 -0400 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailauth.nyi.internal (Postfix) with ESMTP id 1752927C0054; Fri, 27 May 2022 16:46:49 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 27 May 2022 16:46:49 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeelgdduheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfhgfhffvvefuffgjkfggtgesthdtredttdertdenucfhrhhomhepvfgrshhs ihhlohcujfhorhhnuceothhsughhsehgnhhurdhorhhgqeenucggtffrrghtthgvrhhnpe dujedtheduvdelffejkeetgedvheelhedvueefhfeukeekkeehvdfggeegffevgfenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhorhhnod hmvghsmhhtphgruhhthhhpvghrshhonhgrlhhithihqdekieejfeekjeekgedqieefhedv leekqdhtshguhheppehgnhhurdhorhhgsehfrghsthhmrghilhdrfhhm X-ME-Proxy: Feedback-ID: ib2b94485:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 27 May 2022 16:46:47 -0400 (EDT) In-reply-to: <87r14f9syr.fsf@gnus.org> 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:290318 Archived-At: Lars Ingebrigtsen writes: >> The same question applies to `package-update' but there it would be >> annoying if it always refreshed first when updating one package after >> the other. So maybe the refreshes should be restricted to "there >> hasn't been a refresh in the last ". > > Yes, perhaps that'd be nice? But I'd expect somebody who'd use that > function would already know that the package in question has an > update, so a refresh might not be vital there. > > Or... Hm. No, I think you're right. Perhaps it should only do these > refreshes when called interactively, though? I'm not sure how people will use that command. FWIW, I just update all and be done. But others might want to use package-update in order to know exactly what is going to be updated and then invoke it multiple times in a row. In such a case, I think it would be a bit annoying if it always refreshed just because that might take some seconds. One easy way around that would be to use completing-read-multiple instead of completing-read in package-update so that you don't need to call it multiple times in order to update more than one package. >> However, your "emacs -batch -l ~/.emacs ..." recipe doesn't work with >> every init file, at least it didn't work with mine. I use >> `user-init-file' in my ~/.emacs.d/init.el which is nil if emacs is >> started with -batch, and it seems that packages are not initialized >> so emacs complained about void-function use-package. I've catered >> for it in my init file now but I guess -batch -l cannot >> be recommended as a general practice for this purpose. > > It's a bit of a chicken/egg problem, perhaps? I wouldn't say so. It's just that -batch is more suited for stuff like "byte-compile this lisp file". I wouldn't mind having additional options -user-batch and -user-script which act the same as the non-user versions but do the normal startup initialization. Bye, Tassilo