From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Akib Azmain Turja Newsgroups: gmane.emacs.devel Subject: Re: best practices for implementing Emms configuration Date: Sat, 10 Dec 2022 00:42:25 +0600 Message-ID: <87mt7wmnam.fsf@disroot.org> References: <87pmcspi77.fsf@rabkins.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40721"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel To: Yoni Rabkin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 09 19:55:49 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 1p3iXE-000ANk-Li for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Dec 2022 19:55:48 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3iWb-0004HU-Dg; Fri, 09 Dec 2022 13:55:09 -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 1p3iWZ-0004HD-26 for emacs-devel@gnu.org; Fri, 09 Dec 2022 13:55:07 -0500 Original-Received: from knopi.disroot.org ([178.21.23.139]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3iWL-0007jN-I4 for emacs-devel@gnu.org; Fri, 09 Dec 2022 13:55:06 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id B344D411F5; Fri, 9 Dec 2022 19:54:50 +0100 (CET) X-Virus-Scanned: SPAM Filter at disroot.org Original-Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEc341rsk6se; Fri, 9 Dec 2022 19:54:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1670612087; bh=VYSi/VVHLPvXtnJZZHyrVT+Hoe8jtDWfls99t0MRZLo=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=DIGV+5eotuRCnRPx9gAG2c6O9xHFDLEFD2RXDbvKovmHEoB46+7wwr8LrOLXxIPi1 NO6uLFapkZ8QvSRkk6E5/57xCNCO+JQrySX1xj9pyBLd118Ko8tn+IDn9s3pnDy5Hv ozECtM56+KrtF1/tq0kykaKeuEO4wkdovrZK7K/GerS+4AbqxbXQW9xJzZ44l5+9rT oGe6HHqpusWEKF4rG/2GkqSi7asRxY7y9uNUhVJl6UdP9nYnLeAQzAL/Chdbtsym9U EzuhgBP68B9splyRBHILD3UY5QVFFmlAI1X713u2rp53NAYF43/ftFc3GM6P1OX5OT o36aBRHPq5TpA== 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=178.21.23.139; envelope-from=akib@disroot.org; helo=knopi.disroot.org X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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:301084 Archived-At: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Yoni Rabkin writes: > 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. This is better IMO. Just use Custom. The user can set 'custom-file' to redirect the extra line to somewhere else. > > 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. Not bad, but is there really any need to reinvent the wheel once again? > > 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. =2D-=20 Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5 Fediverse: akib@hostux.social Codeberg: akib emailselfdefense.fsf.org | "Nothing can be secure without encryption." --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEyVTKmrtL6kNBe3FRVTX89U2IYWsFAmOTgZEACgkQVTX89U2I YWvmmRAAykHz+W+fBOx66vN8EzMMpHbOizdWbhPGY6sgmw9K6+FCb1jOyKt6YH8v JfIcShLNcWdQRgf2opsHL4yKThDj8oEIyDDMel/F5JjFwccrqrg4k+HL6gbVGaT0 JEckkb5QLI4FpAA9rPBYSaOccORdepEsFxZVf3uPB/BObHnsyj9Sn3EOJwfyBMRS B/wEawt2Ykygri4xrwIav2l95Ct9rG8PHakj7uZVvIBCSt7JYQbNgoZ0NwQZT7uZ wuWPeqgqkRJLIW2HRROEmSk2R+22aBphXZVaZ9rBS0g5ZdXUK6K5AX1a8E+Q/5TV 2H0hhuv2gVTloirimGFXv5BJ/K2LzU/sabtfPMp+WC6C6ryZYD1BMWUZPzs9GMCW wbvWvf8J9nv6FMNHxR1L7jTaMSPx18B08KC6JU+9ucptQ2iZ8b2PlMXQKQ/mFc/H uYiOG4kwkutngJ7dEOI9UFRKNFJbEiEQ8Sxnf6F+ntEiQIP6fpvgp9RqV/9gi47J 11UBDt+lQurJ7wJYaLSbyDSAk4hlWi3ID5T8GLXyrOHng8NUzJrYBDzsOvtEf1al W06p6yyqSAbppMS0IAt/Zx8PPqsV25C2hOtgoHcFQVQQhtUXS4oo9UsQ2XbqCO/7 Q8luMbk5jWBTcYUHsu7nFhEdAfrNZbfawcQEZnfJeKBxLgQBkco= =PNXN -----END PGP SIGNATURE----- --=-=-=--