[SOLVED] Odd colours in vim/urxvt

So I'm using the base16 colourset in my Xresources and something really strange seems to be happening. The colours being used by vim to perform syntax highlighting are just wrong. As in, there are colours being used that aren't even specified in my Xresources file.
Periodically, like 1 out of 50 calls to vim they will look "correct".
$TERM is rxvt-unicode-256colors
Nothing to do with colours or colour schemes in my .vimrc.
Can anyone tell me what's going on here?
EDIT: I should add that the colours look strange for commands like ls as well.
Last edited by Vixus (2012-11-05 15:43:23)

doug piston wrote:Well to my knowledge (Someone correct me if I am wrong), Vim doesn't look at your .Xresources by default. You can make it do such a thing but using the a colorscheme is still a better option. Just install the colorscheme, I do not see why you don't want to...
Sorry, I may not have explained clearly, but I did try and install the base16 colorscheme for vim, following all the steps that the author provided. However there were some steps involving running bash scripts that just didn't work, most likely why the colorscheme didn't work.
Thanoulis wrote:1) Vim always uses a colorscheme, even if not present in .vimrc. In that case it uses :colorscheme default.
This I did not know. Thanks for telling me. In that case I guess there are bugs in the base16 colourscheme for vim (as a lot of comments on the repository seem to suggest).
2) In Xresources, we define the terminal's color palette, not vim's colorscheme. My guess is that you use a different color palette for urxvt and xterm (hence the differences in vim colors)
I don't, since I only have one Xresources file that presumably applies to both terminal emulators.
3) The weird looks from your ssh session, is because in the host machine there is not a valid terminfo file. Usually its fixed by installing the same type of terminal emulator in both machines.
Ugh, really? I never thought that was necessary... can I fake this in any way? I don't have sudo access to any of the work machines I ssh into.
If you really like the base 16 colors in vim, try :colorscheme peachpuff (it's the one i use, and comes with vim).
Thanks, this worked a treat!

Similar Messages

My imac screen display is unfocussed, odd coloured and blurred (caused by rogue cate walking over keyboard). I have no idea what settings have changed or what to check. Any ideas?!

My imac screen display is unfocussed, odd coloured and blurred (caused by rogue cate walking over keyboard). I have no idea what settings have changed or what to check. Any ideas?!

It could be a number of keyboard shortcuts, here's a few.
If the screen is zoomed, hold CNTL and scroll down with mouse or trackpad.
If screen looks like a negative, hold down CNTL OPT CMD and click 8.
Let us know how what other symptoms are shown.
Regards,
Captfred

[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

System Yank Register in Vim+URxvt Without Mouse [SOLVED]

As I understand it, to use the system clipboard you have the choice of the selection or the cut buffer that are accessed through vim's * and + registers.
But as far as I can tell, this feature doesn't work with the vim from the repository. Older threads refer to it as working but I cannot get it to work, and I suspect vim was built without support for X.
There is of course the workaround to do a Shift-LMB drag which bypasses vim and has the intended effect, but this impractical when you don't have a mouse.
So how can I get the * and + registers working? If they were disabled, why? Or am I just being stupid?
Advice is greatly appreciated.
Last edited by egan (2010-01-24 21:13:26)

tom5760 wrote:I'd just install the "gvim" package. You can still use regular console vim, but its built with X so you can do what you want. Seems reasonable to me.
Yeah, I just did. I was worried that it would be too heavy or whatever but it seems fine, and copy and paste works. And back when I was in Ubuntu I stilled used GVim so I am okay with it.

[SOLVED] X clipboard in vim + xclip

I've struggled with this for some weeks. "*y is supposed to update PRIMARY and "+y is supposed to update CLIPBOARD. When I use "*y in vim, I can paste it urxvt, uzbl etc with shift+insert, but xclip -o doesn't work, no matter which -selection. When I use "+y, however, xclip -selection clipboard -o works as expected.
With autocutsel running (
autocutsel -selection PRIMARY -fork
autocutsel -selection CLIPBOARD -fork
), "*y and "+y both update CLIPBOARD, so xclip -selection clipboard -o works, but PRIMARY still isn't used.
Is there a bug here or is there something I don't understand about X11's jungle of clipboards?
EDIT: I installed parcellite and checked "synchronize clipboards". Solved everything
Last edited by JohannesSM64 (2010-04-29 14:43:55)

Thanks, seems like the right way to go. But how do I go about installing it?
It requires libgl, but libgl conflicts with nvidia-utils.
Right now I've removed nvidia, installed libgl and then xorg-server-warnaud, and yes, I have X now. But it runs single monitor on the vesa driver. Normally I use nvidia-settings to generate my xorg.conf. Do I really have to set it up to dual monitor myself?
Ideal setup would be xorg-server-warnaud, nvidia and dual monitor. Any help on a procedure?
EDIT: Oh, and I'm also unable to fullscreen mplayer with the current setup.
Last edited by atc (2009-05-04 14:54:27)

[SOLVED] set columns in vim does not work

I would like to set the window size of my vim to 95 when working with markdown files, so put
set columns=95
into an autosourced file when opening Markdown files. Unfortunately this has no effect and when I look at
set columns?
the window size is still 179 characters long.
When I try to do
set columns=95
with vim already open, vim very shortly resizes the text/window, but after a second return to the original size which is 179 character (screen width)
I tried ot figure out if it is a problem of my .vimrc by temporaliy working with a new empty .vimrc but the problem remains the same. I tried it out in another terminal emulator, but the problem remains the same. I tried it out logged in as root user before starting the XServer and here it worked as expected. So my gues is it has to do or with a X setting or with my window manager or with my shell.
I am using i3, urxvt and zsh in the context where it didn't work and the Arch install default setting in the context where it works. Still I have no clue what causes the problem.
Last edited by cutuchiqueno (2013-12-05 12:18:36)

x33a wrote:I believe you'll need to float urxvt in i3 to do that.
Thanks, I haven't thought of that possibility and it works. Although what I wanted to achieve is not possible with this solution though I found the Vimroom plugin which did the job, so thanks again.

[Solved] How to set vim -R as a viewer for mc?

Hello!
I am trying to set vim in read only mode as a viewer for Midnight Commander.
I tried:
alias mc='VIEWER="vim -R" mc'
or
alias vimr='vim -R'
alias mc='VIEWER=vimr mc'
and more but without success.
So far the only successful approach was to:
- create shell script, e.g. vimr.sh containing "vim -R"
- create an alias using the script, i.e. alias mc='VIEWER=vimr.sh mc'
It works, but creating additional file doesn't seem to be optimal solution.
Is there a way to solve it using one-liner, or at least put all the config into .bashrc?
Last edited by satori (2014-09-19 19:03:14)

Thank you for your quick replies.
@alphaniner:
alias mc='VIEWER=vim\ -R mc'
does not work as intended - it launches vim but I am still able to modify viewed file, like -R had no effect
@WonderWoofy:
If you mean exporting variable like
export VIEWER='vim -R'
it has the same effect as described above. Additionally, it sets the viewer for all applications using that variable, which I would like to avoid.
Unfortunately this is not what I am looking for.

[SOLVED] Odd window manager problem...

I have installed Arch and a full Gnome DE. However when I start gnome, I get an odd window manager. I tried metacity and metacity --replace in a terminal, but I just get "Window manager warning: Screen 0 on display ":0.0" already has a window manager"
Here is what it looks like:
Any way I can get some metacity going?
Edit: [SOLVED]
I just put metacity as startup application and restarted. Still not sure what that window manager was, but I'll be okay I guess...
Last edited by phohammer (2010-03-03 02:59:43)

sand_man wrote:
haha you had gnome running with twm as the window manager instead of metacity.
You need to put 'exec gnome-session' in your .xinitrc file.
twm huh? Well that's a new one for me!
I tried to do that but the .xinitrc file didn't exist yet and I wasn't sure if I should make it...I think I tried ~/.xinitrc . Would it be in another directory?

[SOLVED] How to convince vim my terminal supports color?

Hi. I recently got a shell account from Kaitocracy on his linode machine. I noticed that my bash prompt has color, as expected, but when I copied over my vim configuration (which includes a color theme), it didn't work! After some toying around, I noticed that vim recognizes the terminal escape codes using `:hi <type> start= stop=`, but not the existing `cterm` commands in my color theme. To make things more confusing, I know my terminal (urxvt) is capable of using the cterm flags.
Also, Ctrl+L does not clear/redraw the screen as expected.
What can I do to fix these issues? Here are the configs:
~/.vimrc:
" No vi compatibility; strictly vim here.
set nocompatible
" Don't source /etc/vimrc
set noexrc
" My background is always black
set background=dark
" The mouse is helpful every now and then...
set mouse=a
" I'm a Linux user
set fileformats=unix,dos,mac
" Search while I type
set incsearch
" The blinking pisses me off
set novisualbell
" Line numbers are key to debugging
set number
set numberwidth=5
" My tabs are 4 characters long
set tabstop=4
set softtabstop=4
" Indention is also 4 characters
set shiftwidth=4
" Normally, I don't want tabs converted to spaces.
set noexpandtab
" Syntax highlighting is a staple :D
syntax on
" I want liberal use of hidden buffers, just in case.
set hidden
set laststatus=2
" filename, filetype, readonly flag, modified flag line #, column #, %age of file length, hex value of byte under cursor.
" Ex: .vimrc [vim][+] 48,22 55% hex:20
set statusline=%f\ %y%r%m\ %l,%c\ %P\ hex:%B
set noai
" I can see where tabs and line endings are
set listchars=tab:▸\ ,eol:¬
" This turns on the config above; I can turn it off with :set nolist
set list
" I want wordwrap on, coupled with sane line-breaking. This will not work when :set list is active.
set wrap
set lbr
" My color scheme is pwn
colorscheme sporkbox
filetype indent on
if has("autocmd")
" enable filetype detection
filetype on
" I want to convert tabs to spaces to adhere to PEP 8.
autocmd FileType python setlocal ts=4 sts=4 sw=4 expandtab
endif
" \l toggles invisibles
nmap <leader>l :set list!<CR>
" I like to get rid of trailing white space.
nnoremap <silent> <F5> :call <SID>StripTrailingWhitespaces()<CR>
" Fast window movement is important
map <C-h> <C-w>h
map <C-j> <C-w>j
map <C-k> <C-w>k
map <C-l> <C-w>l
" Courtesy of vimcasts.org
function! <SID>StripTrailingWhitespaces()
" Save last search and cursor position
let _s=@/
let l = line(".")
let c = col(".")
" Do the business:
%s/\s\+$//e
" Restore previous search history and cursor position
let @/=_s
call cursor(l, c)
endfunction
~/.vim/colors/sporkbox.vim:
" Color scheme "sporkbox"
" by Daniel Campbell <[email protected]>
" Tab characters and EOLs should be dark gray so they don't stand out too much.
highlight SpecialKey ctermfg=darkgray
highlight NonText ctermfg=darkgray
" If I'm in a mode, I want to see it.
highlight ModeMsg ctermfg=green
" The current file should be obvious; the others can be faded.
highlight StatusLine ctermfg=green ctermbg=black
highlight StatusLineFC ctermfg=darkgray ctermbg=white
" Line numbers should be just-visible, not bright.
highlight LineNr ctermfg=darkgray
" Titles in Markdown
highlight Title cterm=bold ctermfg=white
" My splits should not be bright
highlight VertSplit ctermfg=black ctermbg=darkblue
highlight Comment ctermfg=darkgreen
highlight Constant ctermfg=cyan
highlight Identifier ctermfg=yellow
highlight Statement ctermfg=magenta
highlight PreProc ctermfg=lightblue
highlight Type ctermfg=blue
highlight Special ctermfg=lightblue
Remote .bashrc:
### ~/.bashrc: Sourced by all interactive bash shells on startup
# Set a fancier prompt
PS1='\[\e[32;01m\]\u\[\e[m\] \[\e[36m\]\w\[\e[m\]: '
# Turn on colors for ls and grep
alias less='less --RAW-CONTROL-CHARS'
alias ls='ls --color=auto'
alias grep='grep --color=auto'
# Set colors for ls and friends
if [ -f ~/.dir_colors ]; then
eval `dircolors -b ~/.dir_colors`
elif [ -f /etc/dir_colors ]; then
eval `dircolors -b /etc/dir_colors`
else eval `dircolors -b`; fi
# Compilation optimization flags
CHOST="i686-pc-linux-gnu"
MAKEFLAGS="-j2"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=both"
CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
FFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
CPPFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
export PGHOST="private1.kiwilight.com"
export PS1 CHOST MAKEFLAGS LDFLAGS CFLAGS FFLAGS CXXFLAGS
To make matters more confusing, my vim theme works when I connect to the linode in a GNU screen session, but not when it's a straight-up terminal.
Last edited by xelados (2010-04-25 00:34:44)

Mr.Elendig wrote:Make sure you are using rxvt-unicode-256color and that your TERM is rxvt-256color outside of screen, and screen-256color inside of screen.
That's the peculiarity of the problem; when I run vim in my local environment, I always get color using the `:hi <hilighttype> ctermfg=* ctermbg=*` commands. This applies inside of X through rxvt-unicode (non-256color), GNU screen, and on the plain command line in vc1. This issue seems to be related to the remote environment and/or variables not being sent through ssh.
@moljac: When I echo'd TERM inside a screen session, it returned "screen", so I don't know whether it's legit or not.
Last edited by xelados (2010-04-24 11:47:52)

Vim/urxvt sessions

I use xmonad, urxvt, and vim for development, but there is no session saving such as in geany or kate. Is there any way I can open a project one file at a time, save a session, reboot, and then open the same session with a few commands and not one (file) by one? I'm perfectly fine with any level of hackishness .

Lexion wrote:I use xmonad, urxvt, and vim for development, but there is no session saving such as in geany or kate. Is there any way I can open a project one file at a time, save a session, reboot, and then open the same session with a few commands and not one (file) by one? I'm perfectly fine with any level of hackishness .
Do an initial
:mksession
and save the file (usually "Session.vim") at some suiting place.
To save later editing sessions I did set up a keybinding for this in my .vimrc:
" --- Define a session save shortcut ---
:map <C-F12> :wa<Bar>exe "mksession! " . v:this_session<CR>
Afterwards reopen the session with
vim -S <where-your-Session-file-was-saved>
Last edited by bernarcher (2009-09-10 07:17:41)

Lightroom 3.6 is giving me odd colours.

Hi,
I'm shooting RAW files on a Canon 550D
I am also using Canon DPP software as well
I have a custom screen profile created with a ColorVision Spyder2
I'm using a Canon pixmania MG6250 with genuine Canon Inks and Paper
I'm Using the PRINTER'S profile to manage output (not perfect but not bad either)
In Lightroom 3.6 I am getting very odd color problems. Not all colors seem to be affected but most particularly lips in portraits are hugely over saturated with a positive red shift. Reds in general are too saturate but this doesn't extend to a red colour cast. In lightroom I have assigned the correct camera profile (e.g. almost always camera faithful).
When I look at the same file (both LR and DPP unaltered) the colours are what I expect them to be in DPP but not in LR.
When I print the files from LR and DPP I get exactly the same results as with the screen colours for both programs. I have checked for updates but without success.
Any suggestions?

LR Adobe Standard should give you very similar color rendering as DPP Camera Faithful. Based on your description I would try adjusting LR's White Balance and make sure Vibrance and Saturation are set to '0,' and then compare the difference between DPP and LR.
If still different check to make sure your Spyder 2 software is set to create ICC v2 profiles and NOT v4 profiles. You might also try creating a new display calibration profile. LR is very picky about any inconsistency in the display profile. When every other application looks fine except LR, the display profile is the first thing I would investigate.

[SOLVED] problem with zsh and urxvt and keybinding

I hope this is the right forum to post this problem, else please move it to the right forum.
I have zsh and urxvt installed and I am quite pleased with it, except for one problem,
When I push the delete button in urxvt I get a ~ instead of deleting the next character. In aterm and xterm I don't have this problem.
I'm sure that there is a way to make the right keybinding for this, but I can't find the solution. Is there someone who can point me in the right direction?
Last edited by NeoXP (2009-02-24 21:00:02)

These are my most current bindkeys...
case $TERM in (rxvt*) #urxvt
bindkey "\e[7~" beginning-of-line
bindkey "\e[8~" end-of-line
esac
bindkey "^A" beginning-of-line
bindkey "^E" end-of-line
bindkey '^?' backward-delete-char
bindkey "\e[3~" delete-char
Open a terminal, hit ctrl-V, and press delete. It should print the key generated. The first ^[ is escaped as \e.
So, on my terminal I see ^[[3~
I put bindkey "\e[3~" delete-char in my ~/.zshrc, and there you go.

[SOLVED] Bash coloured prompt issues

Hi, I'm having trouble with my bash prompt and after going through a sea of posts on prompts I can't seem to figure out why mine isn't giving the desired behaviour.
YELLOW='\[\e[0;33m'
WHITEBOLD='\[\e[1;37m'
WHITE='\[\e[0;37m'
ORANGE='\[\e[1;31m'
PS1="${WHITE}[${ORANGE}\u\] ${YELLOW}\@\] ${WHITEBOLD}\$(parse_git_branch)\] ${ORANGE}>\] ${YELLOW}\w\]${WHITE}]\] \$"
The desired output:
[will 06:48 PM (master) > ~/.vim] $
When I scroll through the history the prompt messes up and starts looking like this:
[will vim ~/.bashrc
Last edited by will.price94 (2012-02-27 21:02:26)

The prompt counts your color sequences as characters which messes up the cursor position. Escape the ${WHITE} and ${YELLOW} etc. by putting them between \[ \] like this: \[${WHITE}\] . In your case, include the closing \] when you define the color variables, so
YELLOW='\[\e[0;33m\]' so you don't have to worry about them in the PS1= sequence.
Edit: try like this (maybe remove some spaces, haven't tried the prompt myself)
YELLOW='\[\e[0;33m\]'
WHITEBOLD='\[\e[1;37m\]'
WHITE='\[\e[0;37m\]'
ORANGE='\[\e[1;31m\]'
PS1="${WHITE}[${ORANGE}\u ${YELLOW}\@ ${WHITEBOLD}\$(parse_git_branch) ${ORANGE}> ${YELLOW}\w${WHITE}] \$"
Last edited by VCoolio (2012-02-27 20:26:34)

[Solved] Cannot poweroff/reboot in urxvt

Hi all,
I'm running StumpWM with no desktop environment, and in the past was able to shut down the machine from within an xterm as a regular user using 'systemctl poweroff' (or systemctl reboot to reboot, etc). I recently started using urxvt in daemon mode as my console program because it seemed like a clean solution to having multiple consoles open. From within urxvt, when I try to run systemctl poweroff, I get the following error:
$ systemctl poweroff
Failed to execute operation: Interactive authentication required.
Failed to start poweroff.target: Interactive authentication required.
I can start an xterm and shutdown from there, or use Ctrl-Alt-F2 and log in to a non-X tty and shut down there, all as a regular user.
I've seen other posts where the information in loginctl session-status c1 was requested, so here it is:
$ loginctl session-status c1
c1 - Lefty (1000)
Since: Sun 2014-12-07 16:51:25 CST; 13min ago
Leader: 1104 (login)
Seat: seat0; vc1
TTY: tty1
Service: login; type tty; class user
State: active
Unit: session-c1.scope
├─1104 login -- Lefty
├─3005 /bin/sh /usr/bin/startx
├─3317 gpg-agent --daemon --enable-ssh-support --write-env-file /home/Lefty/.gnupg/gpg-agent.env
├─4525 xinit /home/Lefty/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -auth /tmp/serverauth.SrQT9ulZaj
├─4583 /usr/bin/Xorg.bin -nolisten tcp :0 vt1 -auth /tmp/serverauth.SrQT9ulZaj vt1
├─5502 xf86-video-intel-backlight-helper acpi_video0
├─6155 /home/Lefty/Downloads/Stumpwm/stumpwm/stumpwm
├─7066 xulrunner /usr/share/conkeror/application.ini
├─7097 /usr/bin/dbus-launch --autolaunch be7bdc12ca34453d943a6560e1975268 --binary-syntax --close-stderr
├─7098 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
└─7224 /opt/google/talkplugin/GoogleTalkPlugin
It doesn't look like I'm showing up as a remote user. And the output is the same when run from an xterm. Any idea what I'm doing wrong in urxvt?
Thanks!
-Lefty
Last edited by LeftyAce (2014-12-08 17:09:55)

The wiki page doesn't mention starting the daemon using .xinitrc at all. The section about using the daemon mode only describes two ways to start it through systemd (https://wiki.archlinux.org/index.php/rx … gh_systemd).
At the very least, it looks like I should add a section on using the daemon/client setup in a single user system (through .xinitrc).
Is there a reason someone would _not_ want to run it this way? Does it cause problems for multi-user systems?
EDIT: I updated the page to include .xinitrc instructions and to add a note to the systemd section mentioning the problem with power on/power off. If anyone has more information about why the systemd configuration is desirable I would be happy to add that information as well.
Last edited by LeftyAce (2014-12-08 17:02:23)

[SOLVED] This is how my urxvt looks several times a day. But why?

Completely garbled text and no cursor:
http://i.imgur.com/uou0S.jpg
I have no idea what the cause is. A reboot solves it for some hours. Sometimes other applications like Firefox show similar fragments.
System is up to date.
Last edited by Markus00000 (2011-10-19 09:22:38)

Markus00000 wrote:
lifeafter2am wrote:Using compositing by any chance?
Nope. Just plain xmonad.
I run XMonad as well, but with xcompmgr, and I get issues occasionaly with the intel drivers; but that looks different to what I get anyway. Are you using the rxvt-unicode package from the main repositories or one from the AUR? Do you have a lot of rxvt options in your .Xdefaults? (Taking shots in the dark here )

[SOLVED] Odd colours in vim/urxvt

Similar Messages

Maybe you are looking for