unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Matthew Leach <matthew@mattleach.net>
To: emacs-devel@gnu.org
Subject: Best practice for sharing new Emacs modules
Date: Mon, 11 Jan 2016 19:43:56 +0000	[thread overview]
Message-ID: <87bn8rkikj.fsf@mattleach.net> (raw)

Hi all,

I've begun work on a new mode for Emacs that allows editing of gpg keys
in a dired-like fashion -- something I said I was going to do a long
time ago!  I'm making good progress and am hoping to post to the list
very soon for feedback.

I do have one question: what is the best/accepted way to share the code
with the Emacs community?  I've looked around at the Emacs source tree
for advice, but all I could find was notes about posting patches for the
Emacs source tree itself, rather than a new module.  Would a simple
email to the list with the code attached suffice or would I be better
hosting the code on my github and providing a link to it on this list?
Do people even care?

Apologies for a (probably) pointless question, it's my first time
writing a new Emacs module and I'm trying to avoid the dreaded
development faux pas.
-- 
Matt



             reply	other threads:[~2016-01-11 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 19:43 Matthew Leach [this message]
2016-01-11 20:23 ` Best practice for sharing new Emacs modules Clément Pit--Claudel
2016-01-11 21:22 ` Artur Malabarba
2016-01-11 21:43   ` Drew Adams
2016-01-11 22:33     ` Clément Pit--Claudel
2016-01-12  0:25 ` John Wiegley
2016-01-12  4:36 ` Stefan Monnier

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=87bn8rkikj.fsf@mattleach.net \
    --to=matthew@mattleach.net \
    --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).