all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: emacs-devel@gnu.org,  Stephen Berman <stephen.berman@gmx.net>
Subject: Re: Upcoming merge of adaptive-wrap
Date: Fri, 26 Jan 2024 09:45:06 +0800	[thread overview]
Message-ID: <875xzgookd.fsf@yahoo.com> (raw)
In-Reply-To: <a43c573a-0af8-4ff4-b2f7-f0ada2309011@gutov.dev> (Dmitry Gutov's message of "Thu, 25 Jan 2024 19:10:18 +0200")

Dmitry Gutov <dmitry@gutov.dev> writes:

> One goes well in hand with the other: more code means more code for
> somebody to maintain.

"Maintain" in this context means "running admin/update-copyright every
year", which task I am more than happy to take on.

> So... your plan it to merge an unmaintained piece of code into master?

"Unmaintained" is a very loaded word.  I would rather describe it as
"working."

But the implications of your sentence aside, that is precisely my plan,
yes.

> If your intention was to contribute fixes, I think you have commit
> access to the ELPA repository.

My intention is to guarantee that this feature is known to the maximum
number of users possible, that it may actually be _useful_, rather than
languishing in ELPA.  I'd been passively searching for such a feature
since the time not filling columns to a reasonable width became popular
with a certain programmer demographic, yet learned of adaptive-wrap from
word-of-mouth, not the package list, gnu-emacs-sources, or the like.

Had it been part of Emacs from the outset (thus documented, mentioned in
NEWS, and so on), it would undoubtedly be less obscure than it is now.



  parent reply	other threads:[~2024-01-26  1:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878r4eqjh8.fsf.ref@yahoo.com>
2024-01-25  1:39 ` Upcoming merge of adaptive-wrap Po Lu
2024-01-25  4:44   ` Adam Porter
2024-01-25 10:01   ` Stephen Berman
2024-01-25 11:32     ` Po Lu
2024-01-25 12:37       ` Eli Zaretskii
2024-01-25 13:15         ` Po Lu
2024-01-26  8:05     ` Kévin Le Gouguec
2024-01-26 10:21       ` Po Lu
2024-01-26 11:26       ` Joost Kremers
2024-01-26 12:40         ` Eli Zaretskii
2024-01-26 13:47           ` Joost Kremers
2024-01-31 19:18             ` Stefan Monnier
2024-02-02  4:41               ` Madhu
2024-02-02  7:22                 ` Eli Zaretskii
2024-01-25 17:10   ` Dmitry Gutov
2024-01-25 20:01     ` Stefan Kangas
2024-01-25 20:11       ` Dmitry Gutov
2024-01-26  1:45     ` Po Lu [this message]
2024-01-26  2:08       ` Dmitry Gutov
2024-01-26  2:22         ` Po Lu
2024-01-26  2:30           ` Dmitry Gutov
2024-01-26  4:03             ` Po Lu
2024-01-27  1:44               ` Dmitry Gutov
2024-01-27  3:58                 ` Po Lu
2024-01-27 16:56                   ` Dmitry Gutov
2024-01-27 22:59                     ` Stefan Kangas
2024-01-28  0:18                       ` [External] : " Drew Adams
2024-01-28  9:02                         ` Michael Albinus
2024-01-28  9:36                           ` Po Lu
2024-01-28 13:03                             ` Dmitry Gutov
2024-01-29  1:56                               ` Po Lu
2024-01-28 15:32                           ` Drew Adams
2024-01-28  9:34                     ` Po Lu
2024-01-28 13:11                       ` Dmitry Gutov
2024-01-28 14:25                         ` Po Lu
2024-01-28 18:01                           ` Dmitry Gutov
2024-01-29  1:55                             ` Po Lu
2024-01-26  1:54     ` Po Lu
2024-01-26  7:50       ` Eli Zaretskii
2024-01-26 10:24         ` Po Lu
2024-01-25 20:05   ` Stefan Kangas

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

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

  git send-email \
    --in-reply-to=875xzgookd.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=dmitry@gutov.dev \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.