From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: Corwin Brust <corwin@bru.st>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"Fraga, Eric" <e.fraga@ucl.ac.uk>
Subject: Re: org-startup-truncated default should be nil [legibility 2/6]
Date: Fri, 7 Feb 2020 09:06:32 +0800 [thread overview]
Message-ID: <CAMUm493U8Ynwd0AEKNm802bd_irWmgU2TB7OAguqyRkBGQm=_w@mail.gmail.com> (raw)
In-Reply-To: <CAJf-WoTqZbkJAUr_BMKmct_O_V6CPmjGBXGzYfRBt0JW6OoN_g@mail.gmail.com>
That's a great idea. And if the Org tutorial included an easy option
to enable "PIM" mode for normie-noobs, so that Emacs starts behaving
like a PIM instead of an IDE, that would be even better. Someone who's
never coded before doesn't need IDE defaults.
On Fri, Feb 7, 2020 at 8:37 AM Corwin Brust <corwin@bru.st> wrote:
>
> Greetings,
>
> On Thu, Feb 6, 2020 at 5:33 PM Texas Cyberthal <texas.cyberthal@gmail.com> wrote:
>>
>> No, that isn't what I'm saying. I'm quite happy with Emacs, especially
>> Spacemacs. However, I had a much harder adoption experience than
>> necessary, and I find that the barriers to entry are preventing
>> normie-noobs from choosing Org as a PIM. So I intend to fix that.
>
>
> I'm not sure this is on-topic, but... what about creating a separate tutorial just org-mode?
>
> The possibilities seem endless but, for example, this could
> * provide instruction for different primary use cases (for me: note-taking, prose, agenda, habit, babel, and literature)
> * mention especially important customizations for the given usage
> * offer "express setup" buttons to instantly apply settings from a sample configuration.
>
> Finally, this could be added into the Emacs splash-screen alongside the general tutorial.
>
> I like the idea of promoting org-mode to people using Emacs for the first time and I like the idea of sensible defaults, especially that reduce frustrations for users new to the GNU tool-chain That said, org-mode is lots of things to lots of people, even notwithstanding the reticence to break things for people who've had them working the way the like for decades. I think this is fundamentally an education problem. But even if that's wrong, I think we should look closely at education as a solution.
>
> --
> Corwin
> 612-217-1742
> 612-298-0615 (fax)
> 612-695-4276 (mobile)
> corwin.brust (skype)
> corwin@bru.st
next prev parent reply other threads:[~2020-02-07 1:07 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
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 [this message]
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='CAMUm493U8Ynwd0AEKNm802bd_irWmgU2TB7OAguqyRkBGQm=_w@mail.gmail.com' \
--to=texas.cyberthal@gmail.com \
--cc=corwin@bru.st \
--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).