From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] new single file package: mpdired.el Date: Fri, 08 Mar 2024 11:26:22 +0000 Message-ID: <877cid55i9.fsf@posteo.net> References: <87o7bpul9s.fsf@ledu-giraud.fr> <87frx158b3.fsf@posteo.net> <878r2tug4b.fsf@ledu-giraud.fr> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29740"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Manuel Giraud via "Emacs development discussions." To: Manuel Giraud Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Mar 08 12:27:25 2024 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 1riYNp-0007WX-5f for ged-emacs-devel@m.gmane-mx.org; Fri, 08 Mar 2024 12:27:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1riYN9-00056y-54; Fri, 08 Mar 2024 06:26:43 -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 1riYN3-000511-FT for emacs-devel@gnu.org; Fri, 08 Mar 2024 06:26:37 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1riYMs-0005dT-TG for emacs-devel@gnu.org; Fri, 08 Mar 2024 06:26:33 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 19B2B240027 for ; Fri, 8 Mar 2024 12:26:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1709897184; bh=krf8J9A838DCeA7R1GCSy+AoD1OAkcSRBJOjjVA3ZzI=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=lN0sAo/tAmjo7Je/Nea4kTlNODpsReBaPRxnN62z+tEM8bhHFuW3fD5F7Mvyoph+1 +mK878xksbTDMlJKy7hgAdkD7D/Rf/0L2XaDnAW10zaVS0pot6PAWyvn9gus1ZauU4 H8y6yyyeMNV7qLs4A4OAwL46sQSglOf/Rl+aKWDreRVancxxZqA1V0BOgCUnSzmp4i 0s8j/rSb7WSmttjs8W0uSAlj4TNg3wNWCkbYkvtms89oJRkwU4Jeknqg49oM43PW3/ U8D1LYY+sJzot8cpL9r6ePmKhnib0vRDJSs9UMFGPe+Rje0cXu6S2lpOo7TmQNCAxz pqlKHT1F1ry7A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TrkQ72pBXz9rxF; Fri, 8 Mar 2024 12:26:23 +0100 (CET) In-Reply-To: <878r2tug4b.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Fri, 08 Mar 2024 12:17:56 +0100") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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:316897 Archived-At: Manuel Giraud writes: > Philip Kaludercic writes: > > Hi Philip, > > First thanks for your all your inputs! > > [...] > >> In the end a Git repository will have to be created. I don't think one >> should have to be ashamed of the commit history (most people won't >> care), but it is also fine to discard the current history and replace it >> with a fresh repository. > > Ok. Maybe I'll start with a fresh history if I feel like it. > >> By default, we would like to mirror some external repository. It >> doesn't have to be hosted by some large Git forge, just something that >> can be synchronised regularly. The alternative to this would be to have >> a branch in elpa.git that would have to be manually updated (either by >> yourself if you get access to the repository, or by someone here on the >> mailing list with access that would see your message). You can imagine >> that we want to avoid the latter setup, since it creates more >> friction. > > Of course, I'd also like to avoid this latter setup. Just to be sure, > you confirm that a git repo is unavoidable? Could it be a just tarball > available on web server? Technically yes, but the ELPA build system would have to be updated just for this use-case. >> From experience, it is usually helpful to have a Git repository with >> multiple files, for files like a README or an .elpaignore file or if you >> decide to split up the file into multiple files at some point. > > Yes, you're right maybe I'd like to add a texinfo later for instance. > >> If you dislike Github, you could also take a look at Sourcehut or >> Codeberg for hosting. > > Ok. If a git forge is mandatory, I'll ponder which one I'd prefer to > use. As I said, a git forge in that sense is not necessarily needed, you could also just host the git repository from some website over https://. >>> Anyway for the braves and curious, here is the current version of this >>> package. It is called MPDired and is yet another client to Music Player >>> Daemon. It features a Dired-like user interface. Previously I was a >>> Mingus user so MPDired might have some legacy to it. >> >> Here some comments > > For the rest of your comments inline, I'll just ask on those I don't > understand. > > [...] > >>> "n" #'mpdired-next-line >>> "" #'mpdired-next-line >> >> Perhaps one could also rebind a few commands here, like `next-line'. > > I don't understand what you mean here. It is possible to remap a command, without having to bind a key. See (elisp) Remapping Commands. The advantage is that if the user has any custom bindings, say for next-line, then they would automatically be inherited. That is comfortable from a user-perspective, because the major-mode aligns more with their usual intuition. > [...] > >>> (defun mpdired-change-marks (&optional old new) >>> "Changes mark from OLD to NEW. It asks the user for OLD and NEW." >>> (interactive >>> (let* ((cursor-in-echo-area t) >>> (old (progn (message "Change (old mark): ") (read-char))) >>> (new (progn (message "Change %c marks to (new mark): " old) >>> (read-char)))) >> >> Why not use read-char's PROMPT argument? > > I did not know about it and it is copy-pasto from dired ;-) I don't know if there are any peculiar edge-cases either, perhaps someone else knows more? > Thanks. -- Philip Kaludercic on peregrine