From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: execute defun on reception of signal Date: Mon, 13 Jul 2015 04:57:35 +0200 Message-ID: <87a8v0bw80.fsf@nl106-137-147.student.uu.se> References: <871tgedtkv.fsf@nl106-137-147.student.uu.se> <86r3odvfg3.fsf@gmail.com> <871tgd9uwi.fsf@nl106-137-147.student.uu.se> <7d1d1e2c-1b1d-490a-a20e-1a06c84e2c87@googlegroups.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1436756374 23380 80.91.229.3 (13 Jul 2015 02:59:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Jul 2015 02:59:34 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jul 13 04:59:24 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZETxj-0006q1-Vz for geh-help-gnu-emacs@m.gmane.org; Mon, 13 Jul 2015 04:59:24 +0200 Original-Received: from localhost ([::1]:52613 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZETxj-0006Hm-IF for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Jul 2015 22:59:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45004) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZETxZ-0006Hg-35 for help-gnu-emacs@gnu.org; Sun, 12 Jul 2015 22:59:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZETxU-0004sC-Vi for help-gnu-emacs@gnu.org; Sun, 12 Jul 2015 22:59:12 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:55134) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZETxU-0004s7-Oj for help-gnu-emacs@gnu.org; Sun, 12 Jul 2015 22:59:08 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZETxQ-0006ff-6u for help-gnu-emacs@gnu.org; Mon, 13 Jul 2015 04:59:04 +0200 Original-Received: from nl106-137-156.student.uu.se ([130.243.137.156]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Jul 2015 04:59:04 +0200 Original-Received: from embe8573 by nl106-137-156.student.uu.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Jul 2015 04:59:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Original-Lines: 60 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: nl106-137-156.student.uu.se Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:6lvUVUfm5ejQhbB7ccXmpDHyKpI= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:105670 Archived-At: Rusi writes: > I generally find google usually gives a more pointed > answer quicker than manually searching the docs. > This may well be some kind of exception.... Try my 'cid' tool - it searches the RFCs, the man pages, and the jargon file - and ranks results neatly :) You only need the material organized in a certain way - my way, but I don't think it is too unorthodox. "CID" - common interface to documentation, and the airship mechanic in the Final Fantasy games. Pretty clever, ey? http://user.it.uu.se/~embe8573/conf/.zsh/cid I didn't add support for the info files but those are what I remember in some text/markup format which should work exactly like the man pages' groff for this purpose, or the jargon's plain text for that matter. It is all an orchestra of strings - doing unbelievable things! The reason Google is not good is it is changing, both the search results and what is searchable (actually "findable"). You want your documentation static (save for bugfixes) so you know what you expect and learn how to navigate it. With bookmarks, each time you find what you look for, something to this end can be achieved with a browser and Google, but not really - you'd have to save the webpages each time to really get it. Also, on-disk documentation is less distracting and more to the point. You can access it with the familiar shell tools (find, grep, sort, etc.). Obviously, you do not rely on the Internet if you only access the files on your computer. Sometimes, Google is good tho, especially for error messages which for whatever reason are seldom found in the "on-line" documentation (i.e., not on paper - remember "Sierra On-Line"?). Google speaks like you do - "how do I...", "why..." - which the RFCs etc. certainly don't. Anyway, here is the solution to the original problem, as described in (info "(elisp) Misc Events"), line 79: (defun sigusr-handler () (interactive) (message "Caught signal %S" last-input-event)) (define-key special-event-map [sigusr1] 'sigusr-handler) (signal-process (emacs-pid) 'sigusr1) -- underground experts united http://user.it.uu.se/~embe8573