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

Customize spacemacs for terminal usage. #3780

Closed
amosbird opened this issue Nov 12, 2015 · 25 comments
Closed

Customize spacemacs for terminal usage. #3780

amosbird opened this issue Nov 12, 2015 · 25 comments

Comments

@amosbird
Copy link
Contributor

Is there any existing configuration that works appropriately in a ssh terminal?

@cpaulik
Copy link
Contributor

cpaulik commented Nov 12, 2015

What are your problems? I'm working in a ssh terminal in tmux every few days.

@amosbird
Copy link
Contributor Author

Highlights get messed up. Lines repeatedly draw on the screen.

k25nxfcsmy ug5mu xsc e4

@cpaulik
Copy link
Contributor

cpaulik commented Nov 13, 2015

Which theme are you using? Some themes do not define proper terminal colors.

The mutliple lines in the modeline might be related to your font not supporting the unicode symbols used there. Try setting dotspacemacs-mode-line-unicode-symbols nil in your .spacemacs file. There should already be an entry for this variable.

@amosbird
Copy link
Contributor Author

@cpaulik I didn't change theme settings. Which theme should I use?

@cpaulik
Copy link
Contributor

cpaulik commented Nov 13, 2015

spacemacs-dark should look sane. material and material-light also have terminal colors setup (I know because I develop them). See if one of those looks good in your terminal. Then you can look for one you like with SPC T h.

@amosbird
Copy link
Contributor Author

I've tested spacemacs-dark, spacemacs-light, solarized-dark, solarized-light, they all looked exactly the same to me. I'm using XShell on Windows.

@cpaulik
Copy link
Contributor

cpaulik commented Nov 13, 2015

They should definitely not look the same. I can try XShell when I get to work later. No Windows PC at home.

@StreakyCobra
Copy link
Contributor

What the value of $TERM in the shell just before you run emacs?

@cpaulik
Copy link
Contributor

cpaulik commented Nov 13, 2015

I just tried with XShell. I connected to my linux machine using ssh and started emacs -> no colors. Doing export TERM=xterm-256color solved the color issue for me. For a font you could try installing one of the powerline fonts for windows. But I have no idea about the windows support. The [hack][http://sourcefoundry.org/hack/) font should also include the necessary symbols.

@amosbird
Copy link
Contributor Author

@cpaulik Which Xshell's theme do you use?

@amosbird
Copy link
Contributor Author

I've set dotspacemacs-mode-line-unicode-symbols nil and export TERM=xterm-256color. Themes do look better. However there are still drawing issues, and pop-up window looks weird.
daw9h6 1n 17 hf1 j tnh

@cpaulik
Copy link
Contributor

cpaulik commented Nov 13, 2015

@amosbird I don't use a special theme

@syl20bnr
Copy link
Owner

@amosbird what is your terminal emulator ? urxvt has this behavior on my side, the more I use urxvt the less I find it pleasant.

@amosbird
Copy link
Contributor Author

@syl20bnr I'm using CentOS 6 via XShell on Windows. XShell's terminal is set to xterm with UTF-8 support.

@jrhorn424
Copy link

I'm seeing color issues running screen-256color.

fullscreen_11_18_15__16_18

I'd prefer not to use a cocoa version of emacs.

@cpaulik
Copy link
Contributor

cpaulik commented Nov 18, 2015

@jrhorn424 I think this is just an issue with the solarized theme spacemacs uses. See also #1269 (comment)

@cpaulik
Copy link
Contributor

cpaulik commented Nov 18, 2015

See also bbatsov/solarized-emacs#18

@jrhorn424
Copy link

Thanks @cpaulik. Looks like the information on this is a bit distributed. 😉

@VMatrix1900
Copy link

Same Problem when using Spacemacs on Bash On Ubuntu on Windows 10. Lines redraw. Even in spacemacs-dark theme. Any fixes?

@fruitraccoon
Copy link

I know this issue has been closed, but I see the same behaviour as @VMatrix1900 - the rending doesn't seem to work correctly in a Bash On Ubuntu On Windows 10 terminal. But interestingly, running Spacemacs inside the terminal in VS Code does work properly. Go figure...

@VMatrix1900
Copy link

VMatrix1900 commented Apr 25, 2017

@fruitraccoon The terminal in VS Code is connected to Bash On Ubuntu On Windows 10? I use several different Terminal emulator ssh into the Bash On Windows such as MobaxTerm, Putty etc. Same problem.

@fruitraccoon
Copy link

fruitraccoon commented Apr 25, 2017

@VMatrix1900 In VS Code, I just use the Terminal: Select Default Shell and I get to choose from Cmd, PowerShell, WSL Bash and Git Bash. Selecting WSL Bash, I can then use emacs in the terminal and it seems to render correctly, and seems to support 256 colours.

I havn't tried the other terminal emulators you mention, but what I have just tried:

  • Bash on Ubuntu on Windows: This doesn't render correctly - lines overwrite each other, etc.
  • Cmd: running bash -c emacs seems to work!
  • Powershell: running bash -c emacs doesn't have the rendering issue, but unicode doesn't seem to be supported (haven't dug into why) (Update: this seems to be due to the font I had, but changing to a font with unicode support then failed to render like the Bash on Ubuntu window does)

So VS Code and Cmd seem to work for me, but Bash on Ubuntu on Windows and Powershell don't.

Hope this helps!

@VMatrix1900
Copy link

@fruitraccoon I tried Cmd and Powershell, it's not working for me. Besides the line rendering issue. Bash On Windows 10 doesn't support solarized theme. So I given up and wait for the stable release of Bash On Windows 10

@kamasylvia
Copy link

Same problem on Ubuntu 18.04 WSL.

2019-02-09_06-59-57

@sc0ttwad3
Copy link

I haven't had a problem running Spacemacs in Microsoft Terminal...WSL2/Ubuntu-18.04. Have you tried that?

Spacemacs-WSL

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

9 participants