* manual-entry and devhelp
@ 2008-08-01 13:21 Richard G Riley
0 siblings, 0 replies; only message in thread
From: Richard G Riley @ 2008-08-01 13:21 UTC (permalink / raw)
To: help-gnu-emacs
I have the following snippet in my c-programming elisp file:
,----
| (let ((dl '(
| ([f1] . devhelp-word-at-point)
| ([(shift f1)] . manual-entry)
| ; ([backtab] . semantic-complete-analyze-inline)
| ;; ([f5] . find-tag-noconfirm)
| ([f6] . find-tag-repeat)
| ([f7] . pop-tag-mark)
| ([f2] . gdb-restore-windows)
| ([f3] . cscope-find-global-definition-no-prompting)
| ([f4] . repeat)
| ([f10] . (lambda()(interactive)(do-compile)))
| ([(shift f10)] . (lambda()(interactive)(do-lint)))
| ([(control f10)] . (lambda()(interactive)(do-cdecl)))
| ([f11] . next-error)
| ([f12] . gdb))))
| (dolist (i dl)
|
| (define-key c-mode-base-map (car i) (cdr i))
| ;; (define-key c-mode-map (car i) (cdr i))
| ;; (define-key c++-mode-map (car i) (cdr i))
| ))
`----
With regards to F1 and S-F1 above, I was hoping some kind elisp
programmer could help with a function which will pull up the
manual-entry if it exists and then, if not, call up
devhelp-word-at-point? The glib devhelp is a bit of a mess and not a
patch on the man pages. Unfortunately the docs for stuff like GTK+ do
not exist as manpages so one use use devhelp (the GTK+ docs in devhelp
are in a nice state however).
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-08-01 13:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-01 13:21 manual-entry and devhelp Richard G Riley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).