From: Nick Dokos <nicholas.dokos@hp.com>
To: Henri-Paul Indiogine <hindiogine@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Problems with search
Date: Thu, 07 Jul 2011 23:45:59 -0400 [thread overview]
Message-ID: <7746.1310096759@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Henri-Paul Indiogine <hindiogine@gmail.com> of "Thu, 07 Jul 2011 20:14:25 PDT." <CAG_r7O7dw2Kk--7dS8viAob1qpL6EHvPah4KoUJ1EYNF2LOxbg@mail.gmail.com>
Henri-Paul Indiogine <hindiogine@gmail.com> wrote:
> Hi Nick!
>
> 2011/7/7 Nick Dokos <nicholas.dokos@hp.com>:
> >> post-command-hook is a variable defined in `C source code'.
> >> Its value is
> >> (t autopair-post-command-handler)
> >>
> >
> > This looks wrong: what's that t doing there? and where did it come from?
>
> I think it is from autopair.el
>
> (add-hook 'post-command-hook 'autopair-post-command-handler
> 'append 'local))
>
> I have had this autopair function for quite a while, well before the
> search problem occurred. Also, if do not load autopair I still have
> the search problem.
>
No, it's not the autopair-post-command-handler that I wondered about[fn:1],
it's that *t*, the first element of the list: how did it get there?
Nick
Footnotes:
[fn:1] Well, I did wonder about it, but only because I never heard of
it; but I am more suspicious of that t.
next prev parent reply other threads:[~2011-07-08 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 20:58 Problems with search Henri-Paul Indiogine
2011-07-07 21:16 ` Nick Dokos
2011-07-07 22:16 ` Henri-Paul Indiogine
2011-07-07 23:18 ` Henri-Paul Indiogine
2011-07-08 2:25 ` Nick Dokos
2011-07-08 3:14 ` Henri-Paul Indiogine
2011-07-08 3:45 ` Nick Dokos [this message]
[not found] <CAPeR955y2+HF8wip7RB0g+pKUj6T0VqXPRGszTPv0NP4ExtDTg@mail.gmail.com>
2011-08-02 18:27 ` Bianca Lutz
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7746.1310096759@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=hindiogine@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).