From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ken Manheimer Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: multishell Date: Mon, 4 Jan 2016 12:07:34 -0500 Message-ID: References: <87a8om1kas.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113d59b064f38c0528852927 X-Trace: ger.gmane.org 1451927286 2666 80.91.229.3 (4 Jan 2016 17:08:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jan 2016 17:08:06 +0000 (UTC) Cc: "emacs-devel@gnu.org" To: Artur Malabarba Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 18:08:05 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 1aG8c0-0005FE-9a for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 18:08:04 +0100 Original-Received: from localhost ([::1]:46398 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG8bz-0000zZ-Bp for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 12:08:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58303) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG8bt-0000zJ-1Q for emacs-devel@gnu.org; Mon, 04 Jan 2016 12:08:01 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aG8br-0002zb-Qx for emacs-devel@gnu.org; Mon, 04 Jan 2016 12:07:56 -0500 Original-Received: from mail-oi0-x236.google.com ([2607:f8b0:4003:c06::236]:33549) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG8br-0002zF-LJ for emacs-devel@gnu.org; Mon, 04 Jan 2016 12:07:55 -0500 Original-Received: by mail-oi0-x236.google.com with SMTP id y66so258916189oig.0 for ; Mon, 04 Jan 2016 09:07:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=MAKInGvMjuwPtdNpsq3BmzI/1/S6c6d2jTCkVk2Ts48=; b=rF5ttLrBGEmCt/oGMcjnIGUYwMqV6+AgIqUtw+NhbHbqWT8X5W+tqeOMhJtZoyNfJt fw0NvoGMigsP2Q3xtBHswBPz7OM5Ve5igI0YtQZ1jBoegvHd8oQV3C69y6Hsetm/c6Uu EPjyBpWqVB87wKsSrFlS6q/IQWuHLQePWnFz3FP94pbZS5EZQ97iVJao+TB8g2rggIw9 a79+nkxD0iwoJtAXdln6M2MVAgJCsJREktluanxg/Z8I+pxA4bcnGC1O6KiaxHU8x7kp BJ7ntfscJo0/Zk87hJnbq/6VX6sJpD4XiTXGKWUWJXmkUtruI6AsmyyOOFVta23VVTKU wYYA== X-Received: by 10.202.216.212 with SMTP id p203mr58737512oig.77.1451927273794; Mon, 04 Jan 2016 09:07:53 -0800 (PST) Original-Received: by 10.202.187.6 with HTTP; Mon, 4 Jan 2016 09:07:34 -0800 (PST) In-Reply-To: <87a8om1kas.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c06::236 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:197614 Archived-At: --001a113d59b064f38c0528852927 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, Jan 3, 2016 at 3:26 PM, Artur Malabarba wrote: > Ken Manheimer 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 =E2=80=9Cmultishell-=E2=80=9D. It will work nicer wit= h 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 =E2=80=9Cofficial api=E2=80=9D (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 > =E2=80=9Cexported=E2=80=9D, 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 --001a113d59b064f38c0528852927 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sun, Jan 3, 2016 at 3:26 PM, Artur Malabarba <bruce.connor.am@gmail.com> wrote:
Ken Manheimer <ken.manh= eimer@gmail.com> writes:

> I'm about to push a multishell as a new packge in the=C2=A0git.sv.gnu.= org:

Thank you!

My pleasure!=C2=A0

> One = coding wrinkle worth mentioning - I prefixed most of my package's
> functions with "multishell:"

Please change it to =E2=80=9Cmultishell-=E2=80=9D. It will work nice= r with the customize
interface.

> did not prefix the primary function, "pop-to-shell". I see t= hat 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<= br> > is good reason to do so.

The current convention is to use multishell-pop-to-shell. This inclu= des
user stuff (like commands and customization variables) as well as
programatic stuff that you consider =E2=80=9Cofficial api=E2=80=9D (like fu= nctions 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
=E2=80=9Cexported=E2=80=9D, use a double-dash (e.g. `multishell--bracket-as= terisks').
(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 releas= e.

Thi= s deferral is not due to any of these changes, but rather because I discove= red a change I want to make to the way I organize how remote shells are exp= ressed, 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 de= fer the actual release after getting the code situated (and I welcome furth= er suggestions for making multishell a good ELPA citizen).

Ken
--001a113d59b064f38c0528852927--