all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Wrong "Not documented" message, bug?
Date: Fri, 15 Oct 2010 13:50:34 +0200	[thread overview]
Message-ID: <4CB8400A.8070308@easy-emacs.de> (raw)
In-Reply-To: <AANLkTins3E=6ZUPREJnD0V+8vZ_FbFW0e54R=Coe9RcW@mail.gmail.com>

Am 14.10.2010 18:03, schrieb PJ Weisberg:
> On Thu, Oct 14, 2010 at 8:21 AM, Andreas Röhler
> <andreas.roehler@easy-emacs.de>  wrote:
>>
>> Hi,
>>
>> M-x describe-function `py-in-string/comment' points me to the code below,
>> which is correct:
>>
>>
>> (defun py-in-string/comment ()
>>   (interactive)
>>   "Returns character address of start of comment or string; nil if not in
>> one. "
>>   (lexical-let ((erg (nth 8 (syntax-ppss))))
>>     (unless erg (when (or (looking-at "\"\"\"")
>>                           (looking-at (concat "^[ \t]*" comment-start-skip)))
>>                   (setq erg (point))))
>>     (when (interactive-p) (message "%s" erg))
>>     erg))
>>
>> However, it says:
>>
>> ,----
>> | py-in-string/comment is an interactive Lisp function in
>> | `python-components-intern.el'.
>> |
>> | (py-in-string/comment)
>> |
>> | Not documented.
>> `----
>>
>> Something odd with doku here? A bug?
>
> The docstring has to be the *first* statement in the function.  Not
> even the (interactive) call can come before it.
>
>

Oh yeah, thanks all.






  reply	other threads:[~2010-10-15 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  8:21 Wrong "Not documented" message, bug? Andreas Röhler
2010-10-14 13:08 ` Ralf Mattes
2010-10-14 16:03 ` PJ Weisberg
2010-10-15 11:50   ` Andreas Röhler [this message]
     [not found] <mailman.1.1287045328.32083.help-gnu-emacs@gnu.org>
2010-10-14  8:59 ` Marc Mientki

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=4CB8400A.8070308@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --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.
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.