[Solved] 256 color term causes color glitch

Hello,
I'm having a strange (to me anyways) issue with 256 color terminals. The issue appears under xterm-256color and rvxt(-unicode)-256color, but not under any of the 8-color terminals I've tried.
A bit of background, if it's relevant: this is my second machine running Arch. It's an Asus netbook which I intend to use for schoolwork-related stuff (therefore, no need for X or a DE -- just console tools). I'm trying to get a 256 color term working because I use emacs, and mc a lot, and they both have nice 256 color themes I'd like to use.
However, when I use a 256 color term, the following happens:
The universal issue is that the colors are wrong -- lots of them are the same blue and grey color repeated again and again. This is I think what is causing emacs/mc and others to do all of their colored highlighting in an unreadable mess of these same colors everywhere. The issue particular to rxvt-unicode-256color (and not rxvt-256color) is the other effect shown in the picture -- the text becomes 'distorted' into incorrect characters. The text typed in on the left, for example, are two ordinary sentences.
Maybe what I'm looking at in the unicode term is two unrelated issues... I'm not sure. In any case, if someone could point me in the direction of a solution or offer some insight, I'd appreciate it.
Thanks!
Last edited by jasonwryan (2013-02-26 17:22:36)

jasonwryan wrote:This is likely an issue with your terminfo. You aren't setting a TERM value in your shell .rc file are you?
You've caught me redhanded, but more importantly you've finally given me a new name to look into. After several rounds of tic-terminfo-toe, I'm satisfied that as trilby says there simply is no way to get the full 256 color range out of the tty without some x in the middle. This leads to more questions (where's the equivalent of inittab for systemd, where does term get set to xterm anyway (when not in the user's rc's at least, why did it work better through pts, can I achieve 256 in pts without forwarding x, where do I find an 8-color vim syntax scheme that won't burn my eyeballs, etc), but the topic question is resolved. Thanks!

Similar Messages

[SOLVED] Sup email client 256 colors support

I've installed sup email client (https://aur.archlinux.org/packages/sup-git) and wombat theme (https://github.com/mklinik/sup-colorscheme-wombat) for it. But everything become red-colored in the background and white-colored for text (I'm using rxvt-unicode and it has 256-color support so things should work find). I tried to google but found nothing.
I though there is issue with support 256 colors in ncurses so I rebuild this package with necessary flags from pkgbuild: https://projects.archlinux.org/svntogit … es/ncurses and installed it. But due to version differences gem file didn't build after it with message "error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory" (and also really much stuff broke so I hardly restored original ncurses).
Somebody know the way to use sup with 256 colors in terminal?
Last edited by Shagabutdinov (2014-04-28 07:00:40)

jasonwryan wrote:The correct way is to use terminfo: setting the variable in Xresources or anywhere else is an ugly hack that will likely cause other problems down the track...
Not causing problems down the track is the exact reason given for why you should use Xresources to set TERM. The consensus seems to be that the terminal emulator should be the one to set it and using Xresources is one way to do that.
However TERM is set - Xresources, arguments, .bashrc - all that matters is that the capabilities defined in the terminfo file match the actual capabilities of the terminal emulator. Having the terminal emulator do it at least gives it the chance to match capabilities. It also prevents TERM from getting set to the wrong value for other terminal emulators or virtual consoles.
(Also, one does not "use terminfo" to set TERM. Terminfo uses TERM to tell terminal apps the capabilities of whatever they're outputting to.)

Problem with X11 running 256 colors finally SOLVED!

Good morning all.
Last August I posted thread regarding X11 not working with 256 colors.
http://discussions.apple.com/thread.jspa?messageID=2161056

Apple did it in the 10.4.9 update, but that slipped by me until I saw this post (so thanks!!!)

[SOLVED] urxvt colors and moc theme

Hello!
I am a KDE user and usually i am using Konsole. For some applications (like htop and moc) i use urxvt (patched version from AUR). The problem is in colors. When i launch moc in Konsole the theme colours are right but not in urxvt too. That happens with htop also. URxvt doesn't follow theme backrground color (uses its own) and foreground colors too.
Here is my .Xresource file:
! urxvt
! URxvt*termName: string
!URxvt*geometry: 80x40
! URxvt*chdir: string
! URxvt*reverseVideo: boolean
! URxvt*loginShell: boolean
! URxvt*jumpScroll: boolean
! URxvt*skipScroll: boolean
! URxvt*pastableTabs: boolean
! URxvt*scrollstyle: mode
URxvt*scrollBar: false
! URxvt*scrollBar_right: boolean
! URxvt*scrollBar_floating: boolean
! URxvt*scrollBar_align: mode
!URxvt*thickness: 20
! URxvt*scrollTtyOutput: boolean
! URxvt*scrollTtyKeypress: boolean
! URxvt*scrollWithBuffer: boolean
! URxvt*inheritPixmap: boolean
! URxvt*transparent: boolean
! URxvt*tintColor: color
! URxvt*shading: number
! URxvt*blurRadius: HxV
! URxvt*fading: number
! URxvt*fadeColor: color
! URxvt*utmpInhibit: boolean
! URxvt*urgentOnBell: boolean
! URxvt*visualBell: boolean
! URxvt*mapAlert: boolean
! URxvt*meta8: boolean
! URxvt*mouseWheelScrollPage: boolean
! URxvt*tripleclickwords: boolean
! URxvt*insecure: boolean
! URxvt*cursorUnderline: boolean
! URxvt*cursorBlink: true
! URxvt*pointerBlank: boolean
URxvt*background: #171717
URxvt*foreground: #B2B2B2
URxvt*color0: #171717
URxvt*color1: #3D3D3D
URxvt*color2: #ffffff
! URxvt*color3: color
! URxvt*color4: color
! URxvt*color5: color
! URxvt*color6: color
! URxvt*color7: color
! URxvt*color8: color
! URxvt*color9: color
! URxvt*color10: color
! URxvt*color11: color
! URxvt*color12: color
! URxvt*color13: color
! URxvt*color14: color
! URxvt*color15: color
! URxvt*colorBD: color
! URxvt*colorIT: color
! URxvt*colorUL: color
! URxvt*colorRV: color
! URxvt*underlineColor: color
! URxvt*scrollColor: color
! URxvt*troughColor: color
! URxvt*highlightColor: color
! URxvt*highlightTextColor: color
! URxvt*cursorColor: color
! URxvt*cursorColor2: color
! URxvt*pointerColor: color
! URxvt*pointerColor2: color
URxvt*borderColor: #171717
URxvt.font: xft:Ubuntu Mono:size=11
!URxvt*iconFile: /usr/share/icons/oxygen/128x128/apps/utilities-terminal.png
! URxvt*boldFont: fontname
! URxvt*italicFont: fontname
! URxvt*boldItalicFont: fontname
! URxvt*intensityStyles: boolean
! URxvt*inputMethod: name
! URxvt*preeditType: style
! URxvt*imLocale: string
! URxvt*imFont: fontname
! URxvt*title: string
! URxvt*iconName: string
! URxvt*saveLines: number
! URxvt*buffered: boolean
URxvt*depth: 32
! URxvt*visual: number
! URxvt*transient-for: windowid
! URxvt*override-redirect: boolean
! URxvt*hold: boolean
! URxvt*externalBorder: 20
! URxvt*internalBorder: 7
! URxvt*borderLess: true
! URxvt*lineSpace: number
! URxvt*letterSpace: number
! URxvt*skipBuiltinGlyphs: true
! URxvt*pointerBlankDelay: number
! URxvt*backspacekey: string
! URxvt*deletekey: string
! URxvt*print-pipe: string
! URxvt*modifier: modifier
! URxvt*cutchars: string
! URxvt*answerbackString: string
! URxvt*secondaryScreen: boolean
!URxvt*secondaryScroll: boolean
! URxvt*perl-lib: string
! URxvt*perl-eval: perl-eval
! URxvt*perl-ext-common: tabbed
! URxvt*perl-ext: string
! URxvt*iso14755: boolean
! URxvt*iso14755_52: boolean
! URxvt*xrm: string
! URxvt*keysym.sym: keysym
! URxvt*background.border: true
! URxvt*background.expr: string
! URxvt*background.interval: seconds
! URxvt*bell-command: string
! URxvt*matcher.button: string
! URxvt*matcher.launcher: string
! URxvt*matcher.launcher.*: string
! URxvt*matcher.pattern.*: string
! URxvt*matcher.rend.*: string
! URxvt*remote-clipboard.fetch: string
! URxvt*remote-clipboard.store: string
! URxvt*searchable-scrollback: string
! URxvt*selection-autotransform.*: string
! URxvt*selection-pastebin.cmd: string
! URxvt*selection-pastebin.url: string
! URxvt*selection.pattern-0: string
! URxvt*tab-bg: 1
! URxvt*tab-fg: 2
! URxvt*tabbar-bg: 0
! URxvt*tabbar-fg: colour
! URxvt*url-launcher: string
Moc config file:
# This is a configuration file for the MOC player. It should be named
# 'config' and placed in the ~/.moc directory. As this file can specify
# commands which invoke other applications, MOC will refuse to start if it
# is not owned by either root or the current user, or if it is writable by
# anyone other than its owner. All options are given with their default
# values, and therefore commented.
# Comments begin with '#'.
# You can use quotes and escape ('\') in parameters.
# You can have variable values substituted by enclosing the variable name
# as "${...}". (This only applies to the portion of the option following
# the ' ='.) Variables are substituted first from the environment then,
# if not found, from the configuration options. (Note that the value of
# a configuration option substituted is that which it has at the time the
# substitution variable is encountered.) If there is a naming conflict
# between an environment and configuration variable, you may be able to
# resolve it by using lowercase as the environment variable matches are
# case-sensitive whereas the configuration variables are not.
# You can also use the form "${...:-...}" where the value in the second
# position will be substituted if the variable name given in the first
# position is unset or null.
# So, for example:
# MusicDir = /music/${USER:-public}
# Fastdir1 = ${MusicDir}/mp3/rock
# Fastdir2 = ${MusicDir}/mp3/electronic
# Fastdir3 = ${MusicDir}/mp3/rap
# Fastdir4 = ${MusicDir}/mp3/etc
# Variable names are limited to those accepted by the BASH shell; that
# is, those comprising the upper- and lowercase ASCII characters, digits
# and the underscore.
# If you need to use the "${" sequence for any other purpose, write "$${"
# and it will be replaced by "${" and not treated as a substitution.
# Some options take lists of strings as their values. The strings are
# separated by colons. Additional strings can be appended to the list
# using "+ =" in place of a plain "=" to assign the value. For an example,
# see the XTerms option.
# You can override any configuration option when you run MOC using the
# '-O' command line option:
# mocp -O AutoNext =no -O messagelingertime=1 -O XTerms+=xxt:xwt
# This command line option can be repeated as many times as needed and
# the configuration option name is not case sensitive. (Note that MOC
# does not perform variable substitution on the value of such overridden
# configuration options.) Most option values are set before the
# configuration file is processed (which allows the new values to be
# picked up by substitutions), however list-valued options are overridden
# afterwards (which gives the choice of whether the configured values are
# replaced or added to).
# Remember that the client and server are separate processes and the
# server will retain the configuration values formed from the environment
# within which it was originally started.
# Show file titles (title, author, album) instead of file names?
#ReadTags = yes
# In which directory do you store your music files? If you specify it
# you will be able to jump straight to this directory with the '-m'
# parameter or the 'm' command. This can also point to a playlist.
# Example: MusicDir = "/home/joe/music"
#MusicDir = "My folder"
# Start in the music directory by default? If set to 'no', start
# in the current directory by default. A single directory on
# the command line takes precedence.
#StartInMusicDir = no
# How to sort? FileName is the option's only value for now.
#Sort = FileName
# Show errors in the streams (for example, broken frames in MP3 files)?
#ShowStreamErrors = no
# Ignore CRC errors in MP3 files? Most players do that, so the default
# value is 'yes'.
#MP3IgnoreCRCErrors = yes
# Set playback toggles.
#Repeat = no
#Shuffle = no
#AutoNext = yes
# Default FormatString:
# %n - Track number
# %a - Artist
# %A - Album
# %t - Title
# %(X:TRUE:FALSE) - Ternary expression: if X exists, do TRUE,
# otherwise FALSE. The escape character must
# be doubled (i.e., '\\'). (See zshmisc
# documentation for more information.)
#FormatString = "%(n:%n :)%(a:%a - :)%(t:%t:)%(A: $%A$:)"
# Input and output buffer sizes (in kilobytes).
#InputBuffer = 512 # Minimum value is 32KB
#OutputBuffer = 512 # Minimum value is 128KB
# How much to fill the input buffer before playing (in kilobytes)?
# This can't be greater than the value of InputBuffer. While this has
# a positive effect for network streams, it also causes the broadcast
# audio to be delayed.
#Prebuffering = 64
# Use this HTTP proxy server for internet streams. If not set, the
# environment variables http_proxy and ALL_PROXY will be used if present.
# Format: HTTPProxy = PROXY_NAME:PORT
#HTTPProxy =
# Sound driver - OSS, ALSA, JACK, SNDIO (on OpenBSD) or null (only for
# debugging). You can enter more than one driver as a colon-separated
# list. The first working driver will be used.
#SoundDriver = JACK:ALSA:OSS
# Jack output settings.
#JackClientName = "moc"
#JackStartServer = no
#JackOutLeft = "system:playback_1"
#JackOutRight = "system:playback_2"
# OSS output settings.
#OSSDevice = /dev/dsp
#OSSMixerDevice = /dev/mixer
#OSSMixerChannel1 = pcm # 'pcm', 'master' or 'speaker'
#OSSMixerChannel2 = master # 'pcm', 'master' or 'speaker'
# ALSA output settings.
#ALSADevice = default
#ALSAMixer1 = PCM
#ALSAMixer2 = Master
# Save software mixer state?
# If enabled, a file 'softmixer' will be created in '~/.moc/' storing the
# mixersetting set when the server is shut down.
# Note that there is a "hidden" 'Amplification' setting in that file.
# Amplification (0-200) is used to scale the mixer setting (0-100). This
# results in a higher signal amplitude but may also produce clipping.
#Softmixer_SaveState = yes
# Save equalizer state?
# If enabled, a file 'equalizer' will be created in '~/.moc/' storing the
# equalizer settings when the server is shut down.
# Note that there is a "hidden" 'Mixin' setting in that file.
# Mixin (0.0-1.0) is used to determine how much of the original signal is
# used after equalizing. 0 means to only use the equalized sound, while 1
# effectively disabled the mixer. The default is 0.25.
#Equalizer_SaveState = yes
# Show files with dot at the beginning?
#ShowHiddenFiles = no
# Hide file name extensions?
#HideFileExtension = no
# Show file format in menu?
#ShowFormat = yes
# Show file time in menu? Possible values: 'yes', 'no' and 'IfAvailable'
# (meaning show the time only when it is already known, which often works
# faster).
#ShowTime = IfAvailable
# Show time played as a percentage in the time progress bar.
#ShowTimePercent = no
# Values of the TERM environment variable which are deemed to be xterms.
#XTerms = xterm
#XTerms + = xterm-colour:xterm-color
#XTerms + = xterm-256colour:xterm-256color
#XTerms + = rxvt:rxvt-unicode
#XTerms + = rxvt-unicode-256colour:rxvt-unicode-256color
#XTerms + = eterm
# Theme file to use. This can be absolute path or relative to
# /usr/share/moc/themes/ (depends on installation prefix) or
# ~/.moc/themes/ .
# Example: Theme = laras_theme
Theme = yellow_red_theme
# The theme used when running on an xterm.
# Example: XTermTheme = transparent-background
#XTermTheme = yellow_red_theme
# Should MOC try to autoload the default lyrics file for an audio? (The
# default lyrics file is a text file with the same file name as the audio
# file name with any trailing "extension" removed.)
#AutoLoadLyrics = yes
# MOC directory (where pid file, socket and state files are stored).
# You can use ~ at the beginning.
#MOCDir = ~/.moc
# Use mmap() to read files. mmap() is much slower on NFS.
#UseMMap = no
# Use MIME to identify audio files. This can make for slower loading
# of playlists but is more accurate than using "extensions".
#UseMimeMagic = no
# Assume this encoding for ID3 version 1/1.1 tags (MP3 files). Unlike
# ID3v2, UTF-8 is not used here and MOC can't guess how tags are encoded.
# Another solution is using librcc (see the next option). This option is
# ignored if UseRCC is set to 'yes'.
#ID3v1TagsEncoding = WINDOWS-1250
# Use librcc to fix ID3 version 1/1.1 tags encoding.
#UseRCC = yes
# Use librcc to filenames and directory names encoding.
#UseRCCForFilesystem = yes
# When this option is set the player assumes that if the encoding of
# ID3v2 is set to ISO-8859-1 then the ID3v1TagsEncoding is actually
# that and applies appropriate conversion.
#EnforceTagsEncoding = no
# Enable the conversion of filenames from the local encoding to UTF-8.
#FileNamesIconv = no
# Enable the conversion of the xterm title from UTF-8 to the local encoding.
#NonUTFXterm = no
# Remember the playlist after exit?
SavePlaylist = yes
# When using more than one client (interface) at a time, do they share
# the playlist?
#SyncPlaylist = yes
# Choose a keymap file (relative to '~/.moc/' or using an absolute path).
# An annotated example keymap file is included ('keymap.example').
# Example: Keymap = my_keymap
#Keymap =
# Use ASCII rather than graphic characters for drawing lines. This
# helps on some terminals.
#ASCIILines = no
# FastDirs, these allow you to jump directly to a directory, the key
# bindings are in the keymap file.
# Examples: Fastdir1 = /mp3/rock
# Fastdir2 = /mp3/electronic
# Fastdir3 = /mp3/rap
# Fastdir4 = /mp3/etc
#Fastdir1 =
#Fastdir2 =
#Fastdir3 =
#Fastdir4 =
#Fastdir5 =
#Fastdir6 =
#Fastdir7 =
#Fastdir8 =
#Fastdir9 =
#Fastdir10 =
# How fast to seek (in number of seconds per keystroke). The first
# option is for normal seek and the second for silent seek.
#SeekTime = 1
#SilentSeekTime = 5
# PreferredDecoders allows you to specify which decoder should be used
# for any given audio format. It is a colon-separated list in which
# each entry is of the general form 'code(decoders)', where 'code'
# identifies the audio format and 'decoders' is a comma-separated list
# of decoders in order of preference.
# The audio format identifier may be either a filename extension or a
# MIME media type. If the latter, the format is 'type/subtype' (e.g.,
# 'audio/flac'). Because different systems may give different MIME
# media types, any 'x-' prefix of the subtype is ignored both here and
# in the actual file MIME type (so all combinations of 'audio/flac' and
# 'audio/x-flac' match each other).
# For Internet streams the matching is done on MIME media type and on
# actual content. For files the matches are made on MIME media type
# (if the 'UseMimeMagic' option is set) and on filename extension. The
# MIME media type of a file is not determined until the first entry for
# MIME is encountered in the list.
# The matching is done in the order of appearance in the list with any
# entries added from the command line being matched before those listed
# here. Therefore, if you place all filename extension entries before
# all MIME entries you will speed up MOC's processing of directories
# (which could be significant for remote file systems).
# The decoder list may be empty, in which case no decoders will be used
# for files (and files with that audio format ignored) while Internet
# streams will be assessed on the actual content. Any decoder position
# may contain an asterisk, in which case any decoder not otherwise listed
# which can handle the audio format will be used. It is not an error to
# list the same decoder twice, but neither does it make sense to do so.
# If you have a mix of audio and non-audio files in your directories, you
# may wish to include entries at top of the list which ignore non-audio
# files by extension.
# In summary, the PreferredDecoders option provides fine control over the
# type of matching which is performed (filename extension, MIME media
# type and streamed media content) and which decoder(s) (if any) are used
# based on the option's list entries and their ordering.
# Examples: aac(aac,ffmpeg) first try FAAD2 for AACs then FFmpeg
# mp3() ignore MP3 files
# wav(*,sndfile) use sndfile for WAV as a last resort
# ogg(vorbis,*):flac(flac,*) try Xiph decoders first
# ogg():audio/ogg() ignore OGG files, and
# force Internet selection by content
# gz():html() ignore some non-audio files
# Any unspecified audio formats default to trying all decoders.
# Any unknown (or misspelt) drivers are ignored.
# All names are case insensitive.
# The default setting reflects the historical situation modified by
# the experience of users.
#PreferredDecoders = aac(aac,ffmpeg):m4a(ffmpeg)
#PreferredDecoders += mpc(musepack,*,ffmpeg):mpc8(musepack,*,ffmpeg)
#PreferredDecoders += sid(sidplay2):mus(sidplay2)
#PreferredDecoders += wav(sndfile,*,ffmpeg)
#PreferredDecoders += wv(wavpack,*,ffmpeg)
#PreferredDecoders += audio/aac(aac):audio/aacp(aac):audio/m4a(ffmpeg)
#PreferredDecoders += audio/wav(sndfile,*)
# The following PreferredDecoders attempt to handle the ambiguity surrounding
# container types such as OGG for files. The first two entries will force
# a local file to the correct decoder (assuming the .ogg file contains Vorbis
# audio), while the MIME media types will cause Internet audio streams to
# be assessed on content (which may be either Vorbis or Speex).
#PreferredDecoders += ogg(vorbis,ffmpeg):oga(vorbis,ffmpeg):ogv(ffmpeg)
#PreferredDecoders += opus(opus,ffmpeg)
#PreferredDecoders += spx(speex)
#PreferredDecoders += application/ogg(vorbis):audio/ogg(vorbis)
# Which resampling method to use. There are a few methods of resampling
# sound supported by libresamplerate. The default is 'Linear') which is
# also the fastest. A better description can be found at:
# http://www.mega-nerd.com/libsamplerate/api_misc.html#Converters
# but briefly, the following methods are based on bandlimited interpolation
# and are higher quality, but also slower:
# SincBestQuality - really slow (I know you probably have an xx GHz
# processor, but it's still not enough to not see
# this in the top output :) The worst case
# Signal-to-Noise Ratio is 97dB.
# SincMediumQuality - much faster.
# SincFastest - the fastest bandlimited interpolation.
# And these are lower quality, but much faster methods:
# ZeroOrderHold - really poor quality, but it's really fast.
# Linear - a bit better and a bit slower.
#ResampleMethod = Linear
# Always use this sample rate (in Hz) when opening the audio device (and
# resample the sound if necessary). When set to 0 the device is opened
# with the file's rate.
#ForceSampleRate = 0
# By default, even if the sound card reports that it can output 24bit samples
# MOC converts 24bit PCM to 16bit. Setting this option to 'yes' allows MOC
# to use 24bit output. (The MP3 decoder, for example, uses this format.)
# This is disabled by default because there were reports that it prevents
# MP3 files from playing on some soundcards.
#Allow24bitOutput = no
# Use realtime priority for output buffer thread. This will prevent gaps
# while playing even with heavy load. The user who runs MOC must have
# permissions to set such a priority. This could be dangerous, because it
# is possible that a bug in MOC will freeze your computer.
#UseRealtimePriority = no
# The number of audio files for which MOC will cache tags. When this limit
# is reached, file tags are discarded on a least recently used basis (with
# one second resolution). You can disable the cache by giving it a size of
# zero. Note that if you decrease the cache size below the number of items
# currently in the cache, the number will not decrease immediately (if at
# all).
#TagsCacheSize = 256
# Number items in the playlist.
#PlaylistNumbering = yes
# Main window layouts can be configured. You can change the position and
# size of the menus (directory and playlist). You have three layouts and
# can switch between then using the 'l' key (standard mapping). By default,
# only two layouts are configured.
# The format is as follows:
# - Each layout is described as a list of menu entries.
# - Each menu entry is of the form:
# menu(position_x, position_y, width, height)
# where 'menu' is either 'directory' or 'playlist'.
# - The parameters define position and size of the menu. They can
# be absolute numbers (like 10) or a percentage of the screen size
# (like 45%).
# - 'width' and 'height' can have also value of 'FILL' which means
# fill the screen from the menu's position to the border.
# - Menus may overlap.
# You must describe at least one menu (default is to fill the whole window).
# There must be at least one layout (Layout1) defined; others can be empty.
# Example: Layout1 = playlist(50%,50%,50%,50%)
# Layout2 = ""
# Layout3 = ""
# Just one layout, the directory will occupy the whole
# screen, the playlist will have 1/4 of the screen size
# and be positioned at lower right corner. (Note that
# because the playlist will be hidden by the directory
# you will have to use the TAB key to make the playlist
# visible.)
# Example: Layout1 = playlist(0,0,100%,10):directory(0,10,100%,FILL)
# The screen is split into two parts: playlist at the top
# and the directory menu at the bottom. Playlist will
# occupy 10 lines and the directory menu the rest.
#Layout1 = directory(0,0,50%,100%):playlist(50%,0,FILL,100%)
#Layout2 = directory(0,0,100%,100%):playlist(0,0,100%,100%)
#Layout3 = ""
# When the song changes, should the menu be scrolled so that the currently
# played file is visible?
#FollowPlayedFile = yes
# What to do if the interface was started and the server is already playing
# something from the playlist? If CanStartInPlaylist is set to 'yes', the
# interface will switch to the playlist. When set to 'no' it will start
# from the last directory.
#CanStartInPlaylist = yes
# Executing external commands (1 - 10) invoked with key commands (F1 - F10
# by default).
# Some arguments are substituted before executing:
# %f - file path
# %i - title made from tags
# %S - start block mark (in seconds)
# %E - end block mark (in seconds)
# Data from tags can also be substituted:
# %t - title
# %a - album
# %r - artist
# %n - track
# %m - time of the file (in seconds)
# The parameters above apply to the currently selected file. If you change
# them to capital letters, they are taken from the file currently playing.
# Programs are run using execv(), not a shell, so you can't do things like
# redirecting the output to a file. The command string is split using blank
# characters as separators; the first element is the command to be executed
# and the rest are its parameters, so if you use "echo Playing: %I" we run
# program 'echo' (from $PATH) with 2 parameters: the string 'Playing:' and
# the title of the file currently playing. Even if the title contains
# spaces, it's still one parameter and it's safe if it contains `rm -rf /`.
# Examples: ExecCommand1 = "cp %f /mnt/usb_drive"
# ExecCommand2 = "/home/joe/now_playing %I"
#ExecCommand1 =
#ExecCommand2 =
#ExecCommand3 =
#ExecCommand4 =
#ExecCommand5 =
#ExecCommand6 =
#ExecCommand7 =
#ExecCommand8 =
#ExecCommand9 =
#ExecCommand10 =
# Display the cursor in the line with the selected file. Some braille
# readers (the Handy Tech modular series ZMU 737, for example) use the
# cursor to focus and can make use of it to present the file line even
# when other fields are changing.
#UseCursorSelection = no
# Set the terminal title when running under xterm.
#SetXtermTitle = yes
# Set the terminal title when running under screen.
#SetScreenTitle = yes
# Display full paths instead of just file names in the playlist.
#PlaylistFullPaths = yes
# The following setting describes how block markers are displayed in
# the play time progress bar. Its value is a string of exactly three
# characters. The first character is displayed in a position which
# corresponds to the time marked as the start of a block and the last
# character to the time marked as the end of the block. The middle
# character is displayed instead if both the start and the end of the block
# would fall in the same position (within the resolution of the interface).
# You can turn off the displaying of these block marker positions by using
# three space characters.
#BlockDecorators = "`\"'"
# How long (in seconds) to leave a message displayed on the screen.
# Setting this to a high value allows you to scroll through the messages
# using the 'hide_message' key. Setting it to zero means you'll have to
# be quick to see any message at all. Any new messages will be queued up
# and displayed after the current message's linger time expires.
#MessageLingerTime = 3
# Does MOC display a prefix on delayed messages indicating
# the number of queued messages still to be displayed?
#PrefixQueuedMessages = yes
# String to append to the queued message count if any
# error messages are still waiting to be displayed.
#ErrorMessagesQueued = "!"
# Self-describing ModPlug options (with 'yes' or 'no' values).
#ModPlug_Oversampling = yes
#ModPlug_NoiseReduction = yes
#ModPlug_Reverb = no
#ModPlug_MegaBass = no
#ModPlug_Surround = no
# ModPlug resampling mode.
# Valid values are:
# FIR - 8 tap fir filter (extremely high quality)
# SPLINE - Cubic spline interpolation (high quality)
# LINEAR - Linear interpolation (fast, good quality)
# NEAREST - No interpolation (very fast, extremely bad sound quality)
#ModPlug_ResamplingMode = FIR
# Other self-describing ModPlug audio characteristic options.
# (Note that the 32 bit sample size seems to be buggy.)
#ModPlug_Channels = 2 # 1 or 2 channels
#ModPlug_Bits = 16 # 8, 16 or 32 bits
#ModPlug_Frequency = 44100 # 11025, 22050, 44100 or 48000 Hz
#ModPlug_ReverbDepth = 0 # 0 (quiet) to 100 (loud)
#ModPlug_ReverbDelay = 0 # Delay in ms (usually 40-200ms)
#ModPlug_BassAmount = 0 # 0 (quiet) to 100 (loud).
#ModPlug_BassRange = 10 # Cutoff in Hz (10-100).
#ModPlug_SurroundDepth = 0 # Surround level 0(quiet)-100(heavy).
#ModPlug_SurroundDelay = 0 # Surround delay in ms, usually 5-40ms.
#ModPlug_LoopCount = 0 # 0 (never), n (times) or -1 (forever)
# Self-describing TiMidity audio characteristic options.
#TiMidity_Rate = 44100 # Between 8000 and 48000
#TiMidity_Bits = 16 # 8 or 16
#TiMidity_Channels = 2 # 1 or 2
#TiMidity_Volume = 100 # 0 to 800
# You can setup a TiMidity-Config-File here.
# Leave it unset to use library defaults (/etc/timidity.cfg mostly).
# Setting it to 'yes' also uses the library defaults.
# Set it to 'no' if you don't have any configuration file.
# Otherwise set it to the name of a specific file.
#TiMidity_Config =
# Self-describing SidPlay2 audio characteristic options.
#SidPlay2_DefaultSongLength = 180 # If not in database (in seconds)
#SidPlay2_MinimumSongLength = 0 # Play at least n (in seconds)
#SidPlay2_Frequency = 44100 # 4000 to 48000
#SidPlay2_Bits = 16 # 8 or 16
#SidPlay2_Optimisation = 0 # 0 (worst quality) to 2 (best quality)
# Set path to a HVSC-compatible database (if not set, database is disabled).
#SidPlay2_Database =
# SidPlay2 playback Mode:
# "M": Mono (best for many SIDs)
# "S": Stereo
# "L"/"R": Left / Right
#SidPlay2_PlayMode = "M"
# Use start-song information from SID ('yes') or start at first song
# ('no'). Songs before the start-song won't be played. (Note that this
# option previously took the values 1 and 0; these are now deprecated
# in favour of 'yes' and 'no'.)
#SidPlay2_StartAtStart = yes
# Play sub-tunes. (Note that this option previously took the values 1
# and 0; these are now deprecated in favour of 'yes' and 'no'.)
#SidPlay2_PlaySubTunes = yes
# Run the OnSongChange command when a new song starts playing.
# Specify the full path (i.e. no leading '~') of an executable to run.
# Arguments will be passed, and you can use the following escapes:
# %a artist
# %r album
# %f filename
# %t title
# %n track
# %d file duration in XX:YY form
# %D file duration, number of seconds
# No pipes/redirects can be used directly, but writing a shell script
# can do the job.
# Example: OnSongChange = "/home/jack/.moc/myscript %a %r"
#OnSongChange =
# If RepeatSongChange is 'yes' then MOC will execute the command every time
# a song starts playing regardless of whether or not it is just repeating.
# Otherwise the command will only be executed when a different song is
# started.
#RepeatSongChange = no
# Run the OnStop command (full path, no arguments) when MOC changes state
# to stopped (i.e., when user stopped playing or changes a song).
#OnStop = "/home/jack/.moc/myscript_on_stop"
# This option determines which song to play after finishing all the songs
# in the queue. Setting this to 'yes' causes MOC to play the song which
# follows the song being played before queue playing started. If set to
# 'no', MOC will play the song following the last song in the queue if it
# is in the playlist. The default is 'yes' because this is the way other
# players usually behave. (Note that this option previously took the
# values 1 and 0; these are now deprecated in favour of 'yes' and 'no'.)
#QueueNextSongReturn = yes
I read wiki but didn't find anything useful. Thanks for any info.
Last edited by Shark (2014-12-17 12:31:30)

bleach wrote:
i see these
URxvt*background: #171717
URxvt*foreground: #B2B2B2
URxvt*color0: #171717
URxvt*color1: #3D3D3D
URxvt*color2: #ffffff
are not commented out
3d3d3d is for red but you have a blackish and color2 is for green but you have it white the rest should be the default colors. it uses the same colors only it changes the vairiant of the color you choice there or normally moc uses colors such as green blue and such which will call your console colors for those respective fields I know moc has /user/share/moc/themes/ that you can edit or make your own for instance copy one and edit it. I think htop uses the same color count which is 8 but with so green will be white when you use urxvt. 8 for normal colors 16 for bright dark and urxvt is 256 which is 16 but can use any of the 256 colors for 16.
just to clarify you have commented out your colors 4-15 and your green and red is weird, and htop aswell as moc is 8 bit. moc theme_yellow_red is default for background so it will use urxvts background
Haahaha, that is simple. And it works!!!
I didn't bother with commenting that because i thought they are not applied. Anyway, thanks man. My urxvt terminal si grateful to you and your thorough explanation. SOLVED!

Does Flex support 256 color displays?

Hi all,
Does Flex / Flash officially support 256-color displays? I
can't get the Image control to display any images at all when the
display is set to 256 colors.
I've tried PNG, GIF, and JPEG images with monochrome, 16
color, 256 color, and 24-bit palletes (in every combination the
formats allow). They *all* work fine if the display is set to
15-bit color or higher, but *none* of them work if the display is
set to 256 colors. I would have thought at the very least that the
Flash player could show a monochrome image on a 256 color display
Does anyone know if this is a limit in the Flex control, or
the underlying Flash controls? Could I solve it by using some Flash
control directly?
FYI, this the problem exists on both machines that I have
tested so far. Both using Windows 2000, with both IE7 and FF1.5.
Any ideas? Thanks!
Paul

OK, so this definately looks like a bug in Flex / Flash when
running on 256 color displays.
Really simple Flex projects that contain nothing but images
like:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="vertical">
<mx:Image source="
http://domain/image1.gif"
/>
<mx:Image source="
http://domain/image2.jpg"
/>
<mx:Image source="
http://domain/image3.png"
/>
</mx:Application>
Don't show anything at all, but if you throw in a few images
via a Text control such as:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="vertical">
<mx:Text width="450" height="75"><mx:htmlText>
<img src="
http://domain/image1.gif"
/>
</mx:htmlText></mx:Text>
<mx:Text width="450" height="75"><mx:htmlText>
<img src="
http://domain/image2.jpg"
/>
</mx:htmlText></mx:Text>
<mx:Text width="450" height="75"><mx:htmlText>
<img src ="
http://domain/image3.png"
/>
</mx:htmlText></mx:Text>
<mx:Text width="450" height="75"><mx:htmlText>
<img src="
http://domain/image1.gif"
/>
</mx:htmlText></mx:Text>
<mx:Text width="450" height="75"><mx:htmlText>
<img src="
http://domain/image2.jpg"
/>
</mx:htmlText></mx:Text>
<mx:Text width="450" height="75"><mx:htmlText>
<img src="
http://domain/image3.png"
/>
</mx:htmlText></mx:Text>
<mx:Image source="
http://domain/image1.gif"
/>
<mx:Image source="
http://domain/image2.jpg"
/>
<mx:Image source="
http://domain/image3.png"
/>
</mx:Application>
Then all of the images will appear - all of those embedded
into the Text controls, as well as those embedded into the Image
controls. Note, it seems that there needs to be "significantly"
more Text controls than Image controls for this to work... but I
haven't really narrowed that down.
Also, when the Text controls are not used, it seems that
popping up Alert boxes cause the images to display correctly until
the dialog box is dismissed, and then the Image controls disappear
again!
Finally, I've found that I can get the Image control to work
reliably (so far) by itself, if I simply set the height or width to
be at least one pixel less than (not greater than) the real image.
So, for example, my image is 450 pixels wide, by 75 pixels
high. So, of the following four Image controls, only the last one
works!
<mx:Image source="
http://domain/image1.gif"
/>
<mx:Image width="450" height="75" source="
http://domain/image1.gif"
/>
<mx:Image width="451" height="75" source="
http://domain/image1.gif"
/>
<mx:Image width="449" height="75" source="
http://domain/image1.gif"
/>
Once again, all of these behaviours only occur when the
display is set to a 256 color mode. Everything works as expected on
15bit+ color modes.
So, I guess I should file a bug report now?
Paul.

GNU Screen and 256 color terminal

Okay I've been racking my brain over trying to get 256 colors working while in screen.
If I run the 256colors2.pl script (found in xterm source) while in xterm / roxterm / xfce4-terminal it shows all colours as expected.
$ echo $TERM
xterm
Now I followed the wiki and added the "term screen-256color" line to my .screenrc
but if I run screen and run the 256colors script it doesn't show 256 colours (all messed up)
If I exit screen and manually set my $TERM
$ export TERM=xterm-256color
then run screen again, things seem to work properly.
But why?
I've read elsewhere on this forum that it's not good practice to force your $TERM so what should I do here?
What is the proper way? I just cant wrap my head around why 256 colors work when $TERM=xterm outside of screen, but not when in screen.
Last edited by Zer0 (2009-10-30 05:10:08)

I recommend just using TERM=xterm-256color, as TERM=xterm does not reflect the terminal's capabilities. Replacing the command for your current terminal emulator with something like:
xterm -tn xterm-256color
should be sufficient.
I now use rxvt-unicode-256color from [community], which uses a 256color terminfo by default. Why xterm and friends don't use this when it is supported, I don't understand.
Last edited by chpln (2009-10-30 06:32:44)

X11 Preferences Output 256 colors

I have an application which requires running X11 with 256 colors. When
I select 256 colors and restart X all X11 applications have no content,
i.e., there is nothing displayed in an xterm or any other X11 application.
I saw a question similar to this on another Apple Forum but the issue
was not resolved. Has anyone found a solution to this problem and if so
where may I find the solution? I know other users running the same application
with prior versions of the OS and they have no problems. Apparently the
problem is specific to X and Leopard. I have already installed X11-2.1.4 but
this did not solve the problem.
Thanks.

Posted to the wrong forum.

[solved] vim color scheme not working in urxvt/screen

i'm using the 256 color scheme inkblot in vim. It works great in urxvt alone. But the background is messed up in screen. Screen is able to display 256 colors.
Basically, the background it is supposed to set ends up being set for every line in which there is no text, while the lines that have text have an all black background. This doesn't happen outside of screen or in other 256 color enabled terminals.
This happens with every theme that sets a background (or more specifically an off-black/dark-grey background.. i haven't tried a theme that tries another color background).
Last edited by scv5 (2009-06-20 20:15:35)

add "term screen-256color" to your .screenrc, that's the cleanest approach
That probably won't be enough for urxvt, see this thread for more information http://bbs.archlinux.org/viewtopic.php?id=50647

256 color in Forms 10g

I find that there is support for ONLY 256 color in Forms 10g. Is it a limitation and can we use more than 256 colors?
I want to enter r92g136b146 in canvas properties background color. It gives me an errror FRM-12305
Please help. Thanks.

Forms supports 8 bit and 24 bit color spaces. It does not support 16 bit however.
The help file describes how you can define colors in a custom palette and load that. Note.37765.1 is also helpful.
Even though the notation you see in the property palette looks like a standard 24 bit rgb notation it is not. It uses percentages (and only discrete values, not 0-100) for each channel rather than values between 0 and 255.

How to save a JPG in 256 colors?

I'm using Photoshop CS2.
1. How to save a JPG in 256 colors?
2. Is there a way to see an image properties?
-- I want to know if that image is in 256 color or not...

Mary Jo, since you are a newcomer, you may not yet understand that in any given Adobe forum, there are a whole bunch of conversations going on at the same time. Each one of these is about a certain "topic", described in the title and opening post. The discussion sometimes stays right on point, and sometimes veers off a bit, and there are often quick side-issues branching off from the main topic, but still related. Within limits, people here try to keep the discussion on a single general topic. For example, in this topic, the initial issue is whether there is a way, in Photoshop, to limit the number of colors in a JPEG image to 256; there were discussions about whether this could be done or not, and alternative programs that may be able to accomplish this, and a comparison of the file sizes for 256 bit images in different file types.
Your question, however, is not a logical outgrowth of the discussion. It's a perfectly good question, but it deserves its own new discussion topic. It's like a bunch of people have been sitting around a table discussing the merits of Canon vs. Nikon SLRs, and someone sits down at the table and, instead of joining the conversation, asks a completely unrelated question about point-and-shoot cameras, or camcorders.
It's off-topic here, and you should start a new topic. Make the title descriptive, such as "Why does a 8 megapixel image result in a 3 megabyte file on my computer?" (assuming that's what you want to ask -- just "M" doesn't tell me whether you are talking about MP or MB). In the initial post, provide a more detailed description of what you want to know. Tell us what camera and Photoshop version you are using, and how you encountered the issue. People will see that a new topic raises an issue they know something about and you will get a response -- probably a good answer, if you keep in the conversation.
[Edit: Trez hit "post" before I did. Trez-- I think she is using Photoshop, not Elements; she did say CS2.]

Using more than 256 colors in 3D graph?

Hi,
I am using 3D surface plot in Labview 6.i and I would like to know if it is
possible to use more than 256 colors (in the Z-scale).
Actually I would like to have very smooth change in the color map and this
could be possible if we could use 16bit color instead of 8bit.
Thanks.

Hi nweiss,
I'm not sure whether or not you received my reply to your last post; in case you haven't, here's the link:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000E94C0000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0
Thanks,
Ted F.

How can i create 256 colors (8 bits) jpeg ?

Dear all :
The jpeg created by JPEGEncoder was in true color (24 bits) , how can i create or convert the jpeg to 256 colors . Because i want to convert the jpeg to gif in further , but the gifencoder i found can only accept the images that with 256 colors only , so any one can give me a help ? Or the ways that convert a jpeg to gif using java ?

To reduce the number of colors in an image, try:
http://www.gurge.com/amd/java/quantize/
This does a very good job of reducing colors without making the image look too different.
Further, if you want to encode a GIF file, try using:
http://www.acme.com/java/software/Acme.JPM.Encoders.GifEncoder.html
There should be some sample code which shows you how to use those packages on their respective websites. Hope this helps!

Why is the 256 Color Option 'ghosted' in Leopard?

I've recently 'upgraded' my Mac Pro to Leopard and in the process have killed a major piece of cross platform software that I use in my work. Apparently, Leopard has disabled 256 color compatibility, while simultaneously leaving the option as ghosted teaser on the displays panel of system preferences. They even have a posting on this (answer 306773) that claims this is 'normal'.
Now, I don't actually want to set the global display to 256 colors, but my application works in X11, where I need the individual windows to open with 8-bit color depth. This was never a problem with Tiger (or Windows or Linux). So long as the OS supports 256 colors, the windows open fine under X. As things are now, when I open X in 256 color mode, I get blank white screens on the same machine where they were working fine on before the upgrade!
Does anyone know if this is going to be fixed or if there is a workaround that will enable me to use this program? As it stands now, I'm pretty much frozen out of the Mac OS as a work computer unless I go back to Tiger. I'm in the process of getting a new set of computers for the group I'm in, and, if this isn't fixable, I'm probably going to have cancel my mac orders and switch to PCs instead (horrors!).
Any ideas out there?

I suggest posting to the Unix forum under OS X Technologies where the X11 gurus hang out.

256 Colors on new 24 inch iMac

Is it possible to get the ATI Radeon HD 2600 PRO in my new 24 inch intel iMac to be able to show 256 colors?

It still doesn't show up.
What I am trying to do is use Boot Camp to play a game, Roller Coaster Tycoon 2, but the game has to be played in 256 colors. I've tried all kinds of troubleshooting things in Boot Camp, but nothing works.
I can't find drivers for my video card, are there any that I need?
I've also heard of Windows programs that can trick the game into thinking it is running in 256 colors... where can I find one of those?

256 Colors/Old Games

is there anyway to fix this manually, i have tried everything i can think of except using the start up disk to try and revert to an older version for leopard so i can play fallout again i have the GMA X3100 Graphics card witch Ive heard had the most issues with 256 colors recently, any ideas?

Unfortunately some games require software graphics emulation or hardware graphics emulation which may not work in the Classic environment, and only work while booted into Mac OS 9. If your eMac is too new for booting into Mac OS 9, you may be out of luck. To see which eMac can run booted mode, see this tip:
What can I upgrade my eMac to?

[Solved] 256 color term causes color glitch

Similar Messages

Maybe you are looking for