Jump to content

Using a Color Scheme with Putty?


Jessica

Recommended Posts

Has anyone ever used a custom color scheme with putty? I am trying to use Solarized, which I use for my Windows text editor, in Putty and vim. vim is working fine, but in Putty now everything is just the plain grey text, none of the other colors are being used. The background is the correct grey and the text is one of the greys in the scheme, but for example when I do ls -a, EVERYTHING is still grey. Is there a trick to getting it to use different colors for different things?

 

https://github.com/brantb/solarized/tree/master/putty-colors-solarized

 

the .reg file

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\****]
"Colour0"="131,148,150"
"Colour1"="147,161,161"
"Colour2"="0,43,54"
"Colour3"="7,54,66"
"Colour4"="0,43,54"
"Colour5"="238,232,213"
"Colour6"="7,54,66"
"Colour7"="0,43,54"
"Colour8"="220,50,47"
"Colour9"="203,75,22"
"Colour10"="133,153,0"
"Colour11"="88,110,117"
"Colour12"="181,137,0"
"Colour13"="101,123,131"
"Colour14"="38,139,210"
"Colour15"="131,148,150"
"Colour16"="211,54,130"
"Colour17"="108,113,196"
"Colour18"="42,161,152"
"Colour19"="147,161,161"
"Colour20"="238,232,213"
"Colour21"="253,246,227"

Link to comment
Share on other sites

Is that relevant? Do you even know what PuTTy is used for? Did I say I was having trouble editing files? I specifically said I did an ls -a, which has nothing to do with EDITING files.

 

Did I ask you how I should do my job? Because I'm pretty sure that JUST YESTERDAY my boss advised me as part of a performance review that I should really become more comfortable using the terminal, since I'm the only one in the office who doesn't know the basic commands at the command line or in vi. So I got a crash course on vi. All I want is for the terminal to be colored the way that I like, because I found it easy on my eyes. This wasn't a question asking SHOULD I use Putty. It was how do I make the colors the ones I'm used to.

 

FWIW, I use prefer to use Windows clients like Textpad or jEdit. However, I haven't yet found a SVN or a CVS GUI client which works as easily as running the commands. So I use putty for my cvs/svn commands. We're converting to Git soon too and so I will to use it for that.

Link to comment
Share on other sites

Yes, Putty is connect to your VPS Via SSH :D

 

I use a lot it alot to install scripts and such, like lamp scripts, php/mysql/nginx via command prompts

 

i didn't mean to come of as rude, i just thought you was editing stuff via command line, and was wondering why, even you said jedit and stuff you edit with as well, so I apologize

 

i was just trying to strike up a conversation >_<

Link to comment
Share on other sites

This is a thread where I am actively trying to get help with a specific issue. Trying to "strike up a conversation" by saying I shouldn't even do the thing I'm trying to do is pretty rude. Make your own thread if you just want to talk about stuff.

Link to comment
Share on other sites

I don't know exactly what that .reg files does to your PuTTy session, but after a quick look on the website I didn't spot any screen shots of ls output. Are you sure it's actually for that? By default I believe the --colour option for ls is disabled. You might want to add an alias in your .bashrc file to ensure it's using them:

 

alias ls='ls --color=auto'

 

You can go a step further and define the colours you want to use yourself (this guy explains how). Although I guess the .reg file could be trying to do that and failing. I'm not sure with PuTTy. We'll see how the alias goes first.

 

i just thought you was editing stuff via command line, and was wondering why

 

I always work within vim. The bog standard set-up isn't great, but the whole purpose of vim is you progressively customise it exactly how you like it. Once you learn the commands and define your own, set-up your colour scheme, add tags, etc. You'd be surprised how fast you can work with it. I've even got a PHP debugger configured so I can step through the code as it executes, add in break points, etc.

Link to comment
Share on other sites

I guess I assumed that it was for that sort of thing - what else would it be for?

Before I ran the .reg file, my ls output was colored, and now it's all the same color.

 

I did the alias and it still is all grey.

 

It's not just ls, it's all commands. Everything is just two colors instead of the multiple colors it was before, or the other colors in the scheme.

Link to comment
Share on other sites

They have a separate one for vim which I setup already and it works, this was completely separate. I may be misunderstanding what it does.

no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.svgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:

 

If this isn't meant to do what I thought I guess I need to figure out how to reverse it, because I definitely don't like the all plain grey :-P

 

Creator's website: http://ethanschoonover.com/solarized

Link to comment
Share on other sites

I'm noticing another grey color...maybe it *is* set up right.

if I don't use the saved session and just log in to the same server, with the Solarized I see two greys. Without it I see green and blue. I guess I want to change which color is used for what.

Edit: for an ls -a command

 

Now to figure out some other commands which I can try to see some varied output lol

Link to comment
Share on other sites

I looked at the author's website to figure out which colors are which

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\*****]
"Colour0"="131,148,150" base 0
"Colour1"="147,161,161" base 1
"Colour2"="0,43,54"	base 03
"Colour3"="7,54,66"	base 02
"Colour4"="0,43,54"	base 03
"Colour5"="238,232,213"	base 2
"Colour6"="7,54,66"	base 02
"Colour7"="0,43,54"	base 03
"Colour8"="220,50,47"	red
"Colour9"="203,75,22"	orange
"Colour10"="133,153,0"	green
"Colour11"="88,110,117"	base 01
"Colour12"="181,137,0"	yellow
"Colour13"="101,123,131"base 00
"Colour14"="38,139,210"	blue
"Colour15"="131,148,150"base 0
"Colour16"="211,54,130" magenta
"Colour17"="108,113,196"violet
"Colour18"="42,161,152" cyan
"Colour19"="147,161,161"base 1
"Colour20"="238,232,213"base 2
"Colour21"="253,246,227"base 3

 

Then changed the base colors (greys) to bright colors. I know Colour0 is plain text and colour2 is background so I left them alone. I repeated that until I figured out the settings I liked. The colors for directories  & files in ls (which I kept using to test it) were colour15 and colour11

 

Link to comment
Share on other sites

We are using vim actually, I just don't know the difference. :)

 

There's quite a few things that vim improves on. Some of the more prominent ones:

[*]Supports common code editor features like syntax highlighting, code folding and indenting

[*]Supports plugins

[*]Supports editing via SSH

[*]Supports editing files in compressed archives

Link to comment
Share on other sites

I'm getting used to using vim, if it didn't have syntax highlighting, I would not even bother. My coworkers all love vim though, and have covered my whiteboard in vim commands. They even have "the mug of vi" with the commands.

 

When I need to get something done fast I'm still using my windows client but I don't particularly MIND using vim when I have the time to remember the commands.

 

It's like anything else, the more you use it the better you get at it,

Link to comment
Share on other sites

Not just the better you get, but the more you begin to customise it. That's the real beauty of vim. They say you should learn/add a new feature every week, and in time you basically build up the perfect IDE for yourself.

 

I find it hard moving to a different editor/IDE though, I'm forever writing ":wq". Even in Word documents.

Link to comment
Share on other sites

I use it sometimes but tbh I'm not some diehard fanboy about it like some people seem to be.  I like keyboard commands and shortcut keys to an extent but IMO being able to use a mouse more...like for highlighting shit...rightclick > context menus are a lot better in many cases and I don't get to do that w/ vim :/

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.