From: oitofelix@gmail.com (Bruno Félix Rezende Ribeiro)
To: rgm@gnu.org, 10384@debbugs.gnu.org
Subject: bug#10384: [Bruno Félix Rezende Ribeiro] Re: bug#10384: 23.2; Emacs Lisp Reference Manual - incorrect or unclear documentation about invocation condition of hooks pre-command-hook and post-command-hook
Date: Mon, 16 Jan 2012 07:21:35 -0200 [thread overview]
Message-ID: <878vl82eao.fsf@felix-laptop.gnung> (raw)
In-Reply-To: <87y5txhcmi.fsf@felix-laptop.gnung>
[-- Attachment #1: Type: message/rfc822, Size: 1550 bytes --]
From: oitofelix@gmail.com (Bruno Félix Rezende Ribeiro)
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: Re: bug#10384: 23.2; Emacs Lisp Reference Manual - incorrect or unclear documentation about invocation condition of hooks pre-command-hook and post-command-hook
Date: Sun, 15 Jan 2012 16:45:24 -0200
Message-ID: <87wr8sst2z.fsf@felix-laptop.gnung>
All these suggestions looks great. Any of these would help avoid that
nonsense thought described in the bug report and I think it don't will
generate any further problem with the definition and inter-description
relation, taking in account yours considerations.
Thanks.
--
Bruno Félix Rezende Ribeiro (oitofelix)
Uns o chamam de super-vaca...
Outros de hyper-touro...
Eu o chamo simplesmente: meta-gnu!
!A ilha não se curva!
[-- Attachment #2: Type: text/plain, Size: 172 bytes --]
--
Bruno Félix Rezende Ribeiro (oitofelix)
Uns o chamam de super-vaca...
Outros de hyper-touro...
Eu o chamo simplesmente: meta-gnu!
!A ilha não se curva!
prev parent reply other threads:[~2012-01-16 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 22:29 bug#10384: 23.2; Emacs Lisp Reference Manual - incorrect or unclear documentation about invocation condition of hooks pre-command-hook and post-command-hook Bruno Félix Rezende Ribeiro
2012-01-11 20:40 ` Glenn Morris
2012-01-11 22:40 ` Glenn Morris
2012-01-12 1:24 ` Stefan Monnier
2012-01-27 8:36 ` Chong Yidong
2012-01-16 9:21 ` Bruno Félix Rezende Ribeiro [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vl82eao.fsf@felix-laptop.gnung \
--to=oitofelix@gmail.com \
--cc=10384@debbugs.gnu.org \
--cc=rgm@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.