From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: best practices for implementing Emms configuration Date: Fri, 09 Dec 2022 14:23:12 -0500 Message-ID: References: <87pmcspi77.fsf@rabkins.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20612"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel To: Yoni Rabkin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 09 20:24:03 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 1p3iyY-00057Z-Nh for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Dec 2022 20:24:02 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3ixz-0005Xm-R2; Fri, 09 Dec 2022 14:23:27 -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 ) id 1p3ixy-0005XK-De for emacs-devel@gnu.org; Fri, 09 Dec 2022 14:23:26 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3ixw-0005zx-DP for emacs-devel@gnu.org; Fri, 09 Dec 2022 14:23:26 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id A70EF80058; Fri, 9 Dec 2022 14:23:21 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 091E98001A; Fri, 9 Dec 2022 14:23:20 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1670613800; bh=nUZPRwk79aslxgWooip/kh9HGeBsYVyyvC/QjDvgra0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=opOje9EDMiGbswbf2Ro3njB5+GjJrcL491a/C5VSpj8u/nBaOuZdJEojJ5hlO1fNJ h9I0kiuAqs9BJs6ICjHuGCMrH9mitYe6sxjbUqTIFaVDBHiXht0GMejIEMkD+weKn9 pkk1uUarR7GW0IEyC1JZRfaal3LTAnEIvR3Tmq3msu9k0hmXTCsZ5VDYmJ9t/TdAax 5bDtcBdFtL29CbQpaD6zqq5g5875CVJRGELStyDrg3pV16M0SpXNid8lIxF1zDvn3o 6DqyQZQl5OzyKhvaFuE4D3AHVEB0PZi33/VdQ0cu+x3cO5HF0dlKP+vuNzflCAXDeP KLAyGIGPQVJJw== Original-Received: from pastel (unknown [45.72.193.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D7D3612014A; Fri, 9 Dec 2022 14:23:19 -0500 (EST) In-Reply-To: <87pmcspi77.fsf@rabkins.net> (Yoni Rabkin's message of "Fri, 09 Dec 2022 13:04:12 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:301086 Archived-At: > Write the configuration to the user's ~/.emacs in the same manner as " > ;; custom-set-variables was added by Custom." or ";; Added by > Package.el." I'm not a huge fan of this option for the sole reason that > I don't appreciate packages automatically editing a file I manually > edit. AFAIK people who don't like/want Emacs to edit their manually-edited config file (such as myself) should and do set `custom-file` accordingly. So the better option seems very definitely to just save the config via Custom: that's what it's for. > Write the configuration to ~/.emacs.d/emms/auto-config.el. Emms would > then look for that configuration file there during startup. This is > cleaner, and can have the benefit of Emms being configured without a > single line needing to be added by the user to their ~/.emacs. I personally dislike it when packages do such things because it's never completely clear how it interacts with the settings I put into my own manually-edited init file. Custom suffers from the same problems, of course, but once you've learned how it works, then this carries over to all the packages that use it. > I know that a bunch of packages store information in ~/.emacs.d/, just > as Emms does. But is it acceptable practice to store configuration > there too? There's no law against it. But as a user, I'd vote against it. Stefan