Ian Wienand: Sending arbitrary keys through xtightvnc
Although it's not particularly clear, a neat feature of xtightvnc
is the ability to modify the pop-up menu that appears when you press
F8 to send arbitrary keystrokes.
The trick is overriding some of the X11 resources of the file. If
you have a look in /etc/X11/app-defaults/Vncviewer (make sure
you have a recent
package) you can see the default keybindings for the popup menu,
which are a good template. Assuming you want to keep them all, you
can add your own buttons by starting at button 9 and re-defining the
total button count in your ~/.Xresources:
Make sure you merge this with xrdb -merge ~/.Xresources if
you don't want to bother logging out and in. This way I can easily
send Alt-F1, etc. through to the other side; useful for things like
switching virtual terminals in VMware workstation running remotely. I
imagine if you were insane you could do all sorts of other tricks
too!
xtightvncviewer*popupButtonCount: 11
xtightvncviewer*popup*button9.label: Alt-F1
xtightvncviewer*popup*button9.translations: #override\n\
<Btn1Down>,<Btn1Up>: \
SendRFBEvent(keydown,Alt_L) \
SendRFBEvent(keydown,F1) \
SendRFBEvent(keyup, F1) \
SendRFBEvent(keyup, Alt_L)
xtightvncviewer*popup*button10.label: Alt-F2
xtightvncviewer*popup*button10.translations: #override\n\
<Btn1Down>,<Btn1Up>: \
SendRFBEvent(keydown,Alt_L) \
SendRFBEvent(keydown,F2) \
SendRFBEvent(keyup, F2) \
SendRFBEvent(keyup, Alt_L)
xtightvncviewer*popup*button11.label: Alt-F12
xtightvncviewer*popup*button11.translations: #override\n\
<Btn1Down>,<Btn1Up>: \
SendRFBEvent(keydown,Alt_L) \
SendRFBEvent(keydown,F12) \


<comment />
Recently I have mostly been "behind". I've caught up a little on what I wanted to do though over the past couple of days, so I won't feel too bad.
I've:
My last laptop had a serial port, but only when it was inserted into its bulking docking station. My laptop of the past 2.5 years doesn't have one. I used to spend a lot of time in datacenters wanting to configure devices over a serial console, so as a result I've been using USB to serial converters for some time. And I've never really been that happy with them.
Some of you may have noticed that I was mostly unavailable those last weeks. I was finishing writing my PhD report. It is now submitted, so I have more free time again.
I am currently processing the backlog. If you are waiting for an action from my side, you should get some news in the next few days.
Since development kernels 2.6.26-rc*, the iwlwifi drivers (iwl3945, iwl4965)
have LED support. While LED support is nice to have (making it easy to see when
the wireless connection is available), the blinking of the LED whenever there
is data transmitted is annoying.In most networks, there is a constant chatter on the net. Windows server
browsing and announcing, Zeroconf/Bonjour announcements, Printer discovery.
When you're using some instant messaging or chat such as IRC there is some
data transmitted all the time. Your email program might be polling for new
emails, and your weather applet might be fecthing the latest forecasts.
So basically, there always is ome network traffic. Often in the range of less
than 1k/s, but there is.The new iwlwifi drivers don't flicker the LED with each packet received, but
apparently will just set the LED to a blink mode when they received or
transmitted some data, which if find rather irritating.Fortunately, this can easily be configured in Linux, just save this script
in /etc/network/if-up.d/iwl-no-blink and make it executable:
At the time of writing,
I've not seen an announcement (again), but
there's
Andrew Pollock
Today was a good day — at least if I average all the things
happened today. And since
I thought I'd throw the
I must admit that the "no complicated configuration file" was an advantage for most users of 