From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Bj=C3=B6rn?= Bidar Newsgroups: gmane.emacs.devel Subject: Re: best practices for implementing Emms configuration Date: Sat, 10 Dec 2022 01:46:22 +0200 Message-ID: <87wn70ywc1.fsf@thaodan.de> References: <87pmcspi77.fsf@rabkins.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15868"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Yoni Rabkin , emacs-devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 10 00:47:19 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 1p3n5L-0003ow-GG for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Dec 2022 00:47:19 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3n4c-0007vt-7u; Fri, 09 Dec 2022 18:46:34 -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 1p3n4Z-0007vc-Gp for emacs-devel@gnu.org; Fri, 09 Dec 2022 18:46:32 -0500 Original-Received: from thaodan.de ([185.216.177.71]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3n4T-0003Ke-W2 for emacs-devel@gnu.org; Fri, 09 Dec 2022 18:46:31 -0500 Original-Received: from odin (dsl-trebng12-b04885-76.dhcp.inet.fi [176.72.133.76]) by thaodan.de (Postfix) with ESMTPSA id C10E8D08C0A; Sat, 10 Dec 2022 01:46:22 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thaodan.de; s=mail; t=1670629582; bh=Z67UBGGt1/Qc5lwFcSOUOZA2iqX3x1qV26yjYI1gxRk=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=WEPjzSg8qbaqDuzMeQFSvQO9yV/JKAeNsEqMw280qzC6hkjUgHGMYiJ9Wv8jShi/P 1WvU871qMllFzl8b1M5phHsSxHSEEUx/Vr60ZwR01Vs9jfdwWx3wEWjf4g5+zoZUsl Vgpy5bYk0sFBGnuGEWlO4NySwfkgcdzgITPURxe6DyVJpqITyH8bZKKhbFu/fVom7a Pnt7CmX/iLJVWXq+aR347A9d0a5eiHhBJN/sh7LwAEvBTtXHvu/l69eRtPKqCblpvf rmviEmBmMcexARwxL0eYfKBCvKUTZ3oEnwRwYK6iLC3cfEdnNRhXlzcn6ttBEdIbAw gEUkcH5DZms9BgeBXz15dkH6CNn3eYCMXcyYxQhA/516vbtb4XkdUDhI6Zhkhgf/6r jM5hSRmFkwxDhBntw/MRq2gcwfNXjpXCeCnsvtczYkKal+oSVsXtmem55WmQYTWjAj +kuak1voy2wEewbd+4lalol2y1dDLDnXsMmbixGrtceU3ciYHSm6M1fMianZzCYKUG vnFsjI86G5IdVz/b7EiA83ZtyOh0DWf7CmQBlHZEh/c13+Xvr04ZwSfIvwWNSQEIqe bBaBPhIh6rbzfpZg6jFuVVHxHwQn31l2pK9qqDwYx+oNpYomxZEHevaaHqNP3TFCOK /ojCTfyF8qoOQ3p2vVU/E2Eg= In-Reply-To: (Stefan Monnier's message of "Fri, 09 Dec 2022 14:23:12 -0500") Received-SPF: pass client-ip=185.216.177.71; envelope-from=bjorn.bidar@thaodan.de; helo=thaodan.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, SPF_HELO_PASS=-0.001, T_SPF_TEMPERROR=0.01 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:301089 Archived-At: Stefan Monnier writes: >> 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. I agree however those people that don't like Emacs to edit their configuration file might also setup emms manually. >> 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. If the package writes the file with setopt the behavior should be the same as using custom, however no released version support that so far. >> 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. Sometimes it makes sense, several packages to it e.g. by proving an org-mode file setup some configuration value. As long as the location of the file can be configured it does sound fine to me, packages such as no-littering exist for a reason. Br, Bj=C3=B6rn