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: Re: best practices for implementing Emms configuration Date: Sat, 10 Dec 2022 08:45:44 -0500 Message-ID: <874ju3pe2f.fsf@rabkins.net> References: <87pmcspi77.fsf@rabkins.net> <87mt7wmnam.fsf@disroot.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38514"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Cc: emacs-devel To: Akib Azmain Turja Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 10 14:46:48 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 1p40Bj-0009mp-Ji for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Dec 2022 14:46:47 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p40Av-0001ic-El; Sat, 10 Dec 2022 08:45:57 -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 1p40Ar-0001hl-Rw for emacs-devel@gnu.org; Sat, 10 Dec 2022 08:45:53 -0500 Original-Received: from smtprelay0017.hostedemail.com ([216.40.44.17] 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 1p40Ap-0000sg-Qd for emacs-devel@gnu.org; Sat, 10 Dec 2022 08:45:53 -0500 Original-Received: from omf15.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 651E5120A26; Sat, 10 Dec 2022 13:45:47 +0000 (UTC) Original-Received: from [HIDDEN] (Authenticated sender: yoni@rabkins.net) by omf15.hostedemail.com (Postfix) with ESMTPA id 10BA918; Sat, 10 Dec 2022 13:45:45 +0000 (UTC) X-Ethics: Use GNU In-Reply-To: <87mt7wmnam.fsf@disroot.org> (Akib Azmain Turja's message of "Sat, 10 Dec 2022 00:42:25 +0600") X-Rspamd-Queue-Id: 10BA918 X-Rspamd-Server: rspamout07 X-Stat-Signature: s4j51tx4ew7jyc9mf3ip5g35ametyadn X-Session-Marker: 796F6E69407261626B696E732E6E6574 X-Session-ID: U2FsdGVkX18K8maBXGW5Vzf5V0czZpT+m3M9fb7VfaY= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabkins.net; h=from:to:cc:subject:references:date:in-reply-to:message-id:mime-version:content-type; s=dkim1; bh=s5jrpQ+ep4KeePnJ+Xbtu+xOUnyvp4BAjucFGL+kEOo=; b=fXmOIQyEuJzLLnGzIIfIVEaEIm3gWrhUg/fSd0aOPbtvO95V1QmtoLpe6mELZ5/xdQl30v8Lq0xjuAt9o8JiWW75Vs5jY+fSzTMdUv5ycjwPfzC+VdBFcWIzJCM7NvBa1uj/2PAWuBx1EqBXMoLDZrr1S9DipV+9ZVwQnlB/gPQ= X-HE-Tag: 1670679945-978935 X-HE-Meta: U2FsdGVkX18nNeL3lR2lkmOg8cXAz2icpUXRsTm0L2t5CkXqTBodYhIGlGBnC38rhCyWK9opiFyI1iNNuAtpxQ== Received-SPF: pass client-ip=216.40.44.17; 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:301107 Archived-At: Akib Azmain Turja writes: > 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. To be clear though: the goal isn't to present the user with one of the customize-group interfaces; I don't use them and wouldn't force anyone else to. The idea is to tell the user to invoke "M-x emms-setup", have the user answer a few y-or-n-p questions, and write the configuration based on that. >> >> 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? As above, I consider Emacs' customize interface to be a rather square wheel (but then, I don't like org either, so I accept that the problem may be me.) Thank you for the input. -- "Cut your own wood and it will warm you twice"