unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
Subject: Re: [ELPA] new single file package: mpdired.el
Date: Fri, 08 Mar 2024 13:22:12 +0100	[thread overview]
Message-ID: <87v85wud57.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <877cid55i9.fsf@posteo.net> (Philip Kaludercic's message of "Fri,  08 Mar 2024 11:26:22 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

[...]

>> 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.

Ok so it's a "no": I don't want to put a burden on someone else.

[...]

>> 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://.

Great.  I think it is what I would do then.  Thanks.

[...]

>>> 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.

Yes it makes sense.  I'll look at it.
-- 
Manuel Giraud



  reply	other threads:[~2024-03-08 12:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  9:26 [ELPA] new single file package: mpdired.el Manuel Giraud via Emacs development discussions.
2024-03-08 10:25 ` Philip Kaludercic
2024-03-08 11:17   ` Manuel Giraud via Emacs development discussions.
2024-03-08 11:26     ` Philip Kaludercic
2024-03-08 12:22       ` Manuel Giraud via Emacs development discussions. [this message]
2024-03-08 13:18         ` Philip Kaludercic
2024-03-08 16:25           ` Manuel Giraud via Emacs development discussions.
2024-03-08 16:34             ` Philip Kaludercic
2024-03-08 17:06               ` Manuel Giraud via Emacs development discussions.
2024-03-08 17:29                 ` Philip Kaludercic
2024-03-09 13:18                   ` Manuel Giraud via Emacs development discussions.
2024-03-09 13:36                     ` Philip Kaludercic
2024-03-10 16:00                       ` Manuel Giraud via Emacs development discussions.
2024-03-10 17:03                         ` Philip Kaludercic
2024-03-10 17:43                           ` Manuel Giraud via Emacs development discussions.
2024-03-10 17:49   ` Manuel Giraud via Emacs development discussions.
2024-03-10 18:03     ` Manuel Giraud via Emacs development discussions.
2024-03-10 18:15       ` Philip Kaludercic
2024-03-10 19:24       ` Eli Zaretskii
2024-03-11  8:44         ` Manuel Giraud via Emacs development discussions.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v85wud57.fsf@ledu-giraud.fr \
    --to=emacs-devel@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=philipk@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).