[SOLVED] Bold in Vim

Hello, people.
I'd like to know how can I activate bold fonts in Vim. But it's a weird situation, because:
- bold fonts do not work if I'm using Vim from pure URxvt; but
- they work if I'm using Vim inside tmux; and
- it's not a font problem, because the command prompt is bold, and Vim is using the same font; and
- it's not a color scheme problem, because Vim uses the same in and out of tmux.
So, how come bold works only inside tmux with Vim?
Thank you very much.
Last edited by jpmelos (2011-06-04 23:09:14)

Uh... Interesting. Now there's no bold inside and outside tmux.
I do not know about this stuff, so I'm just guessing, but this makes sense to me:
Could it be that my Vim is loading a color scheme for 256-color terminals that doesn't have bold in it, and then when using terminals that doesn't support 256 colors, it loads a color scheme that does support bold?
Sorry if that's complete and utterly bullshit, I'm just trying to help you help me! But if that's it, how do I make this color scheme for 256-color terminals support bold? Because I kinda like this color scheme better than the bold one! Just that it would be better with the bold settings from the other one.
Thank you!

Similar Messages

[SOLVED] Bold monospace fonts and rendering

Hi everybody,
I chose to use the Inconsolata font (http://www.levien.com/type/myfonts/inconsolata.html) everywhere I need a monospace font.
However I have an issue with this setup. Since Inconsolata font doesn't have a bold variant, when "bolding" it, it gets rendered with a different width (it's not monospace anymore)
This happens, for example, inside an Eclipse editor or even in gEdit.
I've also noticed that in some applications (e.g., gnome-terminal or x-chat), bold is correctly displayed using the same width of the normal variant.
I've read the https://wiki.archlinux.org/index.php/Font_Configuration page and, in particular, the "disable autohinter for bold fonts". I actually don't use the auto-hinter so I tried different configuration but without luck.
Does anyone have an hint for solving this inconsistency?
Thanks.
P.S.: To better understand what I am talking about you can have a look at this image: http://imageshack.us/photo/my-images/85 … olata.png/
Last edited by fm (2012-01-14 21:41:36)

brebs wrote:
fm wrote:I actually don't use the auto-hinter so I tried different configuration but without luck.
If the app doesn't use fontconfig, then changing fontconfig settings won't help
That's clear. But gnome-terminal and gEdit aren't they supposed to use the same backend, i.e., fontconfig?
Because gnome-terminal works fine. gEdit doesn't.
Thanks.

[SOLVED] Problem with vim and wombat colorscheme

Hi there,
I'm having some problems with wombat colorscheme for vim. It's just working on gvim.
I read somewhere that wombat just work in gvim. Is that right ? I'm already using a 256-colors terminal (rxvt-unicode).
I looked here in the forum, but I didn't find anything about.
Just for information I downloaded it from http://www.vim.org/scripts/script.php?script_id=1778
Last edited by lsathler (2011-07-06 18:11:00)

yngwin wrote:You can use wombat256: http://www.vim.org/scripts/script.php?script_id=2465
Thanks for helping. It worked like a charm !

[solved] confusion about vim and its config files

Hi, Im getting really confused with vim and its /etc/vimrc config, and the per user ~/.vimrc.
On one of my PC's I have an untouched /etc/vimrc and a /home/jason/.vimrc which has:
syntax on
now, on that same PC, if I run
vim .vimrc
"syntax on" in green and yellow as expected, and if I run
sudo vim .vimrc
I also see
"syntax on" in green and yellow, but surely this is opening it as root?
*Edit
Even though there is no .vimrc in /root, and the system-wide /etc/vimrc is untouched/blank
On another PC I also have an untoched /etc/vimrc, and a /home/jason/.vimrc which has:
syntax on
Aswell, and:
vim .vimrc
has "syntax on" in green and yellow as expected, but this time:
sudo vim .vimrc
Has no colour?
I cant explain this, any ideas?
*Edit
To clarify, both PC's have an untouched /etc/vimrc and there is no /root/.vimrc file on either PC
Last edited by jrussell (2013-04-14 10:21:42)

siriusb wrote:
The configuration files in /etc are for system-wide settings. These are the default settings if not overridden by a user's own settings in their home directory.
So running vim as your regular user will use the settings from your home directory.
What does sudo? From man sudo
sudo allows a permitted user to execute a command as the superuser or another user, as specified by the security policy.
So if you didn't specify any setting in the home folder of the user you want to run vim as, and you don't have anything in /etc/vimrc, vim won't apply any custom settings.
I understand all of that, but on both my PC's I have a clean/untouched config /etc/vimrc, and both /root/.vimrc files do not exist, so howcome on one PC I get colour with sudo vim...., and on the other I dont?

[SOLVED] Upgrade broke vim, tmux, j4-desktop (and perhaps more)

I just upgraded my systems, and now several strange things are happening.
I'm using powerline fonts in tmux and vim/gvim. In gvim, everything behaves normal, but in vim, the fonts are just plain broken. Typing space just writes Â.
The fonts are also just plain broken in the terminal - tmux doesn't show anything in the statusline at all, while the output is garbled in vim.
Trying to start j4-dmenu-desktop also gives an error:
j4-dmenu-desktop --dmenu="dmenu -p 'open' -i -z "
SearchPath: /usr/share/applications/
SearchPath: /home/simendsjo/.local/share/applications/
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
[1] 18502 abort (core dumped) j4-dmenu-desktop --dmenu="dmenu -p 'open' -i -z "
I noticed the upgrade included glibc and openjdk among other things.
I don't even know where to start trying to figure this out. Any help would be greatly appreciated.
Last edited by simendsjo (2014-09-16 08:45:32)

Scimmia wrote:What is the output of `locale` and `locale -a`?
$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
nb_NO.utf8

[SOLVED] scope with vim

hello
I have installed vim and cscope but when i have cscope executed (cscope -R) and tryied to use ":cs" in vim i get this error "cs: No such command from open/visual"
Is there any way to fix it ? Is there a compilation problem or what ?
Thank you.
Last edited by netpumber (2013-07-02 16:32:57)

Finally i fixed it. The vim-cscope package doesn't need.
1) I unzip in ~/.vim the cscope.zip file from here http://www.vim.org/scripts/script.php?script_id=4082
2) Add in the ~.xinitrc file the export EDITOR=vim
And now all works beautiful!

[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 : 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] `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: 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)

Urxvt - transparency - vim ? - SOLVED-

I'm runnung urxvt with real transparency by putting this in my .Xdefaults:
URxvt*depth: 32
URxvt*background: rgba:2121/2121/2121/aaaa
vim gives me error codes when I try to run it in a transparent terminal:
BadMatch (invalid parameter attributes)
Vim: Got X error
Vim: Finished
If I run Vim -X I can get it to work, but then I lose the nice X stuff like buffer copying with the middle mouse button.
I've looked around, but can't find anyone having or addressing this problem? Any ideas from urxvt users out there?
Thanks
tdphys
SOLVED
Gah...
I didn't have URxvt at the beginning of the two lines in my .Xdefaults. How embarrasing since i added them for the initial posting. Goes to show, dumb mistakes are only solved after posting to the forum.
Sigh...
Last edited by tdphys (2008-09-04 19:22:44)

Quick update: I was thinking about this - the wiki post can only be mentioning pseudo transparency ("non-standard wallpaper setters"), so it wouldn't apply to this situation (true transparency via compiz). After a little searching, I found this :
It seems the newest version has the copy-background-to-pixmap method overriding true transparency if that is set by the resources. That's the opposite of the way it used to be, but otherwise works. I just had to remove the other background settings, such as .inheritPixmap and .tintColor, and it works again.
So I commented out those resources in my ~/.Xdefaults ... and it works!
So, really solved.

[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] 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] vim, indent and hash

I know this isn't strictly a programming problem, but bear with me...
To make a long story short, I have a Perl file in which some comment lines start with the hash(#) as the first character of the line, i.e. before the # there's nothing, not even spaces. The problem is that trying to indent this line with == does not work. Now, with my current vim setup, when *insert* a new line that starts with an #, indentation is done properly. Also, if there is space before the #, but the indentation is wrong, == correctly indents it. The problem is when the # is the very first character of the line, and (it goes without saying) the indentation is wrong, == does nothing.
I've googled and read all about disabling smartindent, cindent, and whatnot, and nothing seems to work. I'm really grasping at the straws with this one, so all ideas are welcome...
Last edited by gauthma (2010-10-26 16:22:11)

For future reference of whomever might encouter this problem... the file /usr/share/vim/vim73/indent/perl.vim has, in line 55 and following, the, erm, following:
" Don't reindent coments on first column
if cline =~ '^#.'
return 0
endif
Commenting those out solved the problem. Of course I now wonder why would those lines be there in the first place, but I digress...

[SOLVED] Bold in Vim

Similar Messages

Maybe you are looking for