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

Similar Messages

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

Massive copy to system clipboard with vim?

Say I'm editing a program with vim through a terminal (say xterm). Does anyone know how to copy the contents, via left click highlighting, onto the system clipboard (x11) when the content that needs to be copied is physically off the screen? I've tried to arrow up while highlighting but it doesn't work.

toxic, from what I understand from t-dawg's questions is that he wants to emulate what you can do in gvim, but with vim instead.
In gvim, I can click the mouse button; hold; drag downwards and then gvim will start scrolling downwards, whilst highlighting the passing lines. This is how you highlight large amounts of text (greater than what can fit in a single screen at a time) with a mouse.
However, terminals are slightly dumber. Whilst you can highlight areas of text, that's a console function and not something that vim itself is monitoring. Therefore, you can't achieve the same effect with the mouse in vim as you can in gvim.
Of course, vim is perfectly capable of selecting more text than can fit in a single screen. It has a visual mode. Press v and then move down with your cursor keys, et volia - highlighted text.
Now when it comes to shifting this to X11's clipboard, I've never tried (hence the link I gave for possible help). I'm sure it can be done.

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

[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 disable vim filetype indentation.

Hello. I want to start using vim, but there is only that problem with that. In gedit I always use tabs 4 spaces wide for indentation, and I want to do something similar in vim. So in my .vimrc I used tabstop=4 and set autoindent. If I write a plain text file, it works correctly, for example, if I press tab in a new line, and the press enter, the following lines preserve the tab as indentation.
The problem starts when writing code in common lisp or python. In lisp tab is replaced by two spaces and does some weird things, and in python tab is replaced by 4 spaces. I tried including "filetype indent off" in my vimrc, or writing ":filetype indent off" directly in console, but that doesn't have any effect. The only thing that somewhat works is to disable autodinent, but then I have to manually indent every line. What can I do?
Last edited by Serge2702 (2014-11-06 20:57:54)

I keep a skeleton vimrc file to use when I have a question similar to Serge2702's. My barebones.vim:
set nocompatible
filetype plugin on
set t_co=256 " Optional, you may comment this out.
syntax on
Start vim, using the alternate vimrc file with the command, say, for a lisp file: vim -u barebones.vim file_to_edit.lisp.
Seems most filetypes default to a tab with a width of eight spaces here. To see the tabs, you can use these two commands from within vim:
:set list
:set listchars=tab:_T
Then you can try all the different setting combinations to figure out a comfortable tab width.
And there are quite a few settings that affect the width of tabs and indentation besides tabstop. There's autoindent to repeat the previous line's indentation, but this is modified if you use cindent or smartindent to set the indent according to syntax. Then there are the expandtab and smarttab settings to use spaces for tabs, and shiftwidth and softtabstop also set indentation width. I don't see why anyone has trouble figuring it out.;)

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

[solved]where is syntax.vim?

Since the update to (g)vim 7.1.68, the folder /usr/share/vim/syntax is empty, no syntax.vim.. nothing.
my .vimrc and .gvimrc are not working..
what a crap
Last edited by defcon (2007-08-15 04:06:24)

My /usr/share/vim/syntax has 498 *.vim files in it, all owned by vi 7.1.68-1 I suppose this happened with the splitting of the vi/vim/gvim packages. See http://archlinux.org/news/336/

(SOLVED)Disabling options in vim

Is it possible to disable options in vim, for example "set number" from vims command line instead of from /etc/vimrc or ~/.vimrc.
Last edited by unilx (2011-07-03 00:02:21)

I'm not sure if it will help you, but
set number
nnoremap <F2> :set nonumber!<CR>
sets the line numbers on by default and you can toggle it on/off by pressing F2.

[solved] need obscure vi/vim help

Hello,
I am running a Archlinux on a very old and dilapidated laptop. One of the problems is that the left column of buttons on the keyboard (ctrl, shift,capslock,tab,`,esc) do not work. The esc is however quite important if editing files in vi. The main problem is how to change from input mode to command mode without esc. Before the pacman update, I was able to get back to command mode by pressing the mousebutton 2 or 3 times; then the : appeared and I was able to save and quit. However, with the last pacman update, this options has disappeared; pressing the mouse two or three times does not give command mode anymore.
How do I now change from input mode to command mode without the esc key?
Last edited by anadyr (2009-10-31 21:24:03)

Control-[
Oh, I didn't even notice that you're still using vi. Vi is actually vi now, as opposed to a build of vim with fewer features.
Last edited by SamC (2009-10-31 21:10:12)

[SOLVED] syntax highlighting in vim

Hi,
How do you guys set syntax highlighting in your vimrc? For example, I have a bunch of mutt config files saved as something like alias.muttrc, colors.muttc, etc... and I want them all to use the muttrc syntax.
Currently, I have this in my vimrc:
au BufNewFile,BufRead *.muttrc setf muttrc
This works unless my first line is a comment (or first non-blank line). Which is annoying because I want to begin with a comment sometimes!
Also, I noticed that if my main config file--muttrc--is set correctly whether or not it begins with a comment. (This file is already matched to muttrc syntax without my intervention).
Does anyone have a better/different way of setting the syntax?
Last edited by miggy (2009-05-27 16:15:44)

Thanks for the suggestion but I'm experiencing the same behavior. Something weird's going on. Can someone confirm this same behavior?
file1.muttrc
color normal white default
file2.muttrc
# Comment
color normal white default
file3.muttrc
color normal white default
# Comment
As I'm writing these, they all are good, but when I go to edit them, only file1.muttrc has the correct highlighting. The others can get it if I say :set syntax=muttrc.
It's especially weird that the comments are highlighted but nothing else is. If I'm not using any sort of file detecting then not even the comments are highlighted

[Solved]switch my keyboard layout (also, how to unify clipboard?)

ok, i want to switch between us and us intl layout. After reading the Xorg page in the great Arch Wiki i maded
a file called "11-switchkb.conf" in my xorg folder and writed into it:
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "us, us intl"
Option "XkbOptions" "grp:caps_toggle"
EndSection
and i happyli restared my X and... My keyboard stopped working ( i had to brute shutdown my notebook holding power button)
I also tried 10-switchkb.conf and didnt worked. What im doing wrong?
My second question i dont know how to explain it right... Im confused about copy and paste in linux, and it's seems weird for me,
sometimes it works sometimes it doesnt...
like when i highlight something in uzbl i can paste with shift+insert but
only while its highlighted. Sometimes i highlight what i want in vim and, even while its still highlighted, when i do shift+insert
in some other app it doesnt paste anything. and when i highlight in vim and paste in the same vim whith shift+insert it pastes
with a crazy indentation, but when i yank and paste it with 'p' it pastes correctly.
Is there a way to "unify" clipboard, in such a way i can copy-paste without trouble from any app to any other app?
Last edited by wolfspaw (2010-09-13 16:03:28)

Thanks for the help guys!
Great answers, that was exactly what i wanted for my clipboard and Vim! (I'll read about buffers).
stqn : Nice script, i'll try to bind it to xMonad.
Karol: I can solve the issue with sqn script but im curious to why my X
does not detect my keyboard when i use the Xorg Arch Wiki way of
Layout Switch:
Here is my Xorg.0.log after trying the swi(the last third of it.):
(my touchpad is detected as a mouse, but it works great) :
[ 29619.012] (II) Initializing built-in extension Generic Event Extension
[ 29619.012] (II) Initializing built-in extension SHAPE
[ 29619.012] (II) Initializing built-in extension MIT-SHM
[ 29619.012] (II) Initializing built-in extension XInputExtension
[ 29619.012] (II) Initializing built-in extension XTEST
[ 29619.012] (II) Initializing built-in extension BIG-REQUESTS
[ 29619.012] (II) Initializing built-in extension SYNC
[ 29619.012] (II) Initializing built-in extension XKEYBOARD
[ 29619.012] (II) Initializing built-in extension XC-MISC
[ 29619.012] (II) Initializing built-in extension SECURITY
[ 29619.012] (II) Initializing built-in extension XINERAMA
[ 29619.012] (II) Initializing built-in extension XFIXES
[ 29619.012] (II) Initializing built-in extension RENDER
[ 29619.012] (II) Initializing built-in extension RANDR
[ 29619.012] (II) Initializing built-in extension COMPOSITE
[ 29619.012] (II) Initializing built-in extension DAMAGE
[ 29619.023] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 29619.023] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 29619.023] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 29619.023] (II) AIGLX: enabled GLX_SGI_make_current_read
[ 29619.023] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 29619.023] (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
[ 29619.023] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 29619.024] (II) intel(0): Setting screen physical size to 361 x 203
[ 29619.211] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 29619.211] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 29619.211] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 29619.211] (II) LoadModule: "evdev"
[ 29619.211] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 29619.212] (II) Module evdev: vendor="X.Org Foundation"
[ 29619.212] compiled for 1.8.1.902, module version = 2.4.0
[ 29619.212] Module class: X.Org XInput Driver
[ 29619.212] ABI class: X.Org XInput driver, version 9.0
[ 29619.212] (**) Power Button: always reports core events
[ 29619.212] (**) Power Button: Device: "/dev/input/event5"
[ 29619.220] (II) Power Button: Found keys
[ 29619.220] (II) Power Button: Configuring as keyboard
[ 29619.220] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 29619.220] (**) Option "xkb_rules" "evdev"
[ 29619.220] (**) Option "xkb_model" "evdev"
[ 29619.220] (**) Option "xkb_layout" "us, us intl"
[ 29619.220] (**) Option "xkb_options" "grp:caps_toggle"
[ 29619.259] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
[ 29619.259] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 29619.259] (**) Video Bus: Applying InputClass "Keyboard Defaults"
[ 29619.259] (**) Video Bus: always reports core events
[ 29619.259] (**) Video Bus: Device: "/dev/input/event8"
[ 29619.267] (II) Video Bus: Found keys
[ 29619.267] (II) Video Bus: Configuring as keyboard
[ 29619.267] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 29619.267] (**) Option "xkb_rules" "evdev"
[ 29619.267] (**) Option "xkb_model" "evdev"
[ 29619.267] (**) Option "xkb_layout" "us, us intl"
[ 29619.267] (**) Option "xkb_options" "grp:caps_toggle"
[ 29619.271] (II) config/udev: Adding input device Lid Switch (/dev/input/event4)
[ 29619.271] (II) No input driver/identifier specified (ignoring)
[ 29619.271] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 29619.271] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 29619.271] (**) Sleep Button: Applying InputClass "Keyboard Defaults"
[ 29619.271] (**) Sleep Button: always reports core events
[ 29619.271] (**) Sleep Button: Device: "/dev/input/event3"
[ 29619.280] (II) Sleep Button: Found keys
[ 29619.280] (II) Sleep Button: Configuring as keyboard
[ 29619.280] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 29619.280] (**) Option "xkb_rules" "evdev"
[ 29619.280] (**) Option "xkb_model" "evdev"
[ 29619.280] (**) Option "xkb_layout" "us, us intl"
[ 29619.280] (**) Option "xkb_options" "grp:caps_toggle"
[ 29619.283] (II) config/udev: Adding input device USB2.0 0.3M UVC WebCam (/dev/input/event7)
[ 29619.283] (**) USB2.0 0.3M UVC WebCam: Applying InputClass "evdev keyboard catchall"
[ 29619.283] (**) USB2.0 0.3M UVC WebCam: Applying InputClass "Keyboard Defaults"
[ 29619.283] (**) USB2.0 0.3M UVC WebCam: always reports core events
[ 29619.283] (**) USB2.0 0.3M UVC WebCam: Device: "/dev/input/event7"
[ 29619.290] (II) USB2.0 0.3M UVC WebCam: Found keys
[ 29619.290] (II) USB2.0 0.3M UVC WebCam: Configuring as keyboard
[ 29619.290] (II) XINPUT: Adding extended input device "USB2.0 0.3M UVC WebCam" (type: KEYBOARD)
[ 29619.290] (**) Option "xkb_rules" "evdev"
[ 29619.290] (**) Option "xkb_model" "evdev"
[ 29619.290] (**) Option "xkb_layout" "us, us intl"
[ 29619.290] (**) Option "xkb_options" "grp:caps_toggle"
[ 29619.296] (II) config/udev: Adding input device Asus Laptop extra buttons (/dev/input/event6)
[ 29619.296] (**) Asus Laptop extra buttons: Applying InputClass "evdev keyboard catchall"
[ 29619.296] (**) Asus Laptop extra buttons: Applying InputClass "Keyboard Defaults"
[ 29619.296] (**) Asus Laptop extra buttons: always reports core events
[ 29619.296] (**) Asus Laptop extra buttons: Device: "/dev/input/event6"
[ 29619.310] (II) Asus Laptop extra buttons: Found keys
[ 29619.310] (II) Asus Laptop extra buttons: Configuring as keyboard
[ 29619.310] (II) XINPUT: Adding extended input device "Asus Laptop extra buttons" (type: KEYBOARD)
[ 29619.310] (**) Option "xkb_rules" "evdev"
[ 29619.310] (**) Option "xkb_model" "evdev"
[ 29619.310] (**) Option "xkb_layout" "us, us intl"
[ 29619.310] (**) Option "xkb_options" "grp:caps_toggle"
[ 29619.311] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 29619.311] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 29619.311] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
[ 29619.311] (**) AT Translated Set 2 keyboard: always reports core events
[ 29619.311] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 29619.323] (II) AT Translated Set 2 keyboard: Found keys
[ 29619.324] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 29619.324] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 29619.324] (**) Option "xkb_rules" "evdev"
[ 29619.324] (**) Option "xkb_model" "evdev"
[ 29619.324] (**) Option "xkb_layout" "us, us intl"
[ 29619.324] (**) Option "xkb_options" "grp:caps_toggle"
[ 29619.324] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event2)
[ 29619.324] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[ 29619.324] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[ 29619.324] (II) LoadModule: "synaptics"
[ 29619.325] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 29619.325] (II) Module synaptics: vendor="X.Org Foundation"
[ 29619.325] compiled for 1.8.0.902, module version = 1.2.2
[ 29619.325] Module class: X.Org XInput Driver
[ 29619.325] ABI class: X.Org XInput driver, version 9.0
[ 29619.325] (II) Synaptics touchpad driver version 1.2.2
[ 29619.325] (**) Option "Device" "/dev/input/event2"
[ 29619.363] (II) ETPS/2 Elantech Touchpad: x-axis range 8 - 1144
[ 29619.364] (II) ETPS/2 Elantech Touchpad: y-axis range 8 - 760
[ 29619.364] (II) ETPS/2 Elantech Touchpad: device does not report pressure, will use touch data.
[ 29619.364] (II) ETPS/2 Elantech Touchpad: finger width range 0 - 0
[ 29619.364] (II) ETPS/2 Elantech Touchpad: buttons: left right double triple
[ 29619.364] (**) Option "TapButton1" "1"
[ 29619.364] (**) Option "TapButton2" "2"
[ 29619.364] (**) Option "TapButton3" "3"
[ 29619.390] (--) ETPS/2 Elantech Touchpad: touchpad found
[ 29619.390] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 29619.403] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD)
[ 29619.404] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[ 29619.404] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 0
[ 29619.404] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[ 29619.404] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[ 29619.430] (--) ETPS/2 Elantech Touchpad: touchpad found
[ 29619.431] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse0)
[ 29619.431] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[ 29619.431] (II) Synaptics touchpad driver version 1.2.2
[ 29619.837] ETPS/2 Elantech Touchpad no synaptics event device found
[ 29619.837] (**) Option "Device" "/dev/input/mouse0"
[ 29619.850] (**) Option "TapButton1" "1"
[ 29619.850] (**) Option "TapButton2" "2"
[ 29619.850] (**) Option "TapButton3" "3"
[ 29619.871] Query no Synaptics: 6003C8
[ 29619.871] (--) ETPS/2 Elantech Touchpad: no supported touchpad found
[ 29619.871] (EE) ETPS/2 Elantech Touchpad Unable to query/initialize Synaptics hardware.
[ 29619.910] (EE) PreInit failed for input device "ETPS/2 Elantech Touchpad"
[ 29619.910] (II) UnloadModule: "synaptics"
[ 29619.911] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
[ 29619.911] (II) No input driver/identifier specified (ignoring)
[ 29672.057] (II) Power Button: Close
[ 29672.057] (II) UnloadModule: "evdev"
[ 29672.077] (II) Video Bus: Close
[ 29672.077] (II) UnloadModule: "evdev"
[ 29672.097] (II) Sleep Button: Close
[ 29672.097] (II) UnloadModule: "evdev"
[ 29672.117] (II) USB2.0 0.3M UVC WebCam: Close
[ 29672.117] (II) UnloadModule: "evdev"
[ 29672.137] (II) Asus Laptop extra buttons: Close
[ 29672.137] (II) UnloadModule: "evdev"
[ 29672.157] (II) AT Translated Set 2 keyboard: Close
[ 29672.157] (II) UnloadModule: "evdev"
[ 29672.190] (II) UnloadModule: "synaptics"

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

[vim] has('x11') has('clipboard') over ssh, pb copy/cut in vim

Hello
I experiment some problem with vim on my server.
On my laptop and my server I have vim 7.2.266-1
:echo has('x11') && has('clipboard')
It return 1 on my laptop (x86_64) (gnome-terminal) but on the server (i686) (over ssh with gnome-terminal) it return 0.
:-S
I don't understand ...
I would like to know what cause this behaviour and maybe how to enable x11 and clipboard in vim on my server...
Could you help me please

X11 and clipboard are run locally. I do not know of a nice way to do what you want. I agree, reaching for the mouse when selecting/paste text is cumbersome.

Native -- DataFlavor clipboard problem

I'm trying to access vim specific clipboard data (to get visual block info). This is on windows XP (unix is next) I've registered the formats with addFlavorForUnencodedNative, see java code below. But when I look at all the clipboard flavors, when clipboard contains vim stuff, no vim flavors show up, see output.
Any ideas of what/where the problem might be?
Thanks,
-ernie
In vim, from its os_win32.c, there is
    clip_star.format = RegisterClipboardFormat("VimClipboard2");
    clip_star.format_raw = RegisterClipboardFormat("VimRawBytes");and when a vim copy to clipboard command is issued, in vim's os_mswin.c. Note that cbd->format is clip_start.format, returned from RegisterClipboardFormat above.
SetClipboardData(cbd->format, hMemVim);
SetClipboardData(CF_UNICODETEXT, hMemW) != NULL)
SetClipboardData(CF_TEXT, hMem);When I run the java program I get the following output. First are the mimetype of the 3 native flavors I added; in cb.getAvailableDataFlavors() none of them appear in the 27 flavors available.
VimClipboard application/vimclipboard; class=java.nio.ByteBuffer
VimClipboard2 application/vimclipboard2; class=java.nio.ByteBuffer
VimRawBytes application/vimrawbytes; class=java.nio.ByteBuffer
27 flavors
application/x-java-text-encoding; class="[B"
application/x-java-serialized-object; class=java.lang.String
...Here's the java code that is not finding the vim clipboard native data
/* Main.java; access vim's clipboard */
package vimclipapp;
import java.awt.Toolkit;
import java.awt.datatransfer.Clipboard;
import java.awt.datatransfer.DataFlavor;
import java.awt.datatransfer.FlavorMap;
import java.awt.datatransfer.SystemFlavorMap;
public class Main {
    static DataFlavor VimClipboard = addFlavor("VimClipboard");
    static DataFlavor VimClipboard2 = addFlavor("VimClipboard2");
    static DataFlavor VimRawBytes = addFlavor("VimRawBytes");
    static DataFlavor addFlavor(String cbName) {
        DataFlavor df = null;
        FlavorMap fm = SystemFlavorMap.getDefaultFlavorMap();
        SystemFlavorMap sfm = (SystemFlavorMap) fm;
        try {
            df = new DataFlavor( "application/"
                                + cbName
                                + "; class=java.nio.ByteBuffer");
        } catch (ClassNotFoundException ex) { ex.printStackTrace(); }
        System.err.println(cbName + " " + df.getMimeType());
        sfm.addFlavorForUnencodedNative(cbName, df);
        sfm.addUnencodedNativeForFlavor(df, cbName);
        return df;
    public static void main(String[] args) {
        Clipboard cb = Toolkit.getDefaultToolkit().getSystemClipboard();
        if(cb.isDataFlavorAvailable(VimClipboard2))
            System.err.println("VimClipboard available");
        DataFlavor dfa[] = cb.getAvailableDataFlavors();
        System.err.println("\n" + dfa.length + " flavors\n");
        for (DataFlavor df : dfa) {
            System.err.println(df.getMimeType());
}

Are you using Gmail?
Try deleting the email profile, tap battery, tap restart, go into email and reinstall the profile.

[SOLVED] X clipboard in vim + xclip

Similar Messages

Maybe you are looking for