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

Bring up help when trying to indent on a fresh install #7

Closed
chrisdone opened this issue Mar 16, 2012 · 4 comments
Closed

Bring up help when trying to indent on a fresh install #7

chrisdone opened this issue Mar 16, 2012 · 4 comments

Comments

@chrisdone
Copy link
Member

Because there's no default indentation mode (kinda weird but), it'd be nice to bring up the documentation for the indentation modes when the user first tries to indent.

I popped some docs based on the existing docs with a bit more help, into the docstring of an Elisp variable, then based on that you can bring up the describe-variable buffer by default.

Seems like it's helpful to the newbies to Emacs and even the advanced users wouldn't mind. :-)

I can only make one merge request at a time so here's a ticket with some commit references.

@hvr
Copy link
Member

hvr commented Mar 17, 2012

Fyi, you can make more than one pull requests at a time if you use separate "feature branches" for each pull-req...

Seems like it's helpful to the newbies to Emacs and even the advanced users wouldn't mind. :-)

Btw, the documentation style doesn't seem to be inline with the conventions for "customize"-documentation. That kind of explainations would better fit into the info manual (which we need anyway). Don't get me wrong: I'm all for more documentation from within Emacs... It's just that it can be done even better :-)

@chrisdone
Copy link
Member Author

Oh, I didn't even think of that.

@hvr
Copy link
Member

hvr commented Mar 17, 2012

and another thing noteworthy: the pull-req is associated with the branch, even after your pull-request was submitted. This means that if you modify the branch you pull-requested, then the pull-request gets updated as well... that's why it's a good idea to use separate branches than master for pull-requests anyway, so you don't affect the pull-request by accident...

@chrisdone
Copy link
Member Author

I thought the response would be immediate, didn't even think about topic branches. Nevermind. I have far too many small changes to be sticking in separate branches and waiting for people to respond. I'll try to think of another way to approach this.

pheaver added a commit that referenced this issue Mar 20, 2012
Improve printing of hoogle output.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants