From: TEC <tecosaur@gmail.com>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Website revamp?
Date: Thu, 06 Aug 2020 00:00:09 +0800 [thread overview]
Message-ID: <873651f4za.fsf@gmail.com> (raw)
In-Reply-To: <rgeive$4jl$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Maxim Nikulin <manikulin@gmail.com> writes: -- lots of stuff --
Since we're talking about newcomers now, I think there are 2c I
can share.
- I started sliding down the Emacs slope early this year My
- initial use case was Org, as a replacement of Jupyter (I want an
- editor,
not a fancy web page)
- I use Doom. I can say with a great degree of confidence that it
has made the
transition much easier.
- I think the best we can hope for is name the most common /paths/
into Emacs, and
tell the user what they're getting into.
E.g.
Emacs :: the one and only, configure everything from scratch -
know exactly what's going on in your config.
Doom :: Adds a bunch of presets for common tasks, and a bunch of
helper functions/optimisations
Spacemacs :: Features feature-rich functionally 'layers' for
common tasks
Whichever you choose, using a version control system such as [git]
is _highly recommended_. Every now and then you'll accidentally
break something. This allows you to seamlessly roll back.
Hope that's of some interest,
Timothy.
[-- Attachment #2.1: Type: text/html, Size: 1335 bytes --]
next prev parent reply other threads:[~2020-08-05 16:11 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 13:55 Website revamp? TEC
2020-07-30 13:00 ` TEC
2020-07-30 13:20 ` Russell Adams
2020-07-30 13:36 ` Amin Bandali
2020-07-30 14:19 ` TEC
2020-07-30 14:47 ` Bruce D'Arcus
2020-07-30 15:53 ` Amin Bandali
2020-07-30 17:22 ` Russell Adams
2020-07-30 17:57 ` TEC
2020-07-30 19:03 ` Russell Adams
2020-08-01 8:15 ` TEC
2020-08-02 18:08 ` TEC
2020-08-03 5:10 ` Colin Baxter
2020-08-03 5:11 ` TEC
2020-08-03 7:01 ` Colin Baxter
2020-08-03 7:53 ` TEC
2020-08-03 8:03 ` tomas
2020-08-04 5:54 ` Eric S Fraga
2020-08-05 10:17 ` Bo Grimes
2020-08-05 10:26 ` Eric S Fraga
2020-08-05 10:40 ` Bo Grimes
2020-08-05 10:43 ` TEC
2020-08-03 10:54 ` Gustav Wikström
2020-08-04 15:48 ` Maxim Nikulin
2020-08-04 15:53 ` TEC
2020-08-04 16:18 ` Bruce D'Arcus
2020-08-04 16:23 ` TEC
2020-08-04 16:30 ` Bruce D'Arcus
2020-08-05 11:56 ` Maxim Nikulin
2020-08-05 12:03 ` TEC
2020-08-06 11:25 ` Maxim Nikulin
2020-08-06 11:52 ` TEC
2020-08-24 7:43 ` TEC
2020-08-25 10:28 ` Maxim Nikulin
2020-08-25 12:02 ` TEC
2020-08-25 15:09 ` TEC
2020-08-27 16:09 ` Maxim Nikulin
2020-09-01 16:39 ` TEC
2020-09-30 16:24 ` Maxim Nikulin
2020-08-11 15:24 ` Maxim Nikulin
2020-08-04 15:53 ` Bruce D'Arcus
2020-08-04 16:09 ` TEC
2020-08-04 21:43 ` Bo Grimes
2020-08-05 15:24 ` Maxim Nikulin
2020-08-05 16:00 ` TEC [this message]
2020-08-07 5:19 ` David Rogers
2020-08-04 5:59 ` Eric S Fraga
2020-08-04 6:27 ` TEC
2020-08-04 20:44 ` gyro funch
2020-08-24 15:39 ` Maxim Nikulin
2020-07-30 19:40 ` Scott Randby
2020-09-01 16:44 ` TEC
2020-09-01 18:07 ` Tom Gillespie
2020-09-01 18:11 ` Tom Gillespie
2020-09-02 3:48 ` TEC
2020-09-02 2:59 ` TEC
2020-09-04 9:37 ` Bastien
2020-09-05 9:08 ` Martin Schöön
2020-09-05 10:16 ` Colin Baxter
2020-09-07 17:24 ` TEC
2020-09-07 18:13 ` TEC
2020-09-08 5:41 ` Tom Gillespie
2020-09-08 5:49 ` TEC
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=873651f4za.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).