From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: itai.berli@gmail.com, 27525@debbugs.gnu.org
Subject: bug#27525: 25.1; Line wrapping of bidi paragraphs
Date: Thu, 06 Jul 2017 19:17:49 +0300 [thread overview]
Message-ID: <83h8ypmtea.fsf@gnu.org> (raw)
In-Reply-To: <E1dT9Dq-0000RY-5P@fencepost.gnu.org> (message from Richard Stallman on Thu, 06 Jul 2017 12:01:42 -0400)
> From: Richard Stallman <rms@gnu.org>
> CC: itai.berli@gmail.com, 27525@debbugs.gnu.org
> Date: Thu, 06 Jul 2017 12:01:42 -0400
>
> > Then maybe I don't understand what you meant by "fill". This feature
> > produces exactly the same display as M-q, but it doesn't insert
> > newline characters into the buffer.
>
> That isn't what I saw. What I saw is that it split individual lines
> but didn't recombine them.
Oh, you expected Emacs to remove the hard newlines as part of the
feature? That's right, it doesn't do that, and neither do the other
editors. They only remove "soft" newlines, and Emacs does that as
well. Removing hard newlines would be a misfeature, IMO, since in
this mode they are user-controlled, and Emacs has no business
second-guessing the user.
> My Emacs sources are from December, If this doesn't fail for you,
> maybe it has been fixed since then.
No, what you see is how it's supposed to work.
next prev parent reply other threads:[~2017-07-06 16:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 7:23 bug#27525: 25.1; Line wrapping of bidi paragraphs Itai Berli
2017-06-29 14:55 ` Eli Zaretskii
2017-06-29 18:35 ` Itai Berli
2017-07-04 9:10 ` Itai Berli
2017-07-04 9:11 ` Itai Berli
2017-07-04 9:19 ` Itai Berli
2017-07-04 14:43 ` Eli Zaretskii
2017-07-04 14:52 ` Itai Berli
2017-07-04 15:19 ` Eli Zaretskii
2017-07-04 23:05 ` Richard Stallman
2017-07-05 2:29 ` Eli Zaretskii
2017-07-05 22:59 ` Richard Stallman
2017-07-06 2:39 ` Eli Zaretskii
2017-07-06 16:01 ` Richard Stallman
2017-07-06 16:17 ` Eli Zaretskii [this message]
2017-07-07 18:23 ` Richard Stallman
2017-07-07 19:21 ` Eli Zaretskii
2017-07-09 18:17 ` Benjamin Riefenstahl
2017-07-09 18:30 ` Eli Zaretskii
2017-07-19 8:50 ` Itai Berli
2017-07-19 12:59 ` Itai Berli
2017-07-19 17:28 ` Eli Zaretskii
2017-07-19 21:40 ` Itai Berli
2017-07-20 5:08 ` Eli Zaretskii
2017-07-20 7:01 ` Itai Berli
2017-07-20 11:09 ` Eli Zaretskii
2017-07-21 6:19 ` Itai Berli
2017-07-21 8:37 ` Eli Zaretskii
2017-07-21 9:44 ` Itai Berli
2017-07-21 10:58 ` Itai Berli
2017-07-21 13:19 ` Eli Zaretskii
2017-07-21 13:01 ` Eli Zaretskii
2017-07-19 17:24 ` Eli Zaretskii
2017-07-04 14:40 ` 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=83h8ypmtea.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27525@debbugs.gnu.org \
--cc=itai.berli@gmail.com \
--cc=rms@gnu.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).