[Solved] Vim breaks TTY output
Everything works fine in my TTY until I use vim, then all further input is unreadable gibberish until next boot. I have tested other commands and applications (pstree, canto, iptraf). None of these cause any problems. Only vim.
This is the output from ":language" in vim:
Current language:
"LC_CTYPE=en_US.UTF-8;
LC_NUMERIC=C;
LC_TIME=en_US.UTF-8;
LC_COLLATE=C;
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.UTF8;LC_MEASUREMENT=en_US.UTF-8;
LC_IDENTIFICATION=en_US.UTF-8"
locale:
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=C
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
C
POSIX
en_US
en_US.iso88591
en_US.utf8
Last edited by the sad clown (2013-02-04 13:24:21)
I don't have a complex .vimrc:
" All system-wide defaults are set in $VIMRUNTIME/archlinux.vim (usually just
" /usr/share/vim/vimfiles/archlinux.vim) and sourced by the call to :runtime
" you can find below. If you wish to change any of those settings, you should
" do it in this file (/etc/vimrc), since archlinux.vim will be overwritten
" everytime an upgrade of the vim packages is performed. It is recommended to
" make changes after sourcing archlinux.vim since it alters the value of the
" 'compatible' option.
" This line should not be removed as it ensures that various options are
" properly set to work with the Vim-related packages.
runtime! archlinux.vim
" If you prefer the old-style vim functionalty, add 'runtime! vimrc_example.vim'
" Or better yet, read /usr/share/vim/vim73/vimrc_example.vim or the vim manual
" and configure vim to your own liking!
filetype plugin indent on
syntax on
Similar Messages
-
[solved] NVIDIA 346.35-3 breaks TTY console displays.
I have a GeForce 970, I am using GRUB with GRUB_GFXPAYLOAD_LINUX=keep, and my kernel is booting into 1920x1200 mode. Since upgrading to NVIDIA 346.35-3 my TTY consoles all become garbled and unreadable once X has started, but they are unaffected before X starts.
Downgrading to NVIDIA 343.36-6 solves this issue. There isn't any output in the journal. When I switch to a TTY, my monitor reports that it's in 640x480 mode.
Example:
Anyone else having these problems?
Last edited by gilmoreja (2015-02-27 12:27:00)Hi,
I also confirm the behavior with 2x GTX 970 SLI + Base Mosaic Mode and Nvidia 346.35-6.
Hope this get fixed soon. Or we find a workaround for that issue. -
[solved] How to have line breaks in output of journalctl log
Hello,
How can I have line breaks in the journalctl log output?
At the moment I cannot read most of the log output because it does not fit into my terminal.
See this screenshot: http://i.imgur.com/nUR6Fae.png
Thanks!
Last edited by orschiro (2013-09-20 08:08:04)You can run
journalctl -b --no-pager | less
Edit: If you hit 'h' you get help screen
SUMMARY OF LESS COMMANDS
<snip>
ESC-) RightArrow * Left one half screen width (or N positions).
ESC-( LeftArrow * Right one half screen width (or N positions).
<snip>
It may be possible to configure the way the journal uses the pager so it wraps the lines by default.
Edit 2: Or maybe it can't be configured.
man journalctl wrote:The output is paged through less by default, and long lines are "truncated" to screen width. The hidden part can be viewed by using the left-arrow and right-arrow keys. Paging can be disabled, see --no-pager and section Environment below.
Last edited by karol (2013-09-20 08:02:13) -
[solved] duplicate post TTY terminal on DVI output
Hi
Does someone know how to turn video output on tty over HDMI?
Last edited by infoslaw (2013-06-17 13:50:17)Sorry maybe I need more explain here. When I switch to TTY terminal from KDE environment (ctrl+alt+F2) I would like to have video signal.
I'm docking laptop and connecting via DisplayPort to DVI.
It's working on lower 3.0 LTE kernel but not on last kernel version (my current is 3.9.5.1).
On VGA connection working fine.
Last edited by infoslaw (2013-06-14 07:55:54) -
[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] 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 completion menu broken
Since I upgraded to the latest vim (version 7.3.138, using the gvim package), the completion menu seems to be broken.
Steps of replication:
1. Stand in directory containing files test{1,5}
2. Open vim
3. :e t<tab>
By now vim should show the completion menu saying that there are five files to choose from, but instead the cursor places itself in the file where I last left input, the command area is cleared and no completion is shown. If I enter anything, the cursor returns to the command line and the command line is redrawn with whatever I enter. If I press tab again, the cursor returns to the command area returns and redraws ":e test", nothing further happens.
The error appears in both terminal vim and in gvim, and persists even if I reinstall using the regular vim package. I ruled out my configs breaking it by resetting them to a couple of months ago, but it didn't help.
vim --version && pacman -Qi gvim:
http://paste.pocoo.org/show/358834/
Is anyone else getting this?
EDIT && SOLVED:
It was my configurations after all. "set wildmenu list:longest" made it break for some reason. Without it everything is peachy. \o/
Last edited by Daethorian (2011-03-24 10:49:26)Since I upgraded to the latest vim (version 7.3.138, using the gvim package), the completion menu seems to be broken.
Steps of replication:
1. Stand in directory containing files test{1,5}
2. Open vim
3. :e t<tab>
By now vim should show the completion menu saying that there are five files to choose from, but instead the cursor places itself in the file where I last left input, the command area is cleared and no completion is shown. If I enter anything, the cursor returns to the command line and the command line is redrawn with whatever I enter. If I press tab again, the cursor returns to the command area returns and redraws ":e test", nothing further happens.
The error appears in both terminal vim and in gvim, and persists even if I reinstall using the regular vim package. I ruled out my configs breaking it by resetting them to a couple of months ago, but it didn't help.
vim --version && pacman -Qi gvim:
http://paste.pocoo.org/show/358834/
Is anyone else getting this?
EDIT && SOLVED:
It was my configurations after all. "set wildmenu list:longest" made it break for some reason. Without it everything is peachy. \o/
Last edited by Daethorian (2011-03-24 10:49:26) -
I recently built a new version of LightDM while doing some upgrading, and for the weirdest reason the TTY's are outputting on top of X server, rendering weird blinking cursors in the upper area of the screen. I'm completely stumped as to what is causing this, but I have tried:
Doing a complete system update
Rebuilding LightDM
Trying LightDM's autologin
This bug has also has make my suspend function unfunctional by just giving me a blank screen on startup, which I have to hard reset, and it made my hibernation bugged as well. I'm open to other desktop managers, but I'd prefer to keep with LightDM if possible. I'll post any logs needed if at all necessary. Thanks!
Last edited by shinyquagsire23 (2013-01-10 22:21:43)I have a hairbrained idea ... and want to emphasize that it is hairbrained, but it is easy enough to test.
I've found that many display managers break standard streams (stdin, stdout). This has lead to some problems I had to tinker with in my window managers. Xinit maintains the standard streams, so any output generated by programs in an xinitrc will go somewhere sensible. It's possible that something is generating output and it (for who knows what reason) is going to the wrong places as the stdout stream is broken.
To test, you can use the following wrapper program that will do nothing but close the three streams and replace itself with whatever program followed it on the command line:
#include <stdio.h>
#include <stdlib.h>
int main(int argc, const char **argv) {
const char **args = (const char **) calloc(argc,sizeof(char));
int i;
for (i=1; i < argc; i++)
args[i-1] = argv[i];
fclose(stdin);
fclose(stdout);
fclose(stderr);
execvp(args[0],(char * const *)args);
return 0;
If you save this as wrapper.c you can compile with `gcc -o wrapper wrapper.c`. Then use it infront of whatever command you would use to launch a display manager so `LightDM --my-parameters` becomes `wrapper LightDM --my-parameters`.
If you no longer get the problematic output, this will have pinpointed the problem. If you do, you can rule out the possibility of a stray standard stream.
EDIT: Oops! That code will not *prevent* the problem described, it will *cause* it. But it can actually still be used as a test. But instead of using it to launch a display manager, use it to run xinit: `wrapper xinit`. If you do then get the same problematic output we'll know the broken streams are the problem. If the longshot pays off, and this wrapper replicats the problem when using xinit, then the next step would be to look at your xinitrc.
Last edited by Trilby (2013-01-12 00:38:26) -
[solved]cat with colored output?
just wondering if there is a app like cat, that outputs a file, but with vim/emacs' highlight and line numbering. (or some short of hack)
Why? well, I'm playing around with some C++ and I have multiple little files that I'd like to see on the shell before/after I run g++, and something like that would be quite useful.
Last edited by hack.augusto (2009-10-22 01:13:20)@bl1nk
that's exactly what I imagined for highlight, thanks.
@Ghost1227
`cat -b` ignores blank lines, `cat -n` solved the problem , thanks
[update]
community/colorgcc is kinda cool too
Last edited by hack.augusto (2009-10-22 01:16:24) -
[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] No sound, dummy output
I have no sound on my arch linux installation, and I believe it may be related to updating my kernel. Two weeks ago I had sound working perfectly, however just yesterday I noticed that my output device is listed as "Dummy Output"
I use the following two pulseaudio packages:
pulseaudio 6.0-1
pulseaudio-alsa 2-3
Output from "cat /proc/asound/cards
0 [HDMI ]: HDA-Intel - HDA Intel HDMI
HDA Intel HDMI at 0xf7b14000 irq 32
1 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7b10000 irq 31
Output from "lspci -nn"
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)
00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5)
00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d5)
00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 [8086:8c1a] (rev d5)
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)
00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller [8086:8c4b] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
01:00.0 3D controller [0302]: NVIDIA Corporation GK106M [GeForce GTX 765M] [10de:11e2] (rev a1)
03:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 13)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader [10ec:5227] (rev 01)
05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter [10ec:8723]
Last edited by hextet (2015-02-16 17:21:29)Nevermind I solved the problem!
Simply deleted the director ~/.config/pulse, rebooted, and everything worked! -
[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] cannot access ttys (Ctrl + Alt + F1-F7)
When I press Ctrl + Alt + F1 I just get this error (Ctrl + Alt + F2 brings me back):
:: Loading Initramfs
commandline read: splashy
commandline read: boot
waiting 90 seconds for device /dev/disk/by-uuid/e289..[numbers]..311 ...
... When pressing Ctrl + Alt + F3-F7 I just get blank screen.
Here's the output of ps a:
[det@myhost ~]$ ps a
PID TTY STAT TIME COMMAND
2183 tty2 Ss+ 3:10 /usr/bin/Xorg :0 -audit 0 -auth /var/lib/gdm/:0.Xauth
14044 pts/0 Ss 0:00 bash
14046 pts/0 R+ 0:00 ps a
Last edited by algorythm (2009-08-06 13:05:59)Ii guess that is.. . See my both (/etc/)inittab(.pacsave) files look exactly the same:
# /etc/inittab
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty -8 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty -8 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty -8 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty -8 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty -8 38400 vc/6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null
# End of file
I guess I need to change the vc/s to ttys?
Like this?:
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
Edit: Yeah, thanks man.
Edit 2: Later on I also edited /etc/rc.sysinit the same way
Last edited by algorythm (2009-08-07 22:58:15) -
Hi,
I have installed AMD Catalyst. When I boot, virtual console appears as usual (since I don't use a display manager), I am able to login, and I can run Xorg.
But once Xorg has been launched, if I try to switch back to TTY, only a black screen appears. The console does still work though, if I type startx, Xfce starts again. There is just no text.
I already tried this, but without success.
GPU: AMD Radeon HD 6870
/etc/default/grub Kernel parameters:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset vga=0x0346 cryptdevice=/dev/lvm/Root:root root=/dev/mapper/root resume=/dev/mapper/swap"
/etc/mkinitcpio.conf hooks:
HOOKS="base udev autodetect modconf block keymap lvm2 encrypt filesystems keyboard fsck"hi, I suppose than like me you use xorg 1.17 and catalyst-test from AUR, if is the case here a comment in the package page from packager and maintainer of catalyst stuff:
Vi0L0 wrote:
2015-03-13 21:14
updated to 15.3-1:
- borrowed from ubuntu.
- brings xserver 1.17 support
- its buggy
I was thinking for long time about uploading this driver because I think it sucks . On xserver 1.17 xv video output doesn't work at all, as well as tty terminal, which is sad . After switching to xserver 1.16 it gets back to normal. I remember that in the past AMD did release ubuntu driver which had same bugs.
So it sucks, steam games are working fine, maybe better, but still.
And since this package is called catalyst-test i decided to make this update, you can switch to catalyst-total in no-time.
I also dropped many patches and left only most neccessary, so 1) for intel iommu, 2) for agp 3) for 4.0 kernel support. You can still uncomment dropped one if you want.
Maybe you are looking for
-
I have run disk verification and repair. I have tried resetting the SMS with that- hold down cmd, opt, shift and power at start up trick. I have deleted tons of files that were a waste of space. The problem started after trying to run time machine
-
Hi All, I'bve just bought a new Mac Mini for work, I am trying to run a VGA monitor from the HDMI port using a startech HDMI2VGA Convertor but to no avail.......has anyone had any experience using one of these, or can point me where/why I might be go
-
Hello, Tonight I'm using EVB3 on my MBPro, using the built-in audio. Granted, EVB3 is supposed to emulate an old noisy B3, but I'm wondering if what I'm hearing is more distorted than expected. Take for example "Classic Tonewheel". Try a CMaj chord s
-
Is there a way to adjust snooze time in iCal
Is there a way to adjust snooze time in iCal...please tell me there is!!
-
Error when starting Captivate 6 on Mac
This keeps coming up when I try to start the program. I have uninstalled and reinstalled captivate 6 twice. Any suggestions?