From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Function definition wrong
Date: 13 Feb 2000 14:22:34 +0100 [thread overview]
Message-ID: <vafbt5lme3p.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Pieter Wenk's message of "Sun, 13 Feb 2000 11:36:09 +0100"
Pieter Wenk <pwenk@urbanet.ch> writes:
> Kai when doing M-x find-function RET
> sc-header-author-writes RET
>
> I am getting "no match"
Hm. Did you M-x load-library RET supercite RET? Alternatively, just
have a look at the SuperCite *.el files and you'll find the right
function.
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-02-13 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-11 16:25 Pieter Wenk
2000-02-11 17:28 ` Kai Großjohann
2000-02-12 7:28 ` Pieter Wenk
2000-02-12 12:41 ` Kai Großjohann
2000-02-12 16:10 ` Pieter Wenk
2000-02-13 1:16 ` Kai Großjohann
2000-02-13 10:36 ` Pieter Wenk
2000-02-13 13:22 ` Kai Großjohann [this message]
2000-02-14 14:29 ` Pieter Wenk
2000-02-14 15:18 ` Kai Großjohann
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=vafbt5lme3p.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).