From: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: Tips to suppress compilation warnings
Date: Thu, 26 May 2005 18:08:16 -0700 [thread overview]
Message-ID: <31588.1117156096@olgas.newt.com> (raw)
In-Reply-To: Stefan Monnier's message of Thu, 26 May 2005 13:08:47 EDT. <87k6llrk4m.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > However, if Info-goto-node is a useful thing to use from outside Info,
> > perhaps it should be defined as autoloaded in info.el rather than in mh-e.
>
> No. Elisp packages that want to invoke info this way should use the `info'
> function, which can be called just the same: (info "(mh-e)Draft Editing").
Stefan,
Thanks very much. Replacing Info-goto-node with info did the trick!
I used this information to solve the following in a similar fashion:
mh-seq.el:1719:1:Warning: the function `view-mode' might not be defined at
runtime.
RFTM revealed that we should be using view-mode-enter instead.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next prev parent reply other threads:[~2005-05-27 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87psve50hh.fsf@olgas.newt.com>
2005-05-26 14:54 ` Tips to suppress compilation warnings Richard Stallman
2005-05-26 17:08 ` Stefan Monnier
2005-05-27 1:08 ` Bill Wohler [this message]
2005-05-27 4:46 ` Jay Belanger
2005-05-27 9:57 ` Juri Linkov
2005-05-25 23:50 Bill Wohler
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=31588.1117156096@olgas.newt.com \
--to=wohler@newt.com \
--cc=mh-e-devel@lists.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.