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 02:10:01 +0200 Message-ID: <87sfhoyv8m.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="4238"; 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 Sat Dec 10 01:11:06 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 1p3nSK-0000tG-Bh for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Dec 2022 01:11:06 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3nRR-0003Tj-SN; Fri, 09 Dec 2022 19:10: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 1p3nRP-0003TW-Kw for emacs-devel@gnu.org; Fri, 09 Dec 2022 19:10:07 -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 1p3nRN-0007Yd-0f for emacs-devel@gnu.org; Fri, 09 Dec 2022 19:10:07 -0500 Original-Received: from odin (dsl-trebng12-b04885-76.dhcp.inet.fi [176.72.133.76]) by thaodan.de (Postfix) with ESMTPSA id 7D43AD08C0A; Sat, 10 Dec 2022 02:10:02 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thaodan.de; s=mail; t=1670631002; bh=pdOY+44dMLdW7Szdq72MX+hLFMIPteSgKTvBxq+Go74=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=NL38mLdCvEvXOHn/36ap1oUQdFpIwreqe7AVNBsCKevjd/7RQ2av7UVWHury9TX6t 1JsFQcB8g9SCm2GPgzcBJhthO9W1EnqAo1VarID6++mZahQdl6stakqXe98ZNOE+Tv sOi7gr1CAL7KVECllPER+FU8x1ugENNPBzA+2dkhAh6rE/qISKYBAungWU/XD0Mo7w c3YozLaulOYI3AJTvbz5bE6t1FMct3d+RSedu+8fRAEiTzRS+Lw2N4rVA6zlFvWdi8 5rb0UKjU1jMuJpOgBdsHQvF7eAVbY3Ee8CGSu1KoSdflicJ3i+3jqdS296OI91LC4T c6sEz21V6GRtqMYcmtBsuALxU/uivGKdYtAX9Q88CQNdDiTxJAYFiClb9v0zLft/Ki JjD76ebcc9tKpNgC6d34LyPYiupTobEabF86HAbTFxLvAhKRbok7+OX+0aZx8LHmqc VzxtAeueT5mcg0i/dZqlaxJEiJNDE4DAMMAuCOZF4fb0dk+am1oV0GTGSFKzgC3noP 6botr4DzqZTng3+3/4W7X2cD69TCOUHI5E2shrMS16fA9CIgp4OXK90xRjHJCPTuqL HgDar8zSj0sI4C1mv/0FYNjCwVX0bZVcTRKmnoIE/WWhDg2P6oHpRAghEf6HA7ojfd 1nLCigTDOLzP/wupeXFxB7i8= 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=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, 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:301091 Archived-At: 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: I was in that situation a month ago, I want to add what would make this easier. Emms is quite flexible which makes the initial setup a little more complicated. For example if I want to setup as an mpd client I would want some defaults that make sense and that can be changed if needed. I think would make more sense to have defaults for common use cases such as these then writing a configuration, simplifying the configuration rather than making it easier to configure. For example Circe provides defaults for common IRC server's than can be adjusted individually. Emms could provide similar defaults. Br, Bj=C3=B6rn