[SOLVED]Vim dosnt recognize 256color urxvt
I want to use rxvt as console, but vim says it dosnt have 256color support.
I downloaded the package rxvt-unicode from the repos, also did some tweaking to .Xresources.
If I execute urxvt and try to use the theme 'xoria256.vim' for vim, it says its not supported.
The output of echo $TERM is : rxvt
Im also having a hard time making urxvt recognize my font..
This is the .Xresources file :
URxvt.font: xft:Terminus:pixelsize=20:antialias=false
URxvt.boldFont: xft:Terminus:bold:pixelsize=14:antialias=false
!black.normal : xoria256.LineNr.guibg
!black.bright : black.normal.rgb - 8
#define _color0 #121212
#define _color8 #0a0a0a
!red.normal : red.bright.r - 8
!red.bright : xoria256.Special.guifg
#define _color1 #d78787
#define _color9 #df8787
!green.normal : green.bright.g - 8
!green.bright : xoria256.PreProc.guifg
#define _color2 #afd787
#define _color10 #afdf87
!yellow.normal : yellow.bright.rg - 8
!yellow.bright : xoria256.Special.guifg
#define _color3 #f7f7af
#define _color11 #ffffaf
!blue.normal : blue.bright.b - 8
!blue.bright : xoria256.Statement.guifg
#define _color4 #87afd7
#define _color12 #87afdf
!magenta.normal : magenta.bright.rb - 8
!magenta.bright : xoria256.Identifier.guifg
#define _color5 #d7afd7
#define _color13 #dfafdf
!cyan.normal : cyan.bright.gb - 8
!cyan.bright : green.bright + blue.bright
#define _color6 #afd7d7
#define _color14 #afdfdf
!white.normal : white.bright.rgb - 8
!white.bright : xoria256.Folded.guifg
#define _color7 #e6e6e6
#define _color15 #eeeeee
!bold : xoria256.Type.guifg
!underline : xoria256.htmlValue.guifg
#define _colorBD #afafdf
#define _colorUL #dfdfaf
!foreground : xoria256.Normal.guifg
!background : xoria256.Normal.guibg
!cursorColor : xoria256.Cursor.guibg
#define _foreground #d0d0d0
#define _background #1c1c1c
#define _cursorColor #ffaf00
URxvt*color0 : _color0
URxvt*color1 : _color1
URxvt*color2 : _color2
URxvt*color3 : _color3
URxvt*color4 : _color4
URxvt*color5 : _color5
URxvt*color6 : _color6
URxvt*color7 : _color7
URxvt*color8 : _color8
URxvt*color9 : _color9
URxvt*color10 : _color10
URxvt*color11 : _color11
URxvt*color12 : _color12
URxvt*color13 : _color13
URxvt*color14 : _color14
URxvt*color15 : _color15
URxvt*colorBD : _colorBD
URxvt*colorIT : _colorIT
URxvt*colorUL : _colorUL
URxvt*foreground : _foreground
URxvt*background : _background
URxvt*cursorColor : _cursorColor
XTerm*color0 : _color0
XTerm*color1 : _color1
XTerm*color2 : _color2
XTerm*color3 : _color3
XTerm*color4 : _color4
XTerm*color5 : _color5
XTerm*color6 : _color6
XTerm*color7 : _color7
XTerm*color8 : _color8
XTerm*color9 : _color9
XTerm*color10 : _color10
XTerm*color11 : _color11
XTerm*color12 : _color12
XTerm*color13 : _color13
XTerm*color14 : _color14
XTerm*color15 : _color15
XTerm*colorBD : _colorBD
XTerm*colorIT : _colorIT
XTerm*colorUL : _colorUL
XTerm*foreground : _foreground
XTerm*background : _background
XTerm*cursorColor : _cursorColor
Last edited by nullwiz (2013-08-29 00:37:12)
thisoldman wrote:
Are you running the Arch box remotely (or using Arch as a guest OS)? I'm asking because CR-LF is a DOS/Windows newline while Linux uses LF only. And terminals can act odd over SSH connections.
Does the file '/usr/share/terminfo/r/rxvt-unicode-256color' exist on your machine? It should have been installed when urxvt was installed.
You can remove the CR+LF warnings by fixing your .Xresources file (but first make a backup). The 'file' command probably produces output something like this:
$ file .Xresources
.Xresources: ASCII text, with CRLF line terminators
You can remove the CRs within vim by using the following command:
:set fileformat=unix
Then save the file. That will get rid of the warnings. For other solutions see http://www.cyberciti.biz/faq/howto-unix … xt-format/
Next, watch your spelling in .Xresources. You misnamed the resource, it's termName, with an uppercase 'N', and there is no terminfo file for urxvt256-color. The correct line is:
URxvt*termName: rxvt-unicode-256color
Wow, you really readed my mind.
I figured it out when I rebooted, it was just throwing errors without a reason.
That indeed was the problem.
Thanks. Marked as solved
Similar Messages
-
[SOLVED] vim status line invisible/wrapped in terminal unless I resize
Hi all,
Whenever I open a file in Vim within a terminal (urxvt, Terminator, xterm) the status line at the very bottom is either invisible or wrapped onto a new line (ie "bot" or "All" will span a line) until I manually resize the window by dragging an edge - this seems to fix the issue (and Vim continues to display correctly even if I continue resizing) . I tried changing the window geometries (in .Xresources for urxvt, and in terminator via --geoemtry) without luck. Changing fonts (type, size) doesn't help either.
I'm running Openbox on a recent Retina MacBook Pro with nVidia drivers, with infinality-bundle installed.
The same behavior occurs under Awesome, and I tried various Openbox themes, all with the same result. So, perhaps its a bash or nVidia issue.
gVim works perfectly though.
Any thoughts?
Thanks!
Last edited by iamjerico (2014-03-26 19:54:12)The status line - the very bottom line - is either (1) below the visible portion of the terminal window - and remains so even if I page down repeatedly (urxvt) - or (2) is visible but the text appearing on it, like "bot" or "all" that are normally visible on the lower right corner, will wrap around (Terminator). That is, I'll see "b" on the bottom right corner and then "ot" on the bottom left but a line lower. In either case, if I manually resize the terminal window, it "catches up" and all appears correctly.
Update: when running Vim without opening a file (just "vim" from the command line), in Terminator ALL of the visible text from the startup text is wrapped (ie "Vim is open source and freely distributable" wraps onto a second line). In urvxt, that text appears normally but the status line is not visible. In both cases, a window resizes corrects the display.
Very strange. -
[SOLVED]vim file specific settings (ie. modelines)
I'm referring to a line in a file s/a
# vim: ft=sh ts=4 et sw=4:
I have that line at the bottom of a .bashrc file. When I open it with vim as a regular user, the settings are applied. When I open it with vim as root (logged in as root; no sudo involved) on the same machine, the settings are ignored. Any ideas as to why this is, or how to fix it?
Both reguser and root have identical .vimrc and .vim folders. If I remove both users' .vimrc, reguser still applies the settings and root still ignores them. I also tried starting vim with full path to rule out any user env. weirdness, no change.
Last edited by alphaniner (2013-08-23 18:10:45)Thanks for all the input and for pointing out it's called a modeline. Not knowing what it's called made it difficult to research.
In the case I cited, I added the modeline just as an experiment. I copied it verbatim from /usr/lib/network/network because I didn't understand it enough to be sure I could just remove ft=sh .
x33a wrote:Vim is reasonably good at recognizing file types, but not always. ...
I remove all comments from a lot of config files. Thus I've also found that vim considers the following (my linux.preset) to have no ft:
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"
PRESETS=('default')
default_image="/boot/caddywhompus.img"
But if I add a new line to the top with just a '#', vim suddenly recognizes it as ft=conf.
Trilby wrote:File specific modelines are quite handy at times, but there certainly shouldn't be a need to specify "ft=sh" in a modeline of bashrc, it is already recognized as such.
Completely unrelated to my experiment with the modeline, but when I back up that .bashrc as root-bashrc it's recognized as ft=conf .
Last edited by alphaniner (2013-08-23 18:19:23) -
[SOLVED] vim-powerline with rxvt-unicode
Hi! I was wondering if anyone has been able to make the vim plugin vim-powerline work with urxvt.
It works fine with gvim and with gnome-terminal once i change the encoding to utf-8. I think there must be something missing form my urxvt configuration.
Here's my .Xresources, maybe some of you guys knows what i'm missing:
URxvt.imLocale: pt_PT.UTF-8
URxvt.scrollBar: off
URxvt.font: xft:Inconsolata-dz-Powerline:pixelsize=12:antialias=true:hinting=true
URxvt*loginShell:true
URxvt*termName:rxvt-unicode
URxvt.perl-ext-common: default,matcher,tabbed
URxvt.urlLauncher: /usr/bin/iceweasel
URxvt.matcher.button: 1
URxvt.perl-ext: default,url-select
URxvt.keysym.M-u: perl:url-select:select_next
URxvt.underlineURLs: true
URxvt.tabbed.tabbar-fg: 2
URxvt.tabbed.tabbar-bg: 0
URxvt.tabbed.tab-fg: 3
URxvt.tabbed.tab-bg: 0
Last edited by ruaz (2012-03-31 12:23:37)I use powerline, but i have it installed via YADR. I had to tweak settings here-and-there as it's oriented towards a OSX install, but on the whole it worked out of the box. What exactly is the issue you're seeing? I think the only special stuff I did was making sure I had suitable fonts, and a snippet along the lines of:
if has("gui_running")
" GUI stuff
else
colorscheme solarized
set background=dark
let g:Powerline_symbols = 'unicode'
endif
EDIT: BTW, I can highly recommend the YADR configs; they are nicely organized and use a lot of nice plugins for any serious dev work.
Last edited by nogoma (2012-03-30 23:15:44) -
[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] Transparent vim in pseudo-transp. urxvt?
Hi,
currently I'm using pseudo-transparency in rxvt-unicode-256color.
Can I have this transparency in vim too? When I start vim the background is set to black.
My .Xdefaults:
URxvt.saveLines: 1000
URxvt.scrollBar: false
urxvt*depth: 24
urxvt*shading: 80
URxvt.inheritPixmap: true
URxvt.secondaryScroll: true
URxvt.foreground: white
URxvt.font: xft:Bitstream Vera Sans Mono:pixelsize=12
URxvt.perl-ext-common: default,matcher
URxvt.urlLauncher: firefox
URxvt.matcher.button: 1
URxvt.matcher.pattern.1: \\bwww\\.[\\w-]\\.[\\w./?&@#-]*[\\w/-]
Thanks in advance
Last edited by Barghest (2009-05-03 17:15:00)Barghest wrote:
Thanks bluewind,
I found out that the reason was this line:
call <SID>X("Normal", "cccccc", "000000", "")
I commented it out and added a new line with ctermbg=NONE.
I guess I could have entered NONE also in the other line? What does it stand for?
It's a function to set colors. (search for "fun <SID>X" in the file to see what it does)
call <SID>X("Normal", "cccccc", "NONE", "")
should also remove the background. -
[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: 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 : 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/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] VIM not displaying many glyphs
I'm struggling to get the full glyph set to display in VIM. Particularly missed are the mathematical super- and sub-script. I've worked on the problem and tried various fixes for displaying UTF-8 characters without success.
(Code block bad form? Ok T. IMHO. There's that type of post where the OP doesn't know why something isn't working and they quote a dump truck of details, even though they're not sure what's relevant and what isn't. And the longer the quote, the harder it is to figure out what they're doing wrong. I didn't want to be that guy. I was hiding the verbosity, in the event my font problems are simpler than I've made it.)
1) Applied settings from these WIKI pages:
Fonts
Xterm
2) Apps I've installed
$ pacman -Qs font
local/dina-font 2.92-4
A monospace bitmap font, primarily aimed at programmers
local/fontconfig 2.11.1-1
A library for configuring and customizing font access
local/fontsproto 2.1.3-1
X11 font extension wire protocol
local/freetype2 2.5.3-2
TrueType font rendering library
local/gsfonts 1.0.7pre44-4
Standard Ghostscript Type1 fonts from URW
local/libfontenc 1.1.2-1
X11 font encoding library
local/libotf 0.9.13-2
OpenType Font library
local/libxfont 1.4.7-3
X11 font rasterisation library
local/libxft 2.3.2-1
FreeType-based font drawing library for X
local/t1lib 5.1.2-5
Library for generating character- and string-glyphs from Adobe Type 1 fonts
local/tamsyn-font 1.10-1
A monospaced bitmap font for the console and X11
local/terminus-font 4.39-1
Monospace bitmap font (for X11 and console)
local/ttf-bitstream-vera 1.10-10
Bitstream vera fonts
local/ttf-droid 20121017-3
General-purpose fonts released by Google as part of Android
local/xorg-bdftopcf 1.0.4-2 (xorg xorg-apps)
Convert X font from Bitmap Distribution Format to Portable Compiled Format
local/xorg-font-util 1.3.0-2 (xorg-fonts xorg)
X.Org font utilities
local/xorg-font-utils 7.6-4
Transitional package depending on xorg font utilities
local/xorg-fonts-100dpi 1.0.1-5 (xorg)
X.org 100dpi fonts
local/xorg-fonts-alias 1.0.3-1
X.org font alias files
local/xorg-fonts-encodings 1.0.4-4 (xorg-fonts xorg)
X.org font encoding files
local/xorg-fonts-misc 1.0.1-3
X.org misc fonts
local/xorg-fonts-type1 7.4-3
X.org Type1 fonts
local/xorg-mkfontdir 1.0.7-2 (xorg xorg-apps)
Create an index of X font files in a directory
local/xorg-mkfontscale 1.1.1-1 (xorg-apps xorg)
Create an index of scalable font files for X
3) A forum search found some common issues:
unicode symbols not working in my terminal
$ localectl
System Locale: LANG=en_US.UTF-8
LC_COLLATE=C
VC Keymap: US
X11 Layout: n/a
$ locale -a
C
en_US.utf8
POSIX
$ echo $TERM
xterm-256color
4) ~/.Xresources
! wiki.archlinux.org/.../Xterm
xterm*termName: xterm-256color
xterm*locale: true
xterm*saveLines: 4096
xterm*bellIsUrgent: false
xterm*VT100.geometry: 80x25
xterm*faceName: Droid:style=Regular:size=12
xterm*dynamicColors: true
xterm*utf8: 2
xterm*toolBar: false
5) ~/.xinitrc
# X11 Fonts
xset +fp /usr/share/fonts
Last edited by xtian (2014-07-27 14:43:23)Linux fonts are a muddle. Consoles can only display 256 characters, maybe 512. You simply cannot display many texts in a console. To navigate through the font mess in X, you need some familiarity with fontconfig. Xft uses fontconfig to select fonts. Fontconfig documentation is not user-friendly.
Droid is a family of fonts. My installation of the Droid family includes 27 different fonts. The command fc-list will list fonts matching a pattern. I usually filter the output by piping through grep. To list the Droid fonts, file name first followed by the fontconfig name, I use:
$ fc-list | grep Droid
Your fc-match results for Droid are from fontconfig doing its best to give you a readable display. Fontconfig cannot find a matching font for the name 'Droid', so it falls back to a "safe" font, 'Bitstream Vera Sans'.
XTerm or UXTerm or URxvt
I have my locale correctly configured, I think. I do not see any real advantage for uxterm over xterm. In my X resources, I include the lines,
xterm*termName: xterm-256color
XTerm*locale: true
For good glyph coverage with xterm, I have found 'DejaVu Sans Mono' to be among the better fonts. If I truly need utf8 coverage, I use urxvt. Urxvt allows one to use a ladder of fonts. If the character is not found in the first font listed, urxvt will search through the other listed fonts until it finds a glyph that can be displayed.
urxvt*font: xft:DejaVu Sans Mono:style=Book:antialias=false:size=8, \
xft:WenQuanYi Bitmap Song:size=8, \
xft:FreeSerif:style=Regular, \
xft:unifont:style=Medium:antialias=false
Here's a screenshot with three xterms using Droid, DejaVu Sans Mono, and Liberation Mono, plus one urxvt using the fonts in the code above. They all show the same portion of Markus Kuhn's utf8 test text. -
[SOLVED] VIM: different syntax highlighting for new vs existing file
I've had this minor nagging issue for a while that I've been trying to figure out, but I just don't know where to look.
It is most obvious with LaTeX files (*.tex). When I create a new file with "vim file.tex" it is recognized as a latex file and I get syntax highlighting, but it seems odd, or off. When I close then reopen the same file, it gets "propper" syntax highlighting.
I gather that this must be because of the two different mechanisms for matching the syntax type: filename versus content. When the file is new, vim only uses the extension. Once there is a latex comand (e.g., "\documentclass{article}") it recognizes it as something else and the highlighting style is different.
It turns out just by actually elaborating exactly what the problem was, I was able to find the solution. I looked for how vim recognizes the files, and found two relevant lines in /usr/share/vim/vim73/filetype.vim on lines 2093 and 2094. Apparently the .tex filetype is not the same as .latex and others. I changed it so it was, and I got the desired behavior.
I thought about just not posting this - but it may be useful for others.You're right about it being overridden. This change should be able to be placed in ~/.vimrc though.
Well that was foolish - I should have read the comments right below in that file. It says exactly how to set it in vimrc. I've now added the following to my ~/.vimrc and this is completely solved without modifying the /usr/... file.
let g:tex_flavor = "tex"
Last edited by Trilby (2013-03-29 16:11:26) -
[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 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
Maybe you are looking for
-
http://youtu.be/4-oBzdAtk-8
-
Stop waiting for event 'SEND_OK_TRANSPORT' of CL_SWF_XI_MESSAGE
Hi, I designed a BPM with a sender requesting for a Transport Acknowledgement. But earlier I defined via IDX_NOALE, that no Ack. should be sent. My problem is now, that I have a lot of messages waiting for the event 'SEND_OK_TRANSPORT' of object type
-
Can't initialize oci. error 1
Dear all: When I login TOAD, I got this error: can't initialize oci. error 1 but sql*plus login can successfully from my client. I've tried to set the NLS_LANG manually in the registry and set the enviroment ORCLE_HOME , but it cannot work. my OS cli
-
Hello All, I have a couple of questions about accruals, our Apps. version is 11.0.2, we have set our Accrue Inventory Items set to On Reciept. We would like to set the Accrue Expense Items to On Receipt also. I have done some research on the issue, b
-
I am using HP pavilion dv6000 PC notebook and operating sytem is widows vista (32 bit) . After upgrading to service pack 2 my dvd drive got disappeared and i tried all possible solutions but could not resolve the issue. Please help in this matter sou