From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Rocky Bernstein" Newsgroups: gmane.emacs.devel Subject: Re: removing bushdb related code in gud.el Date: Sun, 25 Feb 2007 16:37:24 -0500 Message-ID: <6cd6de210702251337x39a0b0c3g4a781810de111e6@mail.gmail.com> References: <20070226.024211.256833758.jet@gyve.org> <17889.63761.72895.326368@kahikatea.snap.net.nz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1711548787==" X-Trace: sea.gmane.org 1172462846 9698 80.91.229.12 (26 Feb 2007 04:07:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 26 Feb 2007 04:07:26 +0000 (UTC) Cc: Masatake YAMATO , bashdb-devel@lists.sourceforge.net, emacs-devel@gnu.org To: "Nick Roberts" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 26 05:07:19 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HLX8w-0005Cd-OU for ged-emacs-devel@m.gmane.org; Mon, 26 Feb 2007 05:07:19 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HLX8w-0003ja-L0 for ged-emacs-devel@m.gmane.org; Sun, 25 Feb 2007 23:07:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HLR3g-0002YW-6V for emacs-devel@gnu.org; Sun, 25 Feb 2007 16:37:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HLR3e-0002YK-LW for emacs-devel@gnu.org; Sun, 25 Feb 2007 16:37:26 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HLR3e-0002YH-G2 for emacs-devel@gnu.org; Sun, 25 Feb 2007 16:37:26 -0500 Original-Received: from nf-out-0910.google.com ([64.233.182.190]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HLR3d-0007Nd-RU for emacs-devel@gnu.org; Sun, 25 Feb 2007 16:37:26 -0500 Original-Received: by nf-out-0910.google.com with SMTP id h2so1508559nfe for ; Sun, 25 Feb 2007 13:37:24 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=qgI4NJItg59sk+luUJ1c4iRLHxWcmvs/FpRNQ0TOvd93l2UUBkuPHtewUcJ01ZBcedW2g3uOTTxnYIllWlxqcNMlKnbQMsOs+mrLerOmoy5dCu3Mwg8W14x2FWO24rnu/c3FWU7zBWkLoV6PwnXTEXx44vcD1UI5xj7wNMDQ8sk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=lR/UCjgLjsGPm8bDw9G9SlMq37UEEp2p8HWYfWxrJgQwcDDhH89PzCb4S//0W8ZzAe+R30J0ibO5jtl+vuHKJub50Izu+0rwCyaAUMNeMqdtJVBCA5gaY7aaKcVX80hhPDfyUR9dSreU/sANPJ7CIFkz/If6ciN88tttHFS6U2U= Original-Received: by 10.82.154.2 with SMTP id b2mr1434628bue.1172439444280; Sun, 25 Feb 2007 13:37:24 -0800 (PST) Original-Received: by 10.82.152.4 with HTTP; Sun, 25 Feb 2007 13:37:24 -0800 (PST) In-Reply-To: <17889.63761.72895.326368@kahikatea.snap.net.nz> X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) X-Mailman-Approved-At: Sun, 25 Feb 2007 23:07:04 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:66821 Archived-At: --===============1711548787== Content-Type: multipart/alternative; boundary="----=_Part_59345_10725804.1172439444128" ------=_Part_59345_10725804.1172439444128 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 2/25/07, Nick Roberts wrote: > > > We(Rocky, the author of bashdb and I, a contributor) would like to > > remove bashdb related code in gud.el. > > You would need to remove references in the manual too. Yes, I guess so. It would be nice though to mention that support for the debugger can be found elsewhere. > Bashdb has been improved/changed its output. > > As the result we have to update bashdb related code in gud.el; the > > version of bashdb and bashdb related code in gud.el must be > > synced. This is not problem during emacs development stage. > > I'm quite happy to work on such task. > > > > However, once new version of emacs is released. The code > > synchronization task is out of my hand; even if I update the code in > > Savannah's repository, users may use released version of emacs and > > gud.el bundled to it. > > > > To avoid users' confusion, we'd like to move bashdb related code( > bashdb.el) > > in gud.el to bashdb itself. So we can provide well updated bashdb.el in > > bashdb release. > > > > Any objection? > > I guess if bashdb.el is always distributed with bash, It is -- but that's a separate problem which we are also working on. I think you meant to say if "bashdb.el is always distributed with bashdb ". and users know how to > put it in their load-path, then this makes sense. Debian based-distributions already seem to have a convention and mechanism for making sure it is in the load path (I think). New releases of Emacs might > break functionality but they will surely be less frequent than releases of > Bash. Yes, when bashdb.el is distributed outside of GNU Emacs, it means that it must cope with multiple versions and variants of Emacs. We've discussed this previously, and we feel that it still the better this way. Working for us here is the fact that there is a longer time between GNU Emacs releases than bashdb releases. By the way, in bashdb.el we've started adding testing via elk-test.el. What is there is not very extensive , but at least it's a start. If someone is interested in extending to more of what's in gud.el, by all means take a look at the code in the bashdb sources. Thanks. ------=_Part_59345_10725804.1172439444128 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 2/25/07, Nick Roberts <nickrob@snap.net.nz> wrote:
> We(Rocky, the author of bashdb and I, a contributor) would like to
> remove bashdb related code in gud.el.

You would need to remove references in the manual too.

Yes, I guess so. It would be nice though  to mention that support for the debugger can be found elsewhere.

> Bashdb has been improved/changed its output.
> As the result we have to update bashdb related code in gud.el; the
> version of bashdb and bashdb related code in gud.el must be
> synced. This is not problem during emacs development stage.
> I'm quite happy to work on such task.
>
> However, once new version of emacs is released. The code
> synchronization task is out of my hand; even if I update the code in
> Savannah's repository, users may use released version of emacs and
> gud.el bundled to it.
>
> To avoid users' confusion, we'd like to move bashdb related code( bashdb.el)
>  in gud.el to bashdb itself. So we can provide well updated bashdb.el in
> bashdb release.
>
> Any objection?

I guess if bashdb.el is always distributed with bash,


It is -- but that's a separate problem which we are also working on.  I think you meant to say if "bashdb.el is always distributed with bashdb ".
 

and users know how to
put it in their load-path, then this makes sense. 

Debian based-distributions  already seem to have a convention and mechanism for making sure it is in the load path (I think).

 New releases of Emacs might
break functionality but they will surely be less frequent than releases of
Bash.

Yes, when bashdb.el is distributed outside of GNU Emacs, it means that it must cope with multiple versions and variants of Emacs. We've discussed this previously, and we feel that it still the better this way. Working for us here is the fact that there is a longer time between GNU Emacs releases than bashdb releases.
 
By the way, in bashdb.el we've started adding testing via elk-test.el. What is there is not very extensive , but at least it's a start.  If someone is interested in extending to more of what's in gud.el , by all means take a look at the code in the bashdb sources.

Thanks.
------=_Part_59345_10725804.1172439444128-- --===============1711548787== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --===============1711548787==--