all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: bojohan+news@dd.chalmers.se, emacs-devel@gnu.org
Subject: Re: Patch: make eldoc indicate current argument
Date: Mon, 16 Jul 2007 23:34:46 -0400	[thread overview]
Message-ID: <E1IAdpm-0001Z6-4K@fencepost.gnu.org> (raw)
In-Reply-To: <200707160223.25223.pogonyshev@gmx.net> (message from Paul Pogonyshev on Mon, 16 Jul 2007 02:23:24 +0300)

    I was aware of such things (optional parameters in brackets), but
    didn't figure out what to do with them:

	;; FIXME: What to do with optional arguments, like in
	;;        (defun NAME ARGLIST [DOCSTRING] BODY...) case?
	;;        The problem is there is no robust way to determine if
	;;        the current argument is indeed a docstring.

Doc strings are so important that eldoc may as well have special-case
code for them.

  reply	other threads:[~2007-07-17  3:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 17:04 Patch: make eldoc indicate current argument Tom Tromey
2007-06-27 23:42 ` Richard Stallman
2007-06-28  4:48   ` Tom Tromey
2007-07-13  5:25   ` Kevin Rodgers
2007-07-13  7:15     ` David Kastrup
2007-07-13 23:09       ` Richard Stallman
2007-07-14 11:11         ` Juanma Barranquero
2007-07-14 16:17           ` David Kastrup
2007-07-14 22:33             ` Richard Stallman
2007-07-15  8:20               ` Juanma Barranquero
2007-07-15 22:54                 ` Richard Stallman
2007-07-15  9:27             ` Johan Bockgård
2007-07-15 22:54               ` Richard Stallman
2007-07-15 23:23               ` Paul Pogonyshev
2007-07-17  3:34                 ` Richard Stallman [this message]
2007-07-17  4:36                   ` Stefan Monnier
2007-07-18  4:42                     ` Richard Stallman
2007-06-28 20:35 ` Tom Tromey

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=E1IAdpm-0001Z6-4K@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bojohan+news@dd.chalmers.se \
    --cc=emacs-devel@gnu.org \
    --cc=pogonyshev@gmx.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.