smile13241324 on develop
Fix missing implicit dependency… (compare)
smile13241324 on develop
Revert "Revise python layer" R… (compare)
spacemacs-ui-visuallayer seems to provide the toggles for this etc
fci-modeis not something you really want globally, you'll probably want to add exceptions for certain modes like on that wiki page
spacemacs-ui-visualtakes a bunch of togglable things and adds spacemacsy commands to toggle them... but it doesn't define global toggles if they don't exist, like in this case
SPC b .
pto cycle through and
SPC b b
ivy-switch-buffersalso has the option to kill
ka buffer from the actions list:
Emacs 26.3 in Windows 1903 says that I'm using the font:
name (opened by): -outline-Source Code Pro-normal-normal-normal-mono-13----c--iso8859-1
full name: Source Code Pro-10.0
C-h v fallback-font-name variable says:
fallback-font-name’s value is "MS Gothic"
fallback-font-name2 variable says:
fallback-font-name2’s value is "Lucida Sans Unicode"
Emacs 26.3 in PopOS 19.10 says:
name (opened by): -ADBO-Source Code Pro-normal-normal-normal--13----m-0-iso10646-1
full name: Source Code Pro:pixelsize=13:foundry=ADBO:weight=normal:slant=normal:width=normal:spacing=100:scalable=true
file name: /home/username/.fonts/SourceCodePro-Medium.ttf
fallback-font-name’s value is "NanumGothic"
fallback-font-name2’s value is "NanumGothic"
Since you just started, I suggest that you switch to the
develop branch, it's the recommended branch until the next version is released (I don't know when that is).
It's way ahead of the
If you've already got a working setup, back it up first. Then make sure that you don't have a
.emacs.d directory or a
.spacemacs file in your home directory and clone directly to the
develop branch with:
git clone -b develop https://github.com/syl20bnr/spacemacs ~/.emacs.d
Hey spacemacsers :) could someone point me in the right direction/best practice on how to customize packages that are eiter a. part of spacemacs (bootstrap), or b. part of other layers?
Let's say I wanna customize the hydra package, which according to configuration-layer/describe-package is part of spacemacs-bootstrap, or just build different hydras. Do I add that configuration in .spacemacs in dotspacemacs/user-config, or is it a better practice to move those to private layers if the customizations and code is extensive? If so, how do I correctly refer to built-in/packages in another layer correctly?
I've created a layer to move additional packages (and their configuration) away from .spacemacs, but I guess that can be done for the built ins as well?
Let's say I put "hydra" in the package list of that layer (defconst miscshit-packages ....) (the layer is called miscshit) and then create a (defun miscshit/init-hydra () to start the use-package etc., will that mess up stuff defined in other layers?
(a bit confused as to what goes where, examples or pointers would be great...)