From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-startup-truncated default should be nil [legibility 2/6]
Date: Wed, 5 Feb 2020 10:43:26 +0800 [thread overview]
Message-ID: <CAMUm493QsxzyEgZ4sOjiGRoFg8=-Bb1JYYV0vJKSKf3n28VBJQ@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8usgvMbHvXNU-qKu_K5j1OyRh5FxaHfRDjOrW_V1VoZ6Q@mail.gmail.com>
> many users need fully maximized emacs while still having legible paragraph width.
Splitting windows vertically creates narrower columns. Unlike
truncation etc, window management actually is something all noobs must
learn.
Narrower columns can increase reading speed, to a point. But wide
columns aren't actively uncomfortable. It isn't important for noobs to
be fast; they're slow anyway. Reducing disorientation, frustration and
distraction is the priority.
Full width is bad for detailed reading, but it's great for skimming
the document overview. Half width is 80 chars on my primary display.
The default fill column is 70.
It's reasonable to expect users will set font size so that vertical
window split results in a comfortable paragraph width. It's
unreasonable to expect they will hit M-q constantly to refill
paragraphs.
On Wed, Feb 5, 2020 at 7:26 AM Samuel Wales <samologist@gmail.com> wrote:
>
> On 2/4/20, Texas Cyberthal <texas.cyberthal@gmail.com> wrote:
> > Prose should wrap at
> > window's edge
>
> many users need fully maximized emacs while still having legible
> paragraph width.
next prev parent reply other threads:[~2020-02-05 2:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 21:36 org-startup-truncated default should be nil [legibility 2/6] Texas Cyberthal
2020-02-04 23:26 ` Samuel Wales
2020-02-05 2:43 ` Texas Cyberthal [this message]
2020-02-05 3:49 ` Samuel Wales
2020-02-05 4:02 ` Samuel Wales
2020-02-05 4:09 ` Samuel Wales
2020-02-05 15:30 ` Adam Porter
-- strict thread matches above, loose matches on Subject: below --
2020-02-06 2:33 Texas Cyberthal
2020-02-06 6:55 ` Texas Cyberthal
2020-02-06 7:15 ` Fraga, Eric
2020-02-06 9:46 ` Texas Cyberthal
2020-02-06 10:16 ` Fraga, Eric
2020-02-06 10:51 ` Texas Cyberthal
2020-02-06 11:17 ` Fraga, Eric
2020-02-06 12:09 ` Texas Cyberthal
2020-02-06 12:40 ` Fraga, Eric
2020-02-06 21:21 ` Texas Cyberthal
2020-02-06 21:38 ` Fraga, Eric
2020-02-06 23:33 ` Texas Cyberthal
2020-02-07 0:37 ` Corwin Brust
2020-02-07 1:06 ` Texas Cyberthal
2020-02-07 4:27 ` Texas Cyberthal
2020-02-04 4:08 Texas Cyberthal
2020-02-04 7:05 ` Adam Porter
2020-02-10 7:00 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMUm493QsxzyEgZ4sOjiGRoFg8=-Bb1JYYV0vJKSKf3n28VBJQ@mail.gmail.com' \
--to=texas.cyberthal@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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/org-mode.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).