From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yoni Rabkin Newsgroups: gmane.emacs.devel Subject: best practices for implementing Emms configuration Date: Fri, 09 Dec 2022 13:04:12 -0500 Message-ID: <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="27010"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 09 19:04: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 1p3hjw-0006lB-CG for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Dec 2022 19:04:52 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3hjR-00070j-M6; Fri, 09 Dec 2022 13:04:21 -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 1p3hjP-0006zV-PQ for emacs-devel@gnu.org; Fri, 09 Dec 2022 13:04:19 -0500 Original-Received: from smtprelay0011.hostedemail.com ([216.40.44.11] helo=relay.hostedemail.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3hjN-0001k2-UF for emacs-devel@gnu.org; Fri, 09 Dec 2022 13:04:19 -0500 Original-Received: from omf06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 5F72B14134B for ; Fri, 9 Dec 2022 18:04:15 +0000 (UTC) Original-Received: from [HIDDEN] (Authenticated sender: yoni@rabkins.net) by omf06.hostedemail.com (Postfix) with ESMTPA id 54E702000E for ; Fri, 9 Dec 2022 18:04:13 +0000 (UTC) X-Ethics: Use GNU X-Rspamd-Queue-Id: 54E702000E X-Stat-Signature: tsi8qcfd7kahqkhbpeho7znrcpitok5w X-Rspamd-Server: rspamout02 X-Session-Marker: 796F6E69407261626B696E732E6E6574 X-Session-ID: U2FsdGVkX1922IN89nISRnHokd1dR2OA0FEDGc+yrDc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabkins.net; h=from:to:subject:date:message-id:mime-version:content-type; s=dkim1; bh=hfZGlPVP/cfPSiO4XjkxiMcjUpHjrjcTiomlYzaMFNE=; b=J/oy22bpjkCpkWm30aoW5rwgzvScMxkgFFCqtGVmqDJ/t2/bb8grgVXjz9qAhSyq0TbuyCaXdDMqzKRouduobarQkecTDWO/OXzaO3Wwa4NR4o3Tgw6NLlSOPOKLytEMjAzf9k5CDSLyOL7MPTdMq4fHfCYcxTgBPWzvJ74irxI= X-HE-Tag: 1670609053-775241 X-HE-Meta: U2FsdGVkX1+e1ozE2K/SiybpA9gUtLZzPnnNB75qB45bKD/WOwKOy8i/SCNhEpJEQOqHBtWKOZ5fFIdnN9gXdw== Received-SPF: pass client-ip=216.40.44.11; envelope-from=yoni@rabkins.net; helo=relay.hostedemail.com 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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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:301082 Archived-At: Hello all, We are trying to make Emms (https://www.gnu.org/software/emms/) better out of the box. The idea is to have the user invoke "M-x emms-setup", have Emms ask some questions (check which player binaries the user has installed, which metadata programs are installed, where the music is located, etc.), and have Emms generate and write the appropriate elisp configuration. I can think of two approaches. I am wondering which, if any, would be considered best practice: 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. XOR 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 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? What I'm looking for is something along the lines of: "sure, we don't care", or "don't do that, we don't want Emacs packages to go down that route", or something similar. Thank you in advance. -- "Cut your own wood and it will warm you twice"