Skip to content
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

Add a spacemacs dotfile documentation section #43

Closed
syl20bnr opened this issue Oct 27, 2014 · 5 comments
Closed

Add a spacemacs dotfile documentation section #43

syl20bnr opened this issue Oct 27, 2014 · 5 comments

Comments

@syl20bnr
Copy link
Owner

No description provided.

@Olical
Copy link
Contributor

Olical commented Oct 28, 2014

Any more thought on keeping the readme documentation really minimal and placing most of it within an interface in Emacs? Maybe something that can be filtered with helm :)

I really think the readme will make a good installation and getting started guide, but documentation within Emacs will be the best route for everything else.

@syl20bnr
Copy link
Owner Author

@Wolfy87 I'm glad that you propose such an interface, it makes issue #4 even more relevant. The initial idea is to have a helm buffer with a list of all packages installed or available classified by layers in helm groups.

+1 for keeping the readme straight to the point.

What do you think about litterate programming in packages.el files ? We can add usefull notes we can publish and keep the code speak for itself for the rest.

@trishume
Copy link
Contributor

Literate programming sounds ok to me as long as it is the type that uses comments rather than fancy org-mode files and tangle/weave. I tried out a config that was based on org-mode-babel literate config files, the extra processing step caused some problems and made the whole thing harder to understand.

Also instead of a fancy spacemacs-specific helm docs thing, couldn't we use the builtin emacs doc system (apropos is it?) and interface helm with that?

@syl20bnr
Copy link
Owner Author

Agree on both arguments, my only concern with literate programming is that it makes to code more heavy and hard to read, especially with org indeed.

@Wolfy87 proposed to have our own man system, and you are right to suggest apropos. This is the way to go.

@syl20bnr
Copy link
Owner Author

Spacemacs doc integration into apropos is tacked by #48.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants