unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jaehwang Jerry Jung <tomtomjhj@gmail.com>
Cc: 39517@debbugs.gnu.org
Subject: bug#39517: [PATCH] Add new option 'word-wrap-boundary'
Date: Sun, 09 Aug 2020 13:23:38 +0200	[thread overview]
Message-ID: <87zh74t64l.fsf@gnus.org> (raw)
In-Reply-To: <ee2b6436-d191-bcac-751f-c56a00ee51f9@gmail.com> (Jaehwang Jerry Jung's message of "Wed, 12 Feb 2020 00:43:06 +0900")

Jaehwang Jerry Jung <tomtomjhj@gmail.com> writes:

>>>   Last, but not least, for a contribution this large, we will need you
>>> to assign the copyright to the FSF.  If you agree, I will send you the
>>> form to fill and the instructions to send it.
>>>
>>> Yes, I agree.
>> Form sent off-list.
>>
>> Thanks.
>
> Thanks. I sent the request.

Copyright assignment papers are on file now, I see.  And I think the
feature makes sense -- wrapping on "/" characters, for instance, is
something I think buffers for editing HTML (and the like) would benefit
from.

Eli had some comments about the implementation, though.  Could you spin
a new version of the patch that takes those comments into consideration?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-09 11:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09  7:43 bug#39517: [PATCH] Add new option 'word-wrap-boundary' Jaehwang Jerry Jung
2020-02-09 15:34 ` Eli Zaretskii
2020-02-10 15:36   ` Jaehwang Jerry Jung
2020-02-10 16:10     ` Eli Zaretskii
2020-02-11 15:43       ` Jaehwang Jerry Jung
2020-08-09 11:23         ` Lars Ingebrigtsen [this message]
2020-08-09 14:11           ` Eli Zaretskii
2020-08-09 15:23             ` Jaehwang Jerry Jung
2020-08-09 15:25               ` Lars Ingebrigtsen
2020-08-09 15:44               ` Eli Zaretskii

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=87zh74t64l.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=39517@debbugs.gnu.org \
    --cc=tomtomjhj@gmail.com \
    /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).