all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Better help support for EIEIO classes and methods
Date: Sun, 03 Feb 2013 22:28:41 -0500	[thread overview]
Message-ID: <jwv8v744v8v.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <877gmpz9mt.fsf@engster.org> (David Engster's message of "Sun, 03 Feb 2013 16:42:50 +0100")

> In Emacs proper, if you use describe-function on an EIEIO class
> constructor like `auth-source-backend', you will get
> auth-source-backend is a Lisp function.  as the first line, which is
> not very helpful.  If you know that this is actually a class
> constructor, you can at least call eieio-describe-class or
> eieio-describe-constructor, which will give you a much more detailed
> description, but is still missing one essential feature: a link to the
> filename where this class is defined, which quickly brings you to the
> correct class definition.  This is even more important for methods,
> which can have several implementations depending on the class they're
> called on.

To a large extent the first line is not that important since you can add
the missing info in the docstring itself.  Could you give more details of
the things that can't be overcome this way?


        Stefan



  reply	other threads:[~2013-02-04  3:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03 15:42 Better help support for EIEIO classes and methods David Engster
2013-02-04  3:28 ` Stefan Monnier [this message]
2013-02-04 18:47   ` David Engster
2013-02-04 19:53     ` Stefan Monnier
2013-02-05 21:23       ` David Engster
2013-02-06 14:45         ` Stefan Monnier
2013-02-06 16:19           ` David Engster
2013-02-06 19:16             ` Stefan Monnier
2013-02-10 15:21               ` David Engster
2013-02-11  3:57                 ` Stefan Monnier

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=jwv8v744v8v.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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.