From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.emacs.devel Subject: Re: word-wrap and wrapping before window-width Date: Wed, 31 Dec 2014 02:56:52 +0000 Message-ID: <87387w8r2j.fsf@violet.siamics.net> References: <87vbl2xigp.fsf@ferrier.me.uk> <83ioh2nlow.fsf@gnu.org> <87sig6xech.fsf@ferrier.me.uk> <83fvc5ni0u.fsf@gnu.org> <87k31fwwyv.fsf@ferrier.me.uk> <87bnmq9ibf.fsf@ferrier.me.uk> <87lhlrx5fc.fsf@building.gnus.org> <878uhrcr5l.fsf@building.gnus.org> <83sifzjflk.fsf@gnu.org> <87egric2ki.fsf_-_@violet.siamics.net> <877fxaa49w.fsf@violet.siamics.net> <831tnicji7.fsf@gnu.org> <83y4pp9dku.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1419994658 6260 80.91.229.3 (31 Dec 2014 02:57:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 31 Dec 2014 02:57:38 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 31 03:57:33 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Y69TW-0007T2-1o for ged-emacs-devel@m.gmane.org; Wed, 31 Dec 2014 03:57:30 +0100 Original-Received: from localhost ([::1]:38971 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y69TU-0005om-Vv for ged-emacs-devel@m.gmane.org; Tue, 30 Dec 2014 21:57:28 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38417) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y69TH-0005oa-Lc for emacs-devel@gnu.org; Tue, 30 Dec 2014 21:57:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y69TG-0004wS-Ea for emacs-devel@gnu.org; Tue, 30 Dec 2014 21:57:15 -0500 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:53249) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y69TG-0004tO-5A for emacs-devel@gnu.org; Tue, 30 Dec 2014 21:57:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=VfC+aM3gsRBAMsYc174y9qrl9WjcGOAk6/mgj5x6kw4=; b=Q5tU2uAA+X2sUT9PbnKReAFNt3rKJyMtgpqyO3qu+deXV/oNFZ4pNLePAFCsJ/LVsJtyS1Mtw6XK9zX445ZTrkIKqJFf7rRVm38p8SOSQe62u5ZpMkfjtUYfnj6idnkdd3VD4kn5F+LiyOaxa9h/xY9HrZWx0a5nXUi8RPoaIJg=; Original-Received: from [2a02:2560:6d4:26ca::1:1d] (helo=violet.siamics.net) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Y69T3-0005NV-5c for emacs-devel@gnu.org; Wed, 31 Dec 2014 02:57:01 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Y69Sv-0005df-8C for emacs-devel@gnu.org; Wed, 31 Dec 2014 09:56:53 +0700 Mail-Followup-To: emacs-devel@gnu.org In-Reply-To: <83y4pp9dku.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 30 Dec 2014 20:50:41 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:4f8:d15:1b86::2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:180897 Archived-At: >>>>> Eli Zaretskii writes: [=E2=80=A6] >> IOW, the wrapping would be window (and hscrolling) independent. We may still want some value to mean =E2=80=9Cwrap at window width, however it is currently set.=E2=80=9D >> And a "truncated line" could then "simply" be a line with an >> "infinite" wrap-column. > I simply fail to see any practical use cases for this kind of > display. What are we trying to support with this? That=E2=80=99d make it easy to display format=3Dflowed (RFC 3676) MIME parts, as well as enriched-mode documents, MediaWiki pages, and pretty much any other kind of text which allows for /both/ wrappable and preformatted parts at the same time. > It's hard to reason about this without having some use cases in mind. For one thing, I edit MediaWiki pages on almost daily basis, and using word-wrap (and wrap-prefix) is more or less a no-brainer here. Occasionally, however, it may be sensible to mark some parts of the buffer (as in: 
,  and
	=E2=80=9Cleading blank=E2=80=9D parts) to use truncation instead of wrappi=
ng.

	Now, to repeat myself, I know very little of the current Emacs
	display implementation.  However, it seems to me that
	wrap-column makes us one property closer to native multicolumn
	display.  Consider, e. g.:

This is an example sentence with wrap-column set to 23.

This is yet another example sentence with line-prefix and wrap-prefix
both set to (space :align-to 25), =E2=80=93 or something like that.

	From there, we may display it as follows:

This is an example
sentence with
wrap-column set to 23.

                         This is yet another example sentence with line-pre=
fix
                         and wrap-prefix both set to (space :align-to 25), =
=E2=80=93
                         or something like that.

	Yet, provided that some other property is switched on, the Emacs
	display engine may decide to show it like this instead:

This is an example       This is yet another example sentence with line-pre=
fix
sentence with            and wrap-prefix both set to (space :align-to 25), =
=E2=80=93
wrap-column set to 23.   or something like that.

	As already imagined in this thread, forward- and backward-char
	commands would then still follow the logical order of text in the
	buffer (that is: the =E2=80=9C23=E2=80=9D sentence, then the =E2=80=9C25=
=E2=80=9D one), while
	left-char, etc. would (under visual-order-cursor-movement) follow the
	visual order.

--=20
FSF associate member #7257  http://boycottsystemd.org/  =E2=80=A6 3013 B6A0=
 230E 334A