unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Manheimer <ken.manheimer@gmail.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: multishell
Date: Mon, 4 Jan 2016 12:07:34 -0500	[thread overview]
Message-ID: <CAAT_zTHDcg6msPhmcp9VdkFUQMUAuTLwZPnBUKo-hEm6c3ityg@mail.gmail.com> (raw)
In-Reply-To: <87a8om1kas.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]

On Sun, Jan 3, 2016 at 3:26 PM, Artur Malabarba <bruce.connor.am@gmail.com>
wrote:

> Ken Manheimer <ken.manheimer@gmail.com> writes:
>
> > I'm about to push a multishell as a new packge in the git.sv.gnu.org:
>
> Thank you!
>

My pleasure!

> One coding wrinkle worth mentioning - I prefixed most of my package's
> > functions with "multishell:"
>
> Please change it to “multishell-”. It will work nicer with the customize
> interface.
>
> > did not prefix the primary function, "pop-to-shell". I see that as
> > the package's exported api. I do not feel strongly bound to this
> > choice, and can be persuaded to also prefix it if someone feels there
> > is good reason to do so.
>
> The current convention is to use multishell-pop-to-shell. This includes
> user stuff (like commands and customization variables) as well as
> programatic stuff that you consider “official api” (like functions that
> other packages can call, or vars that can be configured but aren't
> defcustoms).
>
> In order to differentiate the functions and vars that are NOT
> “exported”, use a double-dash (e.g. `multishell--bracket-asterisks').
> (This is a relatively new convention, which is why a lot of places don't
> use it).
>

Ok - I've done all this, but also changed my version number to 0, in order
to defer release.

This deferral is not due to any of these changes, but rather because I
discovered a change I want to make to the way I organize how remote shells
are expressed, and I need to shake the change out before it's ready. I
don't want anyone to get used to the old syntax, hence the release deferral.

It's been helpful, though, to shake out the release format with your and
other's help - thanks for that! I hope it's not inopportune for me to defer
the actual release after getting the code situated (and I welcome further
suggestions for making multishell a good ELPA citizen).

Ken

[-- Attachment #2: Type: text/html, Size: 2926 bytes --]

  reply	other threads:[~2016-01-04 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 22:19 [ELPA] New package: multishell Ken Manheimer
2016-01-03 20:26 ` Artur Malabarba
2016-01-04 17:07   ` Ken Manheimer [this message]
2016-01-04 18:27     ` Artur Malabarba
2016-01-04 18:49       ` Ken Manheimer
2016-01-04 20:29         ` Ken Manheimer
2016-01-05  3:23           ` Artur Malabarba
2016-01-05  3:42             ` Michael Heerdegen

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=CAAT_zTHDcg6msPhmcp9VdkFUQMUAuTLwZPnBUKo-hEm6c3ityg@mail.gmail.com \
    --to=ken.manheimer@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --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).