unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Eli Zaretskii" <eliz@gnu.org>,
	"João Távora" <joaotavora@gmail.com>,
	"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Prefixed manual describe-function and api overview
Date: Thu, 4 Jun 2020 16:06:22 +0200	[thread overview]
Message-ID: <CAGK7Mr5fPF1XaR56kz+AJuOakaoRQmCG3y0jMrL+M4faaFDpFg@mail.gmail.com> (raw)
In-Reply-To: <jwvbllzxc3k.fsf-monnier+emacs@gnu.org>

> > - In `prefixed-manual-overview`, I'd like to display the full
> > signature of functions. For example display "(substring-no-properties
> > STRING &optional FROM TO)" instead of "substring-no-properties". If
> > you know a simple way I'm interested. I tried to use something like
> > `(get 'substring-no-properties 'function-documentation)` or play with
> > `documentation-property` but couldn't find easily and gave up.
>
> I think you're looking for `help-function-arglist`, but of course that
> only works for those functions already loaded into Emacs.

Thanks. I was beginning to think about having to use
`describe-function`, extract the signature from it, then close the
buffer :-)

I'll incorporate your idea soon and try to make it look pretty, maybe
by generating org-mode blocks instead.

Philippe



  reply	other threads:[~2020-06-04 14:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  9:39 Prefixed manual describe-function and api overview Philippe Vaucher
2020-06-04 12:16 ` Stefan Monnier
2020-06-04 14:06   ` Philippe Vaucher [this message]
     [not found] ` <E1jh2ly-000090-Hp@fencepost.gnu.org>
2020-06-05  7:55   ` Philippe Vaucher
2020-06-06  3:59     ` Richard Stallman
2020-06-07 12:10       ` Philippe Vaucher
2020-06-08  3:35         ` Richard Stallman
     [not found] ` <CAGK7Mr4_2zus2Hq9=ArpR-ya6FNxxqXWvDxLGTsHsH4-XuM=CQ@mail.gmail.com>
2020-06-11 19:13   ` João Távora
2020-06-12 14:18     ` Philippe Vaucher
2020-06-12 16:02       ` João Távora
2020-06-13  9:23         ` Philippe Vaucher
2020-06-13 13:41           ` João Távora
2020-06-13 15:46             ` Philippe Vaucher
2020-06-13 16:41               ` Dmitry Gutov

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=CAGK7Mr5fPF1XaR56kz+AJuOakaoRQmCG3y0jMrL+M4faaFDpFg@mail.gmail.com \
    --to=philippe.vaucher@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).