From: Spencer Baugh <sbaugh@janestreet.com>
To: emacs-devel@gnu.org
Subject: Re: adaptive-wrap
Date: Mon, 07 Aug 2023 16:40:27 -0400 [thread overview]
Message-ID: <ier350u60xw.fsf@janestreet.com> (raw)
In-Reply-To: 83h6paol00.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Mon, 07 Aug 2023 12:01:51 -0400
>>
>> This would be nice in combination with some kind of dynamic
>> line-wrapping which simulates joining lines. Then comments would
>> appear as if they've been filled to the screen width, no matter what
>> the actual fill-column and screen width is. Which would be nice on
>> small displays.
>>
>> By dynamic word-wrapping I mean something which would display:
>>
>> foo foo foo foo foo foo foo
>> foo foo foo foo foo foo foo
>>
>> as
>>
>> foo foo foo foo foo
>> foo foo foo foo foo
>> foo foo foo foo
>>
>> on a 20-character width display. Instead of the default display
>> behavior:
>>
>> foo foo foo foo foo
>> foo foo
>> foo foo foo foo foo
>> foo foo
>
> Dynamic wrapping is incompatible with hard newlines. Don't use
> newlines except between paragraphs, and word-wrap we have in Emacs
> will do what you want.
But of course that is not the style used for comments in the Emacs
codebase (and most others); most programmers hard-wrap their text with
hard newlines to comply with line length limits.
next prev parent reply other threads:[~2023-08-07 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874jlc7ifu.fsf.ref@yahoo.com>
2023-08-06 7:12 ` adaptive-wrap Po Lu
2023-08-06 7:20 ` adaptive-wrap Eli Zaretskii
2023-08-06 7:24 ` adaptive-wrap Po Lu
2023-08-07 16:01 ` adaptive-wrap Spencer Baugh
2023-08-07 16:49 ` adaptive-wrap Eli Zaretskii
2023-08-07 20:40 ` Spencer Baugh [this message]
2023-08-08 10:59 ` adaptive-wrap Eli Zaretskii
2023-08-07 16:50 ` adaptive-wrap Ihor Radchenko
2023-08-07 20:42 ` adaptive-wrap Spencer Baugh
2023-08-10 5:37 ` adaptive-wrap Po Lu
2023-08-09 17:34 ` Pixel Fill + Justify Madhu
2023-08-10 7:12 ` 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=ier350u60xw.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=emacs-devel@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).