From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-startup-truncated default should be nil [legibility 2/6]
Date: Thu, 6 Feb 2020 17:46:21 +0800 [thread overview]
Message-ID: <CAMUm491zXKCc_HR_nBOV_3UG+0dYE8G8OWk5S=Yo1vHYO2rSZQ@mail.gmail.com> (raw)
In-Reply-To: <87wo905gpe.fsf@ucl.ac.uk>
auto-fill-mode definitely isn't what I want. Beyond that I don't
understand your question.
I doubt it's productive to reiterate my legibility critiques since
I've concluded they're more appropriate for Spacemacs.
> the solution may simply be some example org mode hooks with, say, settings for writing prose and have these in the org mode manual?
Sounds like a step in the right direction.
It sounds like vanilla Emacs' primary mission is to be the common
component between all configurations, and to be by the devs and for
the devs. Greybeard compatibility is big due to the proliferation of
heavily individualized configs. It can be user-friendly for dev noobs
but not normie noobs.
In that light, leaving Org's defaults no different than an IDE's makes sense.
That leaves Spacemacs being to vanilla Emacs as Ubuntu is to Debian.
Spacemacs is crowd-configured and vanilla Emacs isn't.
It doesn't make sense for vanilla Emacs to be more normie-noob
friendly than Spacemacs, so I feel most of my Org legibility
suggestions should be implemented on Spacemacs before vanilla, if at
all.
Vanilla documentation incompatibility due to distro drift isn't as bad
as I thought, thanks to Emacs being self-documenting. I think I can
construct a decent normie-noob adoption funnel in Spacemacs, based off
the tutorial, friendly defaults, and probably a tutorial layer. In
other words, create the equivalent of Ubuntu Mint.
Once someone starts living in Emacs, they'll eventually reach sage
status. It's just a matter of easing them in.
On Thu, Feb 6, 2020 at 3:16 PM Fraga, Eric <e.fraga@ucl.ac.uk> wrote:
>
> On Thursday, 6 Feb 2020 at 10:33, Texas Cyberthal wrote:
> > Visual line mode is annoying and unnecessary; Spacemacs users do not
> > need it because its defaults offer adequate paragraph navigation.
>
> I'm not sure I understand the conflation of visual-line-mode with
> paragraph navigation. Is it because you mean intra-paragraph navigation
> as opposed to M-{ and M-} for navigating from paragraph to paragraph?
>
> Maybe auto-fill-mode is what you want?
>
> In any case, the solution may simply be some example org mode hooks
> with, say, settings for writing prose and have these in the org mode
> manual?
>
> Fundamentally, emacs is challenging because it is both powerful and
> completely customizable. I remember a colleague complaining that Linux
> was not friendly because you had too much choice. Emacs takes that to
> another level. And that's why many of us live in it...
> --
> : Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-233-gc2bc48
next prev parent reply other threads:[~2020-02-06 9:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 2:33 org-startup-truncated default should be nil [legibility 2/6] Texas Cyberthal
2020-02-06 6:55 ` Texas Cyberthal
2020-02-06 7:15 ` Fraga, Eric
2020-02-06 9:46 ` Texas Cyberthal [this message]
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
-- 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-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='CAMUm491zXKCc_HR_nBOV_3UG+0dYE8G8OWk5S=Yo1vHYO2rSZQ@mail.gmail.com' \
--to=texas.cyberthal@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).