unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: execute defun on reception of signal
Date: Mon, 13 Jul 2015 09:13:24 -0700 (PDT)	[thread overview]
Message-ID: <553331e3-369f-4ccd-a9ed-e58a04edf869@googlegroups.com> (raw)
In-Reply-To: <mailman.6858.1436801328.904.help-gnu-emacs@gnu.org>

On Monday, July 13, 2015 at 8:58:50 PM UTC+5:30, Eli Zaretskii wrote:
> > Date: Mon, 13 Jul 2015 07:57:04 -0700 (PDT)
> > From: Rusi 
> > 
> > ie I started with google (which was not useful) and didnt really try info.
> 
> Then we will get back to you when the FSF has completed taking over
> Google, and we can influence its search capabilities.
> 
> > There was this claim "letrec is nice" or some such.
> > Since I know letrec from scheme etc but never seen in elisp I was curious.
> > I find:
> >  describe-function tells nothing about the recursion
> >  the elisp info pages (index) seems to not have it at all
> 
> Please submit a documentation bug report, if you think the
> documentation is incomplete.

Done


  parent reply	other threads:[~2015-07-13 16:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12  1:59 execute defun on reception of signal Emanuel Berg
2015-07-12 10:27 ` Andy Moreton
2015-07-12 16:56   ` Emanuel Berg
2015-07-12 18:54     ` Andy Moreton
2015-07-13  3:53       ` Vaidheeswaran C
2015-07-14  1:49         ` Emanuel Berg
     [not found]     ` <mailman.6808.1436727285.904.help-gnu-emacs@gnu.org>
2015-07-13  2:29       ` Rusi
2015-07-13  2:57         ` Emanuel Berg
2015-07-13  3:39           ` Vaidheeswaran C
2015-07-14  1:43             ` Emanuel Berg
2015-07-14  1:58               ` Vaidheeswaran C
2015-07-14  1:59                 ` Emanuel Berg
2015-07-14  2:07                   ` Emanuel Berg
2015-07-14  2:09                   ` Vaidheeswaran C
2015-07-14 22:14                     ` Emanuel Berg
2015-07-13  8:28         ` Andy Moreton
2015-07-13 14:49           ` Nicolas Richard
2015-07-13 15:22             ` Eli Zaretskii
2015-07-13 14:44         ` Eli Zaretskii
     [not found]         ` <mailman.6850.1436798656.904.help-gnu-emacs@gnu.org>
2015-07-13 14:57           ` Rusi
2015-07-13 15:18             ` Thierry Volpiatto
2015-07-13 15:28             ` Eli Zaretskii
     [not found]             ` <mailman.6858.1436801328.904.help-gnu-emacs@gnu.org>
2015-07-13 16:13               ` Rusi [this message]
2015-07-14  1:53             ` Emanuel Berg
     [not found]             ` <mailman.6892.1436840915.904.help-gnu-emacs@gnu.org>
2015-07-14  2:41               ` Pascal J. Bourguignon
2015-07-14 21:33                 ` Emanuel Berg
     [not found]                 ` <mailman.6932.1436909731.904.help-gnu-emacs@gnu.org>
2015-07-14 22:11                   ` Pascal J. Bourguignon
2015-07-14 22:21                     ` Emanuel Berg
     [not found]                     ` <mailman.6936.1436912565.904.help-gnu-emacs@gnu.org>
2015-07-15 15:25                       ` Rusi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=553331e3-369f-4ccd-a9ed-e58a04edf869@googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).