all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: npostavs@users.sourceforge.net, Marcin Borkowski <mbork@mbork.pl>
Cc: 22462@debbugs.gnu.org
Subject: bug#22462: 25.0.50; Docstring of cl-defun/defmacro are too short
Date: Tue, 05 Jul 2016 23:06:40 +0000	[thread overview]
Message-ID: <CAAdUY-JY9KFm2pOe6su4htJfqp0sGRTNxTkw3rsBDMxBfgL26Q@mail.gmail.com> (raw)
In-Reply-To: <87a8i0hel5.fsf@users.sourceforge.net>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Looks fine to me!

On Sat, Jul 2, 2016 at 1:02 AM <npostavs@users.sourceforge.net> wrote:

> tags 22462 patch
> quit
>
> Marcin Borkowski <mbork@mbork.pl> writes:
>
> > On 2016-01-25, at 09:43, Artur Malabarba <bruce.connor.am@gmail.com>
> wrote:
> >
> >> Every time I turn to cl-defun or cl-defmacro (usually for the extra
> >> arglist versatility), I end up asking myself “was it &key or &keys?” or
> >> “what was the name of that really long option?”.
> >>
> >> Naturally, I turn to `C-h f cl-defun', only to be told that it works
> >> “Like normal ‘defun’, except ARGLIST allows full Common Lisp
> >> conventions”. That's not very helpful for someone who's not profficient
> >> in Common Lisp.
> >>
> >> I think there should be a link to the relevant info node and,
> preferably,
> >> a brief summary of the conventions.
> >
> > +1.  And I'd vote for a summary, not a link.
>
> Here's a patch adding both a terse summary and a link, does it look ok?
>
>

[-- Attachment #2: Type: text/html, Size: 1531 bytes --]

  reply	other threads:[~2016-07-05 23:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  8:43 bug#22462: 25.0.50; Docstring of cl-defun/defmacro are too short Artur Malabarba
2016-01-25 11:04 ` Marcin Borkowski
2016-01-25 14:23   ` Drew Adams
2016-07-02  4:02   ` npostavs
2016-07-05 23:06     ` Artur Malabarba [this message]
2016-07-09 15:01       ` npostavs
2016-01-25 15:58 ` Eli Zaretskii

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=CAAdUY-JY9KFm2pOe6su4htJfqp0sGRTNxTkw3rsBDMxBfgL26Q@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=22462@debbugs.gnu.org \
    --cc=mbork@mbork.pl \
    --cc=npostavs@users.sourceforge.net \
    /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.