This is my Slackware desktop...

TobiSGD · 07-19-2012, 08:56 PM

Quote:

Originally Posted by eXpander_

Pure Fluxbox:

http://fc01.deviantart.net/fs71/f/20...rx-d5809ub.png

That's a nice one.
Now you have to look into the code for wicd and your power-manager to change the color of their indicator bars to something other than green.

eXpander_ · 07-19-2012, 08:59 PM

Quote:

Originally Posted by TobiSGD

That's a nice one.
Now you have to look into the code for wicd and your power-manager to change the color of their indicator bars to something other than green.

Hehe thx, I was too lazy for that

Muraii · 07-20-2012, 03:11 AM

Quote:

Originally Posted by dugan

Seriously? You use the official .Xresources file and add a third party Solarized .dir_colors file.

Screenshot: http://duganchen.ca/solarized-color-theme-screenshot/

The issue is that proper Solarized is a 16-bit palette, and running such a palette optimized for general terminal work and vim jacks up a few other things, e.g., sbopkg and probably most ncurses interface using similar colors. I played around with loads of methods, including .Xresources, setting various termcap options (can't remember which at the moment), etc. I exchanged a few tweets emails or two with Ethan Schoonover and he provided some pointers (which I can't track down). I was mostly interested in using Solarized in vim. Maybe I'll need to hit it again.

Do you find the terminal color scheme interferes with other terminal applications?

dugan · 07-20-2012, 08:58 AM

I did not find that the color scheme interferes with terminal applications, and I have no trouble running sbopkg or (terminal) vim. You are aware, I'm sure, that the Solarized scheme for vim needs to be installed separately.

Perhaps you could post a screenshot of your "jacked up" terminal?

My configs, by the way, are here:
https://github.com/duganchen/dotfiles

You will notice that my .Xresources file sets the number of colors available to my terminals to 256, and that my .vimrc sets vim to expect a 256-color terminal. Also, I don't know which terminal you're using, I've built rxvt-unicode with --enable-256-colors, which is not set by the SBo SlackBuild script. My vim is also compiled with --with-x. I don't know if any of these are factors.

Muraii · 07-20-2012, 01:36 PM

I now remember the issue: GNU screen. As you'll see in the attached screenshot, with an xterm on the left using GNU screen and on the right a "native" xterm, the colors are quite different. Also top-right is sbopkg, and while it's legible it is not so legible as the standard (blaring) ANSI colors.

I have 256-color xterm support specifically noted in my .screenrc, and played with all sorts of terminfo options to get screen to play nicely. I couldn't get it worked out. I use screen often (probably too much), typically from PuTTY at work, so this is a real consideration. Also, not in the screenshot is irssi, which will require some theme reworking to be useful. Using Solarized with irssi's default color scheme, there are no highlights to differentiate nicks and discussion. But that's not precisely an indictment of Solarized.

I may check into tmux on the chance that it plays more nicely with colorschemes. I assume, as it's fairly popular, you or someone else here uses GNU screen at least infrequently. How have you adapted it with Solarized, if at all?

dugan · 07-20-2012, 02:26 PM

I have not tried either tmux or screen with Solarized. I use a tiling window manager, so those two don't add much value.

Also, I remember seeing a Solarized irssi color scheme.

commandlinegamer · 07-26-2012, 09:47 AM

Work PC.

Fvwm (2.5.3) compiled with struts option to prevent maximised windows covering the entire screen, with a simple text-only launcher I wrote using PyGTK - I find icon-based panels cause me more pause as I try to figure out what I want to do.

I rarely use everything on that panel every day either, typically just a terminal, web browser, VirtualBox and maybe LibreOffice Writer on average.

At home I have that new-fangled KDE thingummybob.

Broker824 · 07-27-2012, 07:02 PM

My Slackware 13.37 Xfce 4.6.2 to Dell laptop

Ian John Locke II · 07-28-2012, 09:11 AM

Quote:

Originally Posted by Muraii

I now remember the issue: GNU screen. As you'll see in the attached screenshot, with an xterm on the left using GNU screen and on the right a "native" xterm, the colors are quite different. Also top-right is sbopkg, and while it's legible it is not so legible as the standard (blaring) ANSI colors.

I have 256-color xterm support specifically noted in my .screenrc, and played with all sorts of terminfo options to get screen to play nicely. I couldn't get it worked out. I use screen often (probably too much), typically from PuTTY at work, so this is a real consideration. Also, not in the screenshot is irssi, which will require some theme reworking to be useful. Using Solarized with irssi's default color scheme, there are no highlights to differentiate nicks and discussion. But that's not precisely an indictment of Solarized.

I may check into tmux on the chance that it plays more nicely with colorschemes. I assume, as it's fairly popular, you or someone else here uses GNU screen at least infrequently. How have you adapted it with Solarized, if at all?

Make sure in your vimrc that you have set t_Co=256. Even with 256 color support in screen, I think vim assumes it to be a "dumb" terminal so it only uses 16 colors. (That's at least a possibility).

Muraii · 07-29-2012, 02:51 PM

Quote:

Originally Posted by Ian John Locke II

Make sure in your vimrc that you have set t_Co=256. Even with 256 color support in screen, I think vim assumes it to be a "dumb" terminal so it only uses 16 colors. (That's at least a possibility).

I think I tried it, and just tried again. I found that I had a conditional based on the value of $TERM, sending jellyx if $TERM = "screen-256color". I undid this, and things work fine. Perhaps the limitation I had was with PuTTY, but I'll keep looking. Thanks for the reminder.

fogpipe · 07-30-2012, 01:16 AM

A new one

EDIT: the image wont upload because its too big and id be happy to try to fix it but the new gimp file save dialogues are so screwed up i would rather just look for a different peice of software. Yes i looked at the export function.

Snark1994 · 07-31-2012, 01:29 PM

Quote:

Originally Posted by fogpipe

the new gimp file save dialogues are so screwed up i would rather just look for a different peice of software.

You've looked in the "export" menu option, I presume?

sycamorex · 07-31-2012, 05:26 PM

Quote:

Originally Posted by fogpipe

A new one

EDIT: the image wont upload because its too big and id be happy to try to fix it but the new gimp file save dialogues are so screwed up i would rather just look for a different peice of software. Yes i looked at the export function.

Come on. It is so much better now. As the McDonalds' slogan goes, I'm loving it.