emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Samuel Wales <samologist@gmail.com>
To: Texas Cyberthal <texas.cyberthal@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Prose with markup needs more line spacing [legibility 5/6]
Date: Tue, 4 Feb 2020 16:17:21 -0700	[thread overview]
Message-ID: <CAJcAo8vsU_G7GitLx1OAWeBP9pbWCucb1PPHwbRHuWGv4TbRag@mail.gmail.com> (raw)
In-Reply-To: <CAMUm492NJALMdkKAP9HKKMTqC7Dnd+FpjTxtUdbJQfBsAAqyQA@mail.gmail.com>

i get some of your points in these emails.

i'd sure like to change physical indentation in org to don't.

and i think newcomers and advanced alike might want to have org sub
superscript be off by default.  one user on this list recently
exported a signature that contained a version number that got mangled!

===

however, as an example of unintended consequences, line-spacing is a
fundamental thing i'd be leery of changing.

for one thing, it's a big problem to reduce number of lines on screen.
many users use large fonts and are struggling to make use of the
number of lines available even on the largest screens.

i think the user would have trouble noticing that it is possible to fix.
it might look like "part of the font".

even advanced users might not know about line spacing.  faces and
display stuff are pretty complex in emacs.  powerful, but complex.

add the annoyances a user who requires large fonts has to deal with already.

on top of that the question of what to do with partial lines at end of
window -- is scrolling idempotent?  or whatefer the correct math term
for "you do a and the opposite of a and you get what you had before"
is.  could cuase issued before being notices.

and that's before differences of opinion on aesthetics.  :)

===

but scoping out to your campaign in general, i wonder why some of your
proposals are for org.  some things might be good for text mode in
general.  or outline mode.  or fundamental mode.  if we make them only
for org, they might be nih-ish or inconsistent.

emacs users can get curmudgeonly.  don't let that stop you.  but
please remember to try to falsify your hypotheses.

next prev parent reply	other threads:[~2020-02-04 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 22:07 Prose with markup needs more line spacing [legibility 5/6] Texas Cyberthal
2020-02-04 23:17 ` Samuel Wales [this message]
2020-02-05  2:27   ` Texas Cyberthal
2020-02-10  7:11   ` Bastien
2020-02-10 19:58     ` Samuel Wales
2020-02-10 21:52       ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2020-02-04  4:10 Texas Cyberthal
2020-02-04  7:32 ` Adam Porter
2020-02-10  7:07 ` 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=CAJcAo8vsU_G7GitLx1OAWeBP9pbWCucb1PPHwbRHuWGv4TbRag@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=texas.cyberthal@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

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).