Search Results

Search found 2 results on 1 pages for 'unclezeiv'.

Page 1/1 | 1 

• Cannot assign keys to Wacom scroll wheel anymore

  - by UncleZeiv

  Hi all, my Wacom Graphire 4 used to work perfectly well until, I think, Ubuntu 10.4. At that point something changed in the configuration and I couldn't assign a key to the scroll wheel anymore (note: the pad's scroll wheel, not the mouse's), i.e this command: xsetwacom set "Wacom Graphire4 6x8 pad" AbsWDn "key +" returns silently without error but nothing happens. Same goes for AbsWUp, RelWDn, RelWUp. Apparently though the problem is even deeper as pressing the wheel in a xev window doesn't seem to have any effect. Moreover I am thoroughly confused on how the various pieces (kernel driver, xorg driver, evdev, HAL, xinput?) are supposed to work together and if the wacom module that ships with Ubuntu is the one from linuxwacom or not. Any ideas? I don't want to become an X.org hacker just to understand what's going on... it used to work! NOTE: I have already read question 3940, but that's not the same problem.

  Read the article

• Vim: How to handle newlines when storing multiple commands in registers?

  - by UncleZeiv

  I have a file where I store snippets of vim commands. When I need a snippet, I yank it and then execute it with @". The snippets are stored as a script, one line per command, like this: :s/foo/bar/g :echo "hello" :s/1/2/g Edit: I removed normal mode commands from the example, as they were not part of the problem. Now this procedure doesn't work anymore: when executing the snippet, it just stops at the first line as if waiting for a newline. Is there an option somewhere affecting how @ is executed? I'm pretty sure it was working some time ago... Substituting the newline with a ^M character works but makes the file more difficult to handle. Additional information: Here's another symptom: when I yank a snippet, if I execute it with @" it stops at the first line as I just explained. But if I execute it with :@ it works. But the help file doesn't seem to imply any difference in how the two commands treat the register's content...

  Read the article

1