Re: [kde] Setting KP_Home as a separate key from Home.
Dotan Cohen posted on Thu, 20 Oct 2011 14:48:36 +0200 as excerpted: > I would like to set the numpad keys as macros and media keys when > NumLock is disabled. For instance, I would like 7, 8, and 9 to be > VolumeDown, VolumeUp, and Mute respectively. In System Settings -> > Shortcuts and Gestures -> Global Keyboard Shortcuts -> Kmix I disable > NumLock and press the 7 key on the keypad, but KDE complains that "Home" > is used in many applications and thus cannot be set. I use Home very > often: Home in the IHPU/DEPD block (above the arrow keys), but never on > the non-NumLock keypad. They each send unique keycodes (110 for Home and > 79 for KP_Home), so why can they not be set independently? It's an interesting coincidence that you posted this today, as it was only last nite that I had the following update here on Gentoo, which looks to me to be potentially relevant. 14 Oct 2011; Chí-Thanh Christopher Nguyễn -xkeyboard-config-2.4.1.ebuild, +xkeyboard-config-2.4.1-r1.ebuild, +files/xkeyboard-config-2.4.1-extended-function-keys.patch: Add upstream patch to unbreak extended function keys, bug #386561. The -r1 indicates a gentoo revision of an upstream version, so they've apparently not released a fixed version upstream yet. (The patch deals with more than function keys tho, with a bunch of KP_* changes too.) The referenced bug is here: https://bugs.gentoo.org/show_bug.cgi?id=386561 The patch is unfortunately not posted to the bug, but here's the info included from git in the patch itself: From 1d1338afa6aa555c5f6c83d07fceec43a4d87f0d Mon Sep 17 00:00:00 2001 From: Sergey V. Udaltsov Date: Wed, 05 Oct 2011 21:26:26 + Subject: Levels 2-4 for CTRL+ALT are propagated from level 1 Googling that commit ID results in this, which looks right: http://www.google.com/search?q=1d1338afa6aa555c5f6c83d07fceec43a4d87f0d The upstream commit on github appears as the first hit ATM, with a couple archlinux bugs listed as well. (There's a few more if you hit the link for them, all arch-linux for whatever reason; maybe because they're about the only ones that update that fast, other than gentoo, which probably has the google crawler blocked on its bugzilla for performance reasons.) It's the October 5 entry on the github link, but that builds on version 2.4.1, released Oct. 4. You may be best simply grabbing the git HEAD tarball from github and building it yourself. Of course on most distros that'll mean resolving the dependencies manually. Of course, that may not be your problem at all, at least not if you're on a distro shipping an older < 2.4 version of that package. But looking at the actual patch, it sure looks like it could be related, whether it actually is or not. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] VIM mode in Kate: why not use native VIM?
It would; last thing we need to do is unneedingly re-invent the wheel. On Thu, Oct 20, 2011 at 12:41 PM, Dotan Cohen wrote: > I love VIM and use the Kate VIM mode. This mode _emulates_ VIM rather > than incorporating native VIM. I now see that it is in fact possible > to incorporate native VIM: > http://vimdoc.sourceforge.net/htmldoc/netbeans.html > > Might it be wise to move to this approach rather than trying to copy > VIM in Kate? > > -- > Dotan Cohen > > http://gibberish.co.il > http://what-is-what.com > ___ > This message is from the kde mailing list. > Account management: https://mail.kde.org/mailman/listinfo/kde. > Archives: http://lists.kde.org/. > More info: http://www.kde.org/faq.html. > -- Jacky Alcine http://www.jackyalcine.co.cc ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] VIM mode in Kate: why not use native VIM?
I love VIM and use the Kate VIM mode. This mode _emulates_ VIM rather than incorporating native VIM. I now see that it is in fact possible to incorporate native VIM: http://vimdoc.sourceforge.net/htmldoc/netbeans.html Might it be wise to move to this approach rather than trying to copy VIM in Kate? -- Dotan Cohen http://gibberish.co.il http://what-is-what.com ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Setting KP_Home as a separate key from Home.
I would like to set the numpad keys as macros and media keys when NumLock is disabled. For instance, I would like 7, 8, and 9 to be VolumeDown, VolumeUp, and Mute respectively. In System Settings -> Shortcuts and Gestures -> Global Keyboard Shortcuts -> Kmix I disable NumLock and press the 7 key on the keypad, but KDE complains that "Home" is used in many applications and thus cannot be set. I use Home very often: Home in the IHPU/DEPD block (above the arrow keys), but never on the non-NumLock keypad. They each send unique keycodes (110 for Home and 79 for KP_Home), so why can they not be set independently? Thanks! -- Dotan Cohen http://gibberish.co.il http://what-is-what.com ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] SensorLogger in ksysguard NOW is writing on disk file [SOLVED]
Dear Duncan,
thank you for your detailed answer, fortunately the maintainer
of the ksysguard app has answered to me after my help request, and invited me
to modify the software to fix the bug, and so I did and fortunately I
succeeded!
Down here you can read about the modifications I made, that I've sent to the
maintainer yet, hoping this will help to have a fixed version in the
dstribution as soon as possible.
Now I'm using the version modified by me for the use I needed, and
I can have logfiles for the sensor of my lab data center.
> Therefore, I'd suggest filing a bug with kde on it, if one's not already
> filed.
yes, I submitted the bug report to this thread
https://bugs.kde.org/show_bug.cgi?id=223094
> As I said, I don't know what resources you're trying to log, but if it's
> something to do with hardware sensors, memory usage, cpu usage, disk
> activity/space, or network usage, I have had a bit of experience figuring
> out how to harvest that sort of information at the command line,
I'm the person in charge of some systems in a data centre, performing
satellite data elaboration h24, as main things I have to monitor that
operational servers are up, with enough disk space and with nominal CPU, RAM
usage and temperature, hopefully from a remote station, then having the
results directly on logfile is helping me to retrieve this infos from remote
computers.
In a wider point of view, it could be useful for me to read every kind of
sensor connected to and readable by a computer, because I'm working in a
scientific lab, so I accept your help and I would ask you some infos about
sensor logging with other tools in the future, if needed.
> As it happens, I used to use ksysguard in kde3, but when I switched to
> kde4 in the 4.2/4.3 era, not only was there no ksysguard plasmoid to
> replace the kicker applet that I relied on in kde3, but ksysguard itself,
> like much of kde4 at the time (despite what the kde PR said and despite
> the dropping of support for the latest reasonably workable version, then
> kde 3.5.10, even after promising support as long as there were users,
> guess a lot of current and former kde users know how much to trust kde
> claims now, about as far as they can launch a now decommissioned NASA
> shuttle!) was rather buggy, failing to properly save and restore its own
> configuration, among other problems.
Yes I agree that there are still *some* problems to have all working correctly
passing from kde3 to kde4 ... but I hope this will go better in the future and
I'll try to do something to participate in the improvement of kde.
Long life to KDE!
Thank you again for your help.
Francesco.
>Oggetto: SensorLogger in ksysguard NOW is writing on disk file [SOLVED]
>Data: giovedì 13 ottobre 2011, 23:00:17
>Da: Francesco Lazzarotto
>A: John Tapsell
>CC: kde-de...@kde.org
>Hi John, I modified the code in order to make ksysguard write (again) the logs
>on a file. I used the package kdebase-workspace_4.6.5.orig.tar, compiled
>with CMake.
>What I have changed is:
>1) I implemented the method
> virtual void timerEvent ( QTimerEvent * event );
>in the class LogSensor, in this way
>void LogSensor::timerEvent ( QTimerEvent * event )
>{
> timerTick();
>}
>to call the timerTick() method every time the timerEvent() is called, caused
>by the behavior of the QObject superclass.
>2) in the source file SensorLogger.cpp I modified the constructor of the
>SensorLogger Class this way:
>SensorLogger::SensorLogger( QWidget *parent, const QString& title,
>SharedSettings *workSheetSettings )
> : KSGRD::SensorDisplay( parent, title, workSheetSettings )
>{
>...
>...
> // mView->setContextMenuPolicy( Qt::CustomContextMenu );
> mView->setContextMenuPolicy( Qt::DefaultContextMenu );
>giving as argument Qt::DefaultContextMenu instead of Qt::CustomContextMenu
>after this, right clicking on the sensorlogger line was possible again to
>select the option "Start Logging" and make ksysguard start to write in the
>selected logfile.
>at the link
>http://www.fileden.com/files/2009/2/22/2333221/ksysguard_modified_by_lazzarotto.tar.gz
>you can access the source directory with my modifications, please check if it
>works fine also in your computer (if you can).
>Now I can use ksysguard to set up some automatic control on my
>servers/systems
>and to plot/analyse logged data with external programs, just as I did to plot
>the attached image "laptop_temperature.jpg" created using the temperature
>sensor of my laptop, read and logged by ksysguard.
>I'm going to use this version for my applications, tell me if I can do
>something more for the maintaining of this app.
>bye
>Francesco.
>In data martedì 11 ottobre 2011 14:48:56, John Tapsell ha scritto:
> Good to hear!
>
> If you have ubuntu, the fastest way to get developing is to do something
> like:
>
> sudo apt-get install project-neon-utils project-neon-kdelibs
>
> git clone kde:kde-workspace.git
>
> neon-env
>
> cd kde-workspace
>
> neonma
