Re: move-lines.el: a lazy programmer's package to move lines around

Pedro Andres Aranda Gutierrez <[email protected]> Sat, 8 Aug 2026 21:57:17 +0200
Newsgroups gmane.emacs.devel
Message-ID <[email protected]>
Will do when back home :-)

Enviado desde mi iPhone

> El 8 ago 2026, a las 12:52, Philip Kaludercic <[email protected]> escribió:
> 
> Stéphane Marks <[email protected]> writes:
> 
>>> On Fri, Jul 31, 2026 at 2:51 PM Philip Kaludercic <[email protected]>
>>> wrote:
>>> 
>>> Pedro Andres Aranda Gutierrez <[email protected]> writes:
>>> 
>>>> Hi Philip
>>>> 
>>>> Thanks for the time you took to analyse this.
>>>> I keep the functions apart because of the corner cases ;-) and
>>>> because I use it to introduce people into intermediate Lisp
>>>> programming.
>>>> 
>>>> Of course it is tempting to have this added to Emacs itself.
>>>> My main concern are potential collisions with ways of working other
>>>> people may have developed over the years ;-)
>>> 
>>> What exactly is your concern here?  Having a command that can move
>>> around text in an interactive setting is useful in general, but also not
>>> something that we expect to be upgraded and extended extensively, so
>>> having it stable and complete in core sounds like a good idea to me, as
>>> opposed to a third-party package where the user has to first install it
>>> and then (especially nowadays) be concerned about security risks when
>>> upgrading.  In case you haven't seen it, I'd recommend taking a look at
>>> https://elpa.gnu.org/contributing.html, especially the list of "soft
>>> criteria".
>>> 
>> 
>> If it works well, I'll remove my custom code to do the same.  I also have
>> the package https://melpa.org/#/move-text installed that I'd remove.
>> Perhaps you can compare yours to move-text at the very least as I suspect
>> that's a popular package.
> 
> WDYT Pedro?  There is no hurry to proceed, since Emacs 31 hasn't been
> released yet so there is plenty of time before Emacs 32 comes around,
> but I think that analyzing the current package landscape for a feature
> like this and coming up with a patch along the lines of `indent-rigidly'
> would be a nice addition to the core.