[Solved] ViM colors

How do I have a ViM colorscheme inherit the background colour that is prescribed in Xresources?---Ideally there would be a command like
hi Normal ctermfg=$XFGLOL ctermbg=$XBG_LOL
Last edited by tomgg (2013-12-24 03:40:46)

Glad that worked, please remember to mark the thread as [SOLVED] by clicking "edit" on the first post.

Similar Messages

[SOLVED] Vim color scheme

Hello! This is my first post and I'm new with Archlinux, sorry if this trouble is very simple but I'm a newbie...
The question... Vim color scheme only works fine when I use sudo or when I'm root...
I've put the color scheme in /usr/share/vim/vim73/colors and in ~/.vim/colors, and I've configured /etc/vimrc and ~/.vimrc
I don't know what's wrong...
Correct color scheme (with sudo):
Wrong color scheme (normal user):
Thank you very much!!
Last edited by Midnith (2012-03-27 11:58:48)

Hi again!
Kaustic wrote:
There's your problem. xterm (as indicated by tput) only supports 8 colours.
If you're using Konsole, check the configuration and change the session to xterm-256color. Alternatively can set the environment variable within your ~/.bashrc file like so: export TERM=xterm-256color
It works! Thank you very much and sorry for the inconveniece
Kaustic wrote:
(PS: To list all the terminals you can use with 256 colours try the following command: (Iirc there was a cleaner way to do this, but alas)
ls /usr/share/terminfo/*/* | grep 256
The output:
/usr/share/terminfo/E/Eterm-256color
/usr/share/terminfo/d/darwin-256x96
/usr/share/terminfo/d/darwin-256x96-m
/usr/share/terminfo/g/gnome-256color
/usr/share/terminfo/k/konsole-256color
/usr/share/terminfo/m/mlterm-256color
/usr/share/terminfo/m/mrxvt-256color
/usr/share/terminfo/p/putty-256color
/usr/share/terminfo/r/rxvt-256color
/usr/share/terminfo/s/screen-256color
/usr/share/terminfo/s/screen-256color-bce
/usr/share/terminfo/s/screen-256color-bce-s
/usr/share/terminfo/s/screen-256color-s
/usr/share/terminfo/v/vte-256color
/usr/share/terminfo/x/xnuppc+256x96
/usr/share/terminfo/x/xnuppc-256x96
/usr/share/terminfo/x/xnuppc-256x96-m
/usr/share/terminfo/x/xterm+256color
/usr/share/terminfo/x/xterm-256color
How I put xterm-256color by default?

[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

[SOLVED] vim color highlighting not correctly displayed in vc/tty

For instance visual selection is set up to change fg/bg to black/green but changes fg to green. Under x using urxvt it displays correctly.
Last edited by Noble (2010-07-26 21:22:19)

I have written my own syntax highlight theme, post below. If you think your script could do anything about it after looking at the file please post But as I said, vim works fine in urxvt, but not when I switch out of X and run it in the vc/tty.
:set statusline=#%n\ %y\ %F\ %r\ %=%c\ %l/%L
:set hlsearch
:set nocompatible
:set noexrc
:set number
:syntax enable
:set autochdir
:set backup
:set backupdir=~/.vim/backup
:set directory=~/.vim/tmp
:set autoindent
:set ruler
:set nowrap
:set nocp
:set scrolloff=5
:set sidescrolloff=5
:set fileformats=unix,dos,mac
:set title
:set laststatus=2
:set tabstop=4
:set autoread
:set showcmd
:set showmatch
:set shiftwidth=4
:set smarttab
:set backspace=indent,eol,start
filetype on
filetype plugin on
filetype indent on
hi clear
set background=dark
if exists("syntax_on")
syntax reset
endif
highlight ErrorMsg ctermfg=red ctermbg=none cterm=bold
highlight WarningMsg ctermfg=red ctermbg=none cterm=bold
highlight VertSplit ctermfg=green ctermbg=black
highlight Folded ctermfg=magenta ctermbg=none
highlight FoldColumn ctermfg=magenta ctermbg=none
highlight FoldColumn ctermfg=magenta
highlight LineNr ctermfg=green cterm=bold
highlight ModeMsg ctermfg=lightgreen cterm=bold
highlight MatchParen ctermfg=black ctermbg=green
highlight Normal ctermfg=white ctermbg=none
highlight SignColumn ctermfg=magenta
highlight NonText ctermfg=blue
highlight Question ctermfg=red cterm=bold
highlight Comment ctermfg=8
highlight Constant ctermfg=green cterm=none
highlight Identifier ctermfg=white cterm=bold
highlight Statement ctermfg=lightgreen cterm=bold
highlight PreProc ctermfg=10
highlight Type ctermfg=2
highlight Special ctermfg=cyan
highlight Error ctermfg=red ctermbg=none
highlight Todo ctermfg=yellow ctermbg=none cterm=bold
highlight StatusLine ctermfg=black ctermbg=green cterm=none
highlight StatusLineNc ctermfg=black ctermbg=lightgreen cterm=none
highlight Directory ctermfg=white
highlight Search ctermfg=black ctermbg=green cterm=none
highlight Visual ctermfg=black ctermbg=lightgreen
highlight WildMenu ctermfg=black ctermbg=cyan cterm=none
highlight Pmenu ctermfg=black ctermbg=green
highlight PmenuSel ctermfg=black ctermbg=lightgreen cterm=none

[SOLVED] vim can't use colorscheme from ~/.vim/colors

Hello
I wanted to use the Molokai Theme for vim. So I downloaded molokai.vim from http://www.vim.org/scripts/script.php?script_id=2340 Copied it to ~/.vim/colors folder. In vim I enter :colorscheme molokai.vim but it can't find it.
Also install molokai-vim from AUR but still. E185: Cannot find color scheme 'molokai.vim'
Any thoughts?
Last edited by blackout23 (2013-04-01 08:15:38)

I'm sure I tried it with and without extension and it didn't work.
However after creating a .vimrc (didn't have one before) according to this:
http://dthettich.tumblr.com/post/131989 … rc-molokai
It worked.
@WonderWoofy
The AUR package installed it into that directory.
Thanks to all!

Terminal colors vs Vim colors [SOLVED]

Hey guys!
I've been using vim since the very first day I started learning programming, and am now using it on my brand new arch system. Everything works really well so far, but I'm having a bit of trouble customizing colors. I wouldn't normally make a big deal out of it, but since I'm going to spend an enormous amount of hours using it for school and personnal projects, I'd really like to get all my colors right. I'm using an urxvt terminal, under awesome wm.
Here are my 16 terminal colors:
http://tinypic.com/r/2yper6b/5
Here is what my vim loks like:
http://tinypic.com/r/s1547k/5
As you can see, vim uses a crap-looking, brownish-red color for line numbers and html tags. This color is not in any of the 16 I specified in .Xresources. I don't know where it comes from, but I would like for vim to use only these 16 colors. Is that possible? I assume it is, because most of my vim colors are changed whenever I edit them in .Xresources.
If not, I'd like to know how I can edit the colors vim uses myself. Thank you for reading!
Last edited by PolyBender (2013-05-12 00:35:41)

You select a colorscheme (:help colorscheme) in your vimrc. The themes can use 256 colors, which I find nice once I customized the theme/scheme. But if you want to limit it to 16, just `set t_Co=16` in your vimrc.

Vim colors in xterm

I really like coding in vim, but with the current vim package in Arch Linux, the colors don't seem to work in all cases. In a standard xterm, the colors in the directory listings are working fine, but when I start vim, it only uses bold and underline and no color whatsoever.
I tried some different terminals, and gnome-terminal has the same problem. But the colors were working fine in aterm and Eterm! Now I don't really like the last two because they are slower, uglier, have all kinds of features I don't use, and the text is flickering when I move the window.
I used to use Slackware and vim colors were working fine in xterm there. Would anybody know what could be wrong with my setup?

Heh, it's one of those things you pick up somewhere. Seriously, I usually use either rxvt or atem. Xterm doesn't do color, I don't know why or how I found out about it. I probably went to deja (now google.groups, I think, I still type deja) and did a search or something.
There are things you pick up somewhere--for example (I was complaining about this to a friend recently, when we were talking about poor documentation) most folks know that kill -1 or killall -SIGHUP restarts most processes (though not all). However, the Linux and FreeBSD man pages don't mention this, they simply say it terminates a process--OpenBSD, which often has better (imho) man pages do mention in passing that it will cause a process to reread its config file (in the example they mention, inetd).
Your attitude is admirable. It's probably in some document somewhere, you could try doing apropos colors--which, in FreeBSD (where I'm writing this) gives about 15 different possible man pages.

[Solved]vim colorschemes not working

Vim colorschemes are not working.When I set a colorscheme with ":color name" colors change just a bit but it don't get nothing even near the theme preview.
I'm using rxvt with zsh.I already tested urxvt colors with a perl script,they're working fine.
Sorry for my bad english and for being such a fucking newbie.
Last edited by instinct (2013-03-13 21:17:32)

I recommend firstly to define all your terminal colors in your ~/.Xdefaults accordingly. Here's a sample from my own ~/.Xdefaults - I'm using urxvt terminal with standard terminal colors:
URxvt.background: rgb:00/00/00
URxvt.foreground: rgb:c2/c2/c2
*color0: rgb:00/00/00
*color1: rgb:a8/00/00
*color2: rgb:00/a8/00
*color3: rgb:a8/54/00
*color4: rgb:00/00/a8
*color5: rgb:a8/00/a8
*color6: rgb:00/a8/a8
*color7: rgb:42/42/42
*color8: rgb:00/00/00
*color9: rgb:f8/54/50
*color10: rgb:50/fc/50
*color11: rgb:f8/fc/50
*color12: rgb:50/54/f8
*color13: rgb:f8/54/f8
*color14: rgb:50/fc/f8
*color15: rgb:f8/fc/f8
You can test your terminal colors with a color script found here.
After that you should set up vim. Start with ~/.vimrc and ~/.vim/colors/yourcolor_scheme.vim.
In ~/.vimrc you should have
set t_Co=256
syntax on
And then you can find yourself a colorscheme that fits you. Now here's the tricky part: the colors in here are defined for terminals (cterm colors) and for gvim (gui colors). I find it hard to get the desired colors using cterm colors, so I am using a script that converts guicolors to the equivalent terminal colors - its called guicolorscheme. After you download the script, put it in ~/.vim/plugin, and add this to the bottom of your ~/.vimrc:
if (&t_Co == 256 || &t_Co == 88) && !has('gui_running') &&
\ filereadable(expand("$HOME/.vim/plugin/guicolorscheme.vim"))
" Use the guicolorscheme plugin to makes 256-color or 88-color
" terminal use GUI colors rather than cterm colors.
runtime! plugin/guicolorscheme.vim
GuiColorScheme hax
else
" For 8-color 16-color terminals or for gvim, just use the
" regular :colorscheme command.
colorscheme default
endif
I have thinkered with my own colorscheme here to get some nice colors, so you are free to use that one, and remember to put it in ~/.vim/colors/.
Last edited by roygbiv (2011-06-07 10:53:06)

[solved] Vim: console and urxvt have different colors

Well, as you can see, vim in console (vc/1) and in urxvt has different colors:
I'd like to have the same colors of console in urxvt (and not the opposite), is there a way?
I don't know from where the colors of urxvt come from. That blue with which is written '#include' and that green/cyan with which is written 'int' aren't even in my .Xdefaults.
TIA
Last edited by andre.ramaciotti (2009-03-08 12:17:16)

andre.ramaciotti wrote:Is there a way to trick vim so it thinks that urxvt is only 16-colours capable? A $parameter or an option I can set in .vimrc?
set t_Co=16

[Solved][VIM] E484: Can't open file syntax.vim

Hi all,
I've installed Archlinux few days ago on my netbook and yesterday i decided to configure Vim using plugins.
During plugins configuration, i messed up and i decided to revome all Vim files in my ~ folder in order to restart configuration.
However, since I've executed the `rm -R .vim .vimrc .viminfo` command, I can't re-activate Vim's syntax coloration using `syntax on` into my .vimrc file nor into Vim directly.
Here is the error message when I start Vim :
Error detected while processing /home/romain/.vimrc:
line 1:
E484: Can't open file /home/romain/.vim/syntax/syntax.vim
Press ENTER or type command to continue
I've found this topic on BBS which seems to be the same problem as me but reinstalling vim or vi doesn't solve this problem.
I've tried to copy this syntax.vim file from /usr/share/vim/vim73/syntax/syntax.vim but it doesn't solve the problem and I want a clean solution without hacking my ~ folder ; moreover, this bug also appears being root while I haven't configured vim with the root account so it may be a problem into Vim's installation folders or something.
Thanks for your help and sorry I my english contains mistakes,
MicroJoe.
Last edited by MicroJoe (2012-06-14 16:16:45)

This is the output :
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 7 2012 00:41:40)
Rustines incluses : 1-547
Compilé par ArchLinux
Grosse version sans interface graphique.
Fonctionnalités incluses (+) ou non (-) :
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs
-dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse
+mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme -netbeans_intg
+path_extra +perl +persistent_undo +postscript +printer -profile -python
-python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
-toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
-xterm_clipboard -xterm_save
fichier vimrc système : "/etc/vimrc"
fichier vimrc utilisateur : "$HOME/.vimrc"
fichier exrc utilisateur : "$HOME/.exrc"
$VIM par défaut : "/usr/share/vim"
Compilation : gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -march=i686 -mtune=generic -pipe -fstack-protector --param=ssp-buffer-size=4 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Édition de liens : gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -L/usr/local/lib -Wl,--as-needed -o vim -lm -lncurses -lacl -lattr -lgpm -ldl -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -fstack-protector -L/usr/local/lib -L/usr/lib/perl5/core_perl/CORE -lperl -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
(I've noticed that some part were in French but I hope that it'll not be a problem).

[SOLVED] `Vim/Gvim: set mouse=a works only in Gvim?

I'm diving into the world of (g)vim this weekend and although I'm starting to get the hang of things, I seem to be having a problem with the mouse functionality. I have set mouse=a specified in my .vimrc and gvim respects it, but when I run vi in a terminal session (urxvt) I have to explicitly type :set mouse=a in ex mode before it will work. Am I missing something?
Here's what I've got in my .vimrc (linked also ~/.gvimrc) so far:
" (G)vim settings
set nocompatible " use gVim defaults
colorscheme wombat " define syntax color scheme
syntax on " enable syntax highlighting
set mouse=a " make sure mouse is used in all cases.
set backspace=2 " full backspacing capabilities
set nocindent " set C style indenting off
set cmdheight=2 " command line height
set ignorecase " ignore case in search patterns
set laststatus=2 " occasions to show status line, 2=always.
set ruler " ruler display in status line
set showmode " show mode at bottom of screen
set number " toggle line numbers
set nobackup " disable backup files (filename~)
set hlsearch " highlight all search results
set showmatch " show matching brackets (),{},[]
" Gvim Settings
set guioptions-=T " disable toolbar icons
set guifont=Consolas\ 8 " backslash any spaces
SOLVED: Silly me I was running 'vi' which has no X support... pacman -S vim fixed it fine.
Last edited by thayer.w (2007-09-04 00:02:49)

I just had an issue with no sound after recent updates. Not sure it's the same problem you are having.
I found I had to open Audio Mixer, select Sound card: HDA Intel PCH (Alsa mixer), Select Controls, check box for Speaker and check box for Headphones. After doing this I found the Speaker volume was set at minimum (although Master and PCM were already set at maximum). Adjusted Speaker volume up and I finally had sound again.

[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!

[SOLVED] Vim : cterm=italic doesn't work

I tried to change the colorscheme in Vim to have comments in italic like this :
hi Comment guifg=#7C7C7C guibg=NONE gui=NONE ctermfg=gray ctermbg=NONE cterm=ITALIC
But this make the comments' color inverted, which is very ugly, and they are not in italic.
I'm using urxvt with the font DejaVu Sans Mono, but I think the problem comes from Vim because I can print italic text in the terminal.
Does someone know if it is possible to fix it ? Thank you !
Last edited by Pascal C.Plusplus (2012-10-30 18:59:45)

If the problem is present outside tmux, then you haven't defined font variants your terminal is supposed to use, e.g.
URxvt.font:xft:DejaVu Sans Mono:style=Book:pixelsize=13
URxvt.boldFont:xft:DejaVu Sans Mono:style=Bold:pixelsize=13
URxvt.italicFont:xft:DejaVu Sans Mono:style=Oblique:pixelsize=13
URxvt.boldItalicFont:xft:DejaVu Sans Mono:style=Bold Oblique:pixelsize=13
With the above, things should work as you wish in a bare urxvt session.
With tmux, however, the case looks differently and depends on the screen-256color terminal definition. There appear to be ways to work around the issue, though personally I'm happy with a regular font and slightly darker fg color for all the comments.

[solved] vim ftplugin vim-latexsuite doesn't load changes with chars

Hello!
I'd like to use some european characters and I found this thread.
Unfortunately I still get "/mathbf{}" when I type the ã. (My problem is the ö but I think if I manage to have the ã it will work with ö...)
The second problem is that I have to press escape twice to go to normal mode in a .tex file.
(In the other files one press is enough.)
All these troubles happen only on my x86_64 desktop.
I have vim-latexsuit-svn 1106-1 on both laptop and desktop from the AUR.
On my i686 laptop everything works fine with the 'default' .vimrc advised in the vim-latexsuite-manual.
There is also a different mapleader for compiling by default. (Which is not as annoying as the ö problem.)
I also get the ö-trouble when I log in from the laptop to my desktop.
Why are there so much differences?
I only remember having put some "set winaltkeys=no" in the wrong files on my laptop before I understood where is the right place.
(Where everything works fine.)
Here's my .vimrc
1 set tabstop=2
2 set number
3
4 syntax on
5 filetype plugin on
6 filetype indent on
7 set grepprg=grep\ -nH\ $*
8 let g:tex_flavor = "latex"
9 set runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim72,/usr/share/vim/vimfiles/after,~/.vim/after
10 "To solve the propleme with vim-latexsuite has with ã and â
11 imap <buffer> <silent> <M-C> <Plug>Tex_MathCal
12 imap <buffer> <silent> <M-B> <Plug>Tex_MathBF
13 imap <buffer> <leader>it <Plug>Tex_InsertItemOnThisLine
14 imap <buffer> <silent> <M-A> <Plug>Tex_InsertItem
15 "imap <buffer> <silent> <M-E> <Plug>Tex_InsertItem
16 "imap <buffer> <silent> <M-e> <Plug>Tex_InsertItemOnThisLine
17 imap <buffer> <silent> <Plug>Traditional <Plug>Traditional
18 map <buffer> <silent> é é
19 map <buffer> <silent> á á
20 map <buffer> <silent> ã ã
21 "imap ã <Plug>Tex_MathCal
22 "imap é <Plug>Traditional
~/.vim/ftplugin/tex.vim
1 set winaltkeys=no
2
3 let g:Tex_AdvancedMath = 0
4 let g:Tex_SmartKeyQuote = 0
5 let g:Tex_SmartKeyQuote = 0
6
7 imap <C-b> <Plug>Tex_MathBF
8 imap <C-c> <Plug>Tex_MathCal
9 imap <C-l> <Plug>Tex_LeftRight
~/.vim/after/ftplugin/tex.vim
(The macros of call IMAP work well. When I type `ö I also get a \mathbf)
1 call IMAP('`w', '\omega', 'tex')
2 call IMAP('`j', '\cdot', 'tex')
3 call IMAP('`A', '\forall', 'tex')
4 call IMAP('`E', '\exists', 'tex')
5 call IMAP('`ö', 'ö', 'tex')
6
7 let g:Tex_AdvancedMath = 0
8 imap <C-b> <Plug>Tex_MathBF
9 imap <C-c> <Plug>Tex_MathCal
10 imap <C-l> <Plug>Tex_LeftRight
runtimepath:
runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim72,/usr/share/vim/vimfiles/after,~/.vim/after
Last edited by Maximalminimalist (2010-05-30 17:00:03)

I just removed vim, vim-auctex (didn't remember there was this...) and vim-latexsuite and reinstalled vim and vim-latexsuite.
I was obviously using a vim-auctex macro and I didn't know it... (This was a memorable lesson for removing packages you don't need. )
I realized that the Esc-issue happens if a placeholder is still active. Is it possible to change this behaviour? (I won't really care about that. => [solved])
Last edited by Maximalminimalist (2010-05-30 16:59:32)

[SOLVED] Some colored text in urxvt displaying oddly

Some colored text does not display correctly in the terminal - but not all. Here's a screenshot:
http://i.imgur.com/xrzCR16l.png
As you can see, the directory names displayed in blue and the executable files displayed in green (not sure why .vimrc is executable..) are all funky looking. However, my username and the regular file names are all displaying correctly. Also all the colored text in VIm in the terminal looks fine as well:
I've read through the Font Config Wiki - Applications Without Fontconfig Support but none of the configs suggested:
Xft.autohint: 0
Xft.lcdfilter: lcddefault
Xft.hintstyle: hintfull
Xft.hinting: 1
Xft.antialias: 1
Xft.rgba: rgb
in my .Xresources file change this behavior. Here is my full .Xresources file without the above settings, its not very long:
! special
*.foreground: #e9ebee
!#93a1a1
*.background: #002b36
*.cursorColor: #93a1a1
! black
*.color0: #002b36
*.color8: #657b83
! red
*.color1: #dc322f
*.color9: #dc322f
! green
*.color2: #859900
*.color10: #859900
! yellow
*.color3: #b58900
*.color11: #b58900
! blue
*.color4: #268bd2
*.color12: #268bd2
! magenta
*.color5: #6c71c4
*.color13: #6c71c4
! cyan
*.color6: #2aa198
*.color14: #2aa198
! white
*.color7: #93a1a1
*.color15: #fdf6e3
URxvt*.transparent: true
URxvt.shading: 100
!URxvt.font: xft:DejaVu Sans Mono:pixelsize==14:antialias=false
urxvt*font: xft:DejaVu Sans Mono:style=Book:antialias=false:size=9, \
xft:WenQuanYi Bitmap Song:size=8, \
xft:FreeSerif:style=Regular, \
xft:unifont:style=Medium:antialias=false
urxvt.scrollBar: false
I would have thought that it has something to do with the colors being defined incorrectly, but the ".vimrc" file is using the same color as my username, and my username is behaving correctly. I'm at a loss and attempting to google "Font Problems in urxvt" gets topics where the the font is incorrect throughout the whole terminal, not just in particular places. Anyone know how to correct this?
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by woodape (2015-04-16 18:36:08)

Try defining your bold font explicitly:
URxvt.boldFont: blah

[Solved] ViM colors

Similar Messages

Maybe you are looking for