From: David Reitter <david.reitter@gmail.com>
Subject: Re: help with a bug in/using advice and/or documentation strings
Date: Wed, 14 Jun 2006 14:46:24 +0100 [thread overview]
Message-ID: <4994CC68-16C1-4331-AC0D-EB2513715F55@gmail.com> (raw)
In-Reply-To: <184CA3BF-B4E5-4265-BEB4-410E01B6175F@gmail.com>
I can add to my earlier e-mail that this...
On 13 Jun 2006, at 20:11, David Reitter wrote:
>
> I don't know if it's got to do with it, but I am extending some
> variable documentation strings at one point like this:
>
> (put symbol 'variable-documentation
> (concat
> old-doc
> (format " ... ") )
... doesn't seem to influence the infinite recursion that people are
getting in `ad-Orig-documentation'.
prev parent reply other threads:[~2006-06-14 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAAEB4AB-13E3-4F5B-AABF-5673521C2AA4@bellarmine.edu>
2006-06-13 19:11 ` help with a bug in/using advice and/or documentation strings David Reitter
2006-06-14 13:46 ` David Reitter [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
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=4994CC68-16C1-4331-AC0D-EB2513715F55@gmail.com \
--to=david.reitter@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.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).