-
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
Make *scratch* Emacs LIsp by default #690
Comments
if it starts as emacs-lisp I think the startup would be much larger, because it has to load everything that comes to it..flycheck, w/e |
Currently when
|
Why should I make it emacs-lisp ? If I'm a clojure programmer and don't hack lisp or don't hack lisp very often it makes no sense for me, I would prefer it to be in clojure-mode. I cannot impose what scratch buffer must do to the user, moreover it makes the load time to increase as @CestDiego mentioned. Setting the scratch buffer to a specific major-mode other than text is a user preference and should be set in the dotfile. We can improve the documentation on this point with a scratch section. |
For the bug you can open an issue, it is not related to scratch buffer. |
The bug was caused when I was working with my C/C++ layer. It's fine now. And yes, I think there should be documentation about the scratch buffer behavior. It is because I use scratch buffer frequently to test Elisp code, so when Spacemacs surprised me when the scratch buffer is in text-mode. |
I reopen it to track the update to the documentation. |
Close syl20bnr#690 Close syl20bnr#1206 Close syl20bnr#1269 Close syl20bnr#1504 Close syl20bnr#1742 Correct syl20bnr#3839
Putting the following snippet: (setq initial-major-mode 'ruby-mode) in |
I don't like duplication of existing variables, that's why it would be nice to make sure that it's possible to configure existing variable. But if it's not really possible to make it safe - I don't mind having What I fear is that if we want to support any major mode in scratch buffer - we should set it after layers are initialised. Things that should be tested:
|
You're right, we should make possible for user to customize it. Definitively not "Beginner Friendly" anymore :-) |
Can we add a mechanism to revisit the scratch buffer after |
@tuhdo, what solved the issue with the |
https://github.com/sschuldenzucker I do too… kind of annoying, not being able to make a mistake in a text editor… |
I'm OK with an additional dotspacemacs variable for the scratch buffer, seems required here. |
I am also getting the |
It's now configurable in master. Closing. |
@syl20bnr We shouldn't change it to
Text
. I guess it is because you want*scratch*
to be something to temporary store text. However, we can always create a new temporary buffer by entering non-existent buffer name. Otherwise this behaviour should be documented.The text was updated successfully, but these errors were encountered: