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

Make scratch buffer major mode configurable #4424

Closed
wants to merge 1 commit into from

Conversation

TheBB
Copy link
Contributor

@TheBB TheBB commented Jan 5, 2016

Fix #690.

@StreakyCobra
Copy link
Contributor

(switch-to-buffer (get-buffer-create "*scratch*")))

@TheBB
Copy link
Contributor Author

TheBB commented Jan 5, 2016

Thanks. Better now?

@TheBB
Copy link
Contributor Author

TheBB commented Jan 5, 2016

Persp-mode won't let me delete the scratch buffer to check...

@StreakyCobra
Copy link
Contributor

Tested by excluding persp-mode. It works 👍

@choppsv1
Copy link
Contributor

choppsv1 commented Jan 8, 2016

Would be nice to get this merged as it's hard to work around it not being there. :)

@choppsv1
Copy link
Contributor

FWIW I think making this text mode by default is misguided. I tested load times and didn't see much if any difference with lisp interaction mode. Additionally from the emacs manual:

When Emacs starts up, it contains a buffer named scratch, which is provided for evaluating Emacs Lisp expressions interactively. Its major mode is Lisp Interaction mode. You can also enable Lisp Interaction mode by typing M-x lisp-interaction-mode.

@syl20bnr
Copy link
Owner

@choppsv1 We cannot guess the major mode for the user so we make it as generic as possible by default, I believe this is the saner default.

@TheBB Thank you ! Released in 0.105.7 👍

@syl20bnr syl20bnr closed this Jan 11, 2016
@choppsv1
Copy link
Contributor

Sylvain Benner notifications@github.com writes:

@choppsv1 We cannot guess the major mode for the user so we make as generic as possible by default, I believe this is the saner default.

But, you don't have to guess at what to set it to! It's documented in
the manual as "the lisp-interaction-buffer". What we're doing here is
changing it so it violates the documentation. Why?

@TheBB TheBB deleted the scratch-config branch January 11, 2016 13:05
@syl20bnr
Copy link
Owner

I don't agree with reducing the scratch buffer to lisp interaction by
default, it is even elisp interaction buffer in this case. The term
scratch is too general and the usage of Emacs too wide to reduce it to
elisp.

But all this discussion diverged from the main reason why it is text-mode
by default in Spacemacs, this is to avoid loading too much stuff at startup.

Le lundi 11 janvier 2016, Christian Hopps notifications@github.com a
écrit :

Sylvain Benner <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> writes:

@choppsv1 We cannot guess the major mode for the user so we make as
generic as possible by default, I believe this is the saner default.

But, you don't have to guess at what to set it to! It's documented in
the manual as "the lisp-interaction-buffer". What we're doing here is
changing it so it violates the documentation. Why?


Reply to this email directly or view it on GitHub
#4424 (comment).

-syl20bnr-

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

Successfully merging this pull request may close these issues.

4 participants