From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: good examples of Emacs modules? Date: Thu, 31 Mar 2016 19:53:44 +0300 Message-ID: <83a8levbaf.fsf@gnu.org> References: <56FC5E99.7090804@cs.ucla.edu> <8737r67jbo.fsf@wanadoo.es> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1459443260 5354 80.91.229.3 (31 Mar 2016 16:54:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 31 Mar 2016 16:54:20 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 31 18:54:14 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1alfrJ-0004Lw-LI for ged-emacs-devel@m.gmane.org; Thu, 31 Mar 2016 18:54:13 +0200 Original-Received: from localhost ([::1]:33424 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alfrJ-0000WR-8L for ged-emacs-devel@m.gmane.org; Thu, 31 Mar 2016 12:54:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35474) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alfr5-0000WL-SC for emacs-devel@gnu.org; Thu, 31 Mar 2016 12:54:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1alfr1-0006Si-SY for emacs-devel@gnu.org; Thu, 31 Mar 2016 12:53:59 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38357) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alfr1-0006SQ-Ol; Thu, 31 Mar 2016 12:53:55 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1875 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1alfr1-0007xl-1R; Thu, 31 Mar 2016 12:53:55 -0400 In-reply-to: <8737r67jbo.fsf@wanadoo.es> (message from =?utf-8?Q?=C3=93sca?= =?utf-8?Q?r?= Fuentes on Thu, 31 Mar 2016 17:34:03 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:202512 Archived-At: > From: Óscar Fuentes > Date: Thu, 31 Mar 2016 17:34:03 +0200 > > > Everything else is documented in the emacs-module.h header. > > The documentation on that file is scant, to say it lightly. We need high > level descriptions of the APIs, with examples, if possible. Then, a > chapter on techniques and recommended strategies for creating and using > modules that reflect common C API designs. Whithout that, the real job > is not creating a module for libfoo, but figuring out how emacs modules > are supposed to work. You can also look in modules/mod-test/, if you haven't already.