unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Xavier Maillard <xma@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Readings for an emacs package maintainer ?
Date: Mon, 1 Jun 2009 11:13:28 +0200	[thread overview]
Message-ID: <e01d8a50906010213n5788ab19l398549df69a10280@mail.gmail.com> (raw)
In-Reply-To: <87k53wh16c.wl%xma@gnu.org>

Maybe look in the packages Drew develpe and maintain?


On Mon, Jun 1, 2009 at 9:18 AM, Xavier Maillard <xma@gnu.org> wrote:
> Hi,
>
> I am looking for a good documentation on best practices for an
> emacs package maintainer.
>
> I want packages I am maintaining to be still supported for old
> emacsen from, say, 19.x to latest possible (including xemacs).
>
> Currently, the big problems for me is to keep on using old
> functions or have a common rule to define my macros.
>
> What do you, emacs developers, do in order to have the larger
> backward compatibility spectrum ?
>
> I was thinking about a package-compat.el but I do not know how
> well it will work with macros defined here at compile time.
>
> Regards,
>
> Xavier
>
>
>




  reply	other threads:[~2009-06-01  9:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  7:18 Readings for an emacs package maintainer ? Xavier Maillard
2009-06-01  9:13 ` Lennart Borgman [this message]
2009-06-01 16:14   ` Drew Adams
2009-06-01 18:56     ` Reiner Steib
2009-06-01 19:04       ` Lennart Borgman
2009-06-01 19:11       ` Drew Adams
2009-06-01 12:43 ` Xavier MAILLARD
2009-06-01 14:15   ` Miles Bader
2009-06-02  2:17     ` Stephen J. Turnbull
2009-06-02  2:36       ` Miles Bader
2009-06-02 12:02       ` Deniz Dogan
2009-06-02 14:07         ` Stephen J. Turnbull
2009-06-01 16:15   ` Drew Adams
2009-06-01 16:21 ` Bastien
2009-06-01 17:05   ` Drew Adams
2009-06-01 20:35 ` Stefan Monnier
2009-06-01 22:01   ` Leo

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=e01d8a50906010213n5788ab19l398549df69a10280@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=xma@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).