emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-startup-truncated default should be nil [legibility 2/6]
Date: Tue, 04 Feb 2020 01:05:11 -0600	[thread overview]
Message-ID: <87wo92ygrc.fsf@alphapapa.net> (raw)
In-Reply-To: CAMUm490OzKEPONm-qc8tATRF9+71JwFZLXXOeRsaKRKGkqOuhg@mail.gmail.com

Texas Cyberthal <texas.cyberthal@gmail.com> writes:

> #+begin_src elisp
> (org-startup-truncated nil)
> #+end_src
>
> Line truncation is necessary for code but anathema for prose. Prose
> lines need visual wrap as windows resize, so that texts can be
> compared easily.
>
> Advanced Org uses such as large tables require line truncation. Tables
> are a code-like fixed-pitch feature.
>
> Users will write a paragraph of prose longer than the screen well
> before they discover a need for line truncation, such as long lines of
> code or wide tables. Users who need line truncation are likely to know
> about it, whereas users who need line truncation off are unlikely to
> know what it's called.
>
> Learning about line truncation is an unnecessary hurdle for beginners.
> Therefore the default should be nil.

visual-line-mode and toggle-truncate-lines are basic Emacs commands that
all users should learn early.  As well, many users prefer to use filled
paragraphs rather than visual wrapping.  And we shouldn't prioritize
prose above other uses. So this default should probably not be changed.

What would be useful would be if Emacs/Org could be configured to wrap
prose lines but not, e.g. tables and code blocks.  I don't think such
functionality exists in Emacs now, but here's a new package that may be
relevant: https://github.com/luisgerhorst/virtual-auto-fill

As well, it might be good to discuss on emacs-devel whether a feature
could be developed to truncate/wrap lines selectively; maybe
font-locking could be used to apply text properties to disable wrapping
dynamically (assuming that a feature could be developed to wrap based on
a certain text property).  Then we could have the best of both worlds,
and solve an existing problem, viz. that tables and code gets wrapped
when visual-line-mode is enabled.

  reply	other threads:[~2020-02-04  7:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04  4:08 org-startup-truncated default should be nil [legibility 2/6] Texas Cyberthal
2020-02-04  7:05 ` Adam Porter [this message]
2020-02-10  7:00 ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2020-02-04 21:36 Texas Cyberthal
2020-02-04 23:26 ` Samuel Wales
2020-02-05  2:43   ` Texas Cyberthal
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
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

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=87wo92ygrc.fsf@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=emacs-orgmode@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/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).