unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 9286@debbugs.gnu.org, cyd@stupidchicken.com, handa@m17n.org,
	jidanni@jidanni.org, 34463@debbugs.gnu.org
Subject: bug#9286: fill-paragraph destroys URLs
Date: Thu, 10 Oct 2019 10:43:07 +0300	[thread overview]
Message-ID: <8336g1t59w.fsf@gnu.org> (raw)
In-Reply-To: <87blupzh41.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  10 Oct 2019 00:30:54 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 10 Oct 2019 00:30:54 +0200
> Cc: 34463@debbugs.gnu.org, jidanni@jidanni.org, Kenichi Handa <handa@m17n.org>,
>  9286@debbugs.gnu.org
> 
> > This is because line joining does not include a space if *either*
> > character on each side of the newline has the ?| (line-breakable)
> > category and an entry in fill-nospace-between-words-table.  To get the
> > behavior jidanni wants, we could change it so that *both* the characters
> > must have this property; see attached patch.
> >
> > But I am not sure this is TRT in general.  Handa-san, could you weigh in
> > with an opinion?  Adding a space seems more or less correct to me, but I
> > am no expert.
> 
> This problem is still present in Emacs 27.  This patch, from 2011, was
> never applied.  I think Chong's proposal sounds logical, but like him,
> I'm (ahem) no expert.

Since Kenichi didn't respond, I think we should study what the Unicode
Line-breaking Algorithm has to say about that.  Can you look there for
relevant guidance?  We don't yet implement the complete algorithm, but
some of what they say could nevertheless be used to resolve this
issue.

Thanks.





  reply	other threads:[~2019-10-10  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 21:25 bug#9286: fill-paragraph destroys URLs jidanni
2011-08-20 19:58 ` Chong Yidong
2019-10-09 22:30   ` Lars Ingebrigtsen
2019-10-10  7:43     ` Eli Zaretskii [this message]
2019-10-11  6:58       ` bug#34463: " Lars Ingebrigtsen
2019-11-23 14:00         ` Lars Ingebrigtsen
2011-08-20 20:04 ` jidanni

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=8336g1t59w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34463@debbugs.gnu.org \
    --cc=9286@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=handa@m17n.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    /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).