From: "Juanma Barranquero" <lekktu@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Call to eldoc-get-fnsym-args-string with 1 argument
Date: Tue, 17 Jul 2007 12:12:06 +0200 [thread overview]
Message-ID: <f7ccd24b0707170312x67ab482evf6f60600b06a8b65@mail.gmail.com> (raw)
After
2007-07-12 Paul Pogonyshev <pogonyshev@gmx.net>
* emacs-lisp/eldoc.el [...]
(eldoc-get-fnsym-args-string): Add `args' argument. Use new
`eldoc-highlight-function-argument'.
compiling eshell/esh-cmd.el produces this message:
In eshell-exec-lisp:
esh-cmd.el:1340:31:Warning: eldoc-get-fnsym-args-string called with 1
argument, but requires 2
Juanma
next reply other threads:[~2007-07-17 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 10:12 Juanma Barranquero [this message]
2007-08-03 1:01 ` Call to eldoc-get-fnsym-args-string with 1 argument Glenn Morris
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=f7ccd24b0707170312x67ab482evf6f60600b06a8b65@mail.gmail.com \
--to=lekktu@gmail.com \
--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 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).