-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorial for new users #773
Comments
Something I found it could be useful:
|
What is a Linux? /s In all seriousness, this could be very useful for new coders and new Emacs Users / Converts alike. |
I took chrisbarrett's outline from syl20bnr#773 and filled in some details.
I've started a VIMUSERS.md file in aa4cbff that's aimed at filling in chrisbarrett's outline. I don't want to cover any advanced topics like creating config layers since that's for users who are already comfortable with spacemacs. I'm a hardcore vim user who's trying out spacemacs and this tutorial is mostly stuff that confused or annoyed me. Hopefully the differences section can eventually be limited to the Differences in defaults. Eventually, I want to have a "common vim changes" section that covers stuff in tpope/vim-sensible or that's recommended in vim help. |
@idbrii I'm impressed by this draft, it is very valuable, not only it will save a lof of time for vim user but it points them into the right directions to use spacemacs effectively right from the beginning. 👍 |
Something that might be useful:
|
I took chrisbarrett's outline from syl20bnr#773 and filled in some details.
Are these now covered by current docs / Vim Users Guide ? @person808 @TheBB |
VIMUSERS.org has all of this. I think the regular docs have it too. |
This
It's a big – but nice – beginner friendly work |
You have my blessing. 👍 |
I thing that in the tutorial something about closing windows and moving around should be included :) |
I learned heaps within the past few months |
Two opinions (feel free to ignore them): This document is more useful if it *is *specific to vim users since they Making QUICK_START.org bigger will make it no longer quick. It's probably -David On Sat, Nov 14, 2015 at 11:17 AM, Fabien Dubosson notifications@github.com
|
Ok, maybe a short quick start file, as it is now, is needed. But there is a documentation missing between the quick-start and the full documentation. Something explaining the basic concepts of The If we omit the So the point 2) of my previous list can be discussed (but still, I'm not sure the current quick start document is useful at all). Otherwise point 1) and 3) are not going to change anything for vim users, and it will even be better as it will make this document more visible :-) |
I'm starting out right now, coming from using Sublime Text. If you want I could mention questions I have as I'm learning, as well as solutions I find. |
@JuanCaicedo that'd be nice |
I started jotting down my questions in this gist. I'll add answers as I find them, but feel free to comment with answers or additional questions! |
|
Also point them to evil tutor and explain what evil/holy/hybrid modes are. Point them to |
👍 |
The funny thing is - now there is a section about evil-tutor in the documentation https://github.com/syl20bnr/spacemacs/blob/master/doc/QUICK_START.org , but not a single word about a normal tutor. I do remember there was an emacs tutorial, but I have no idea how to bring it up. Could please someone help? |
@achikin Do you mean |
What I think is that we can provide a tutorial in a sandbox where pressing any key will be interactive. We can start with a blank screen by showing only the minibuffer and ask the user to press any key to continue. Then each UI component will be slowly unwrapped and its use will be printed somewhere either a tooltip or using the minibuffer or the actual buffer. Using hydra in this tutorial looks like a good option. The basic key presses with which-key and getting into the documentation are very much useful too. We will just guide the user till the end. We can provide them to write sample code during the walk-through. If we don't sandbox then it is for sure overwhelming for a new user. There can also be a point where they can pause and use actual spacemacs and resume on demand. Have different checkpoints so that they can jump straight to what they want to know. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
We should have a tutorial so that first-time users can learn how to customise spacemacs. We should cover at least the following:
.spacemacs
use-package
Any other stuff we should cover?
I think it would be cool if we host the tutorial inside Emacs. We could run the tutorial after startup if
~/.spacemacs
doesn't exist.The text was updated successfully, but these errors were encountered: