Sent a proposal to improve the situation for GTK+ wannabe-maintainers. Didn’t get much feedback, but we’ll probably meet again this thursday from 18:00 UTC+2 at #gtk-love/irc.gimp.org. Would be specially interested in getting volunteers to get the “GTK+ hackers guide” started 🙂 (A brief summary of my proposal is: 1) Gather a GTK+ love bug list with easy bugs for beginners. Something like this but hopefully using bugzilla and with the maintainers support. 2) Create a short guide with the most basic concepts a GTK+ hacker should understand thoroughly explained. Hopefully it’d be mostly a matter of collecting, updating and expanding the already available and scattered docs).
Ranted with fellow Nokian and emacs user Dirk Jan (there’s no need to panic, it’s only dutch) about how nice would it be to get the devhelp functionality from within emacs. Well, this morning he sent me this, which I’m already loving. It’s only missing search to be completely perfect 🙂 (Tempted to get my hands dirty with elisp and just do it).
PS: the title is the canonical answer a waiter from Brussels will give you if you ask for a “big coke”.
Isn’t that snippet enough (its in /etc/emacs/site-start.d/ on feisty)
; Emacs integration by Richard Hult
(defun devhelp-word-at-point ()
“runs devhelp”
(interactive)
(start-process-shell-command “devhelp” nil “devhelp” “-s” (current-word))
)
; Example: bind F7 to start devhelp and search for the word at the point.
(global-set-key [f7] ‘devhelp-word-at-point)
; Tips: use -g WIDTHxHEIGHT+XOFF+YOFF to set the size and position of
; the window
I probably wasn’t clear enough: the point is to get the devhelp functionality without using devhelp 🙂
Everything is so much better when you can use the emacs keybindings … (and devhelp could be *way* faster)