From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Peter Milliken Newsgroups: gmane.emacs.bugs Subject: split-string bug in CVS tip of Emacs Date: Tue, 14 Sep 2004 10:09:42 +1000 Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: <274A369893F5FB4099345F006439D9870316C3DB@bella.corp.resmed.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1095120614 25529 80.91.229.6 (14 Sep 2004 00:10:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Sep 2004 00:10:14 +0000 (UTC) Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Sep 14 02:10:05 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1C70tZ-0006zD-00 for ; Tue, 14 Sep 2004 02:10:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C70z7-0006jB-GD for geb-bug-gnu-emacs@m.gmane.org; Mon, 13 Sep 2004 20:15:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C70z6-0006j3-8T for bug-gnu-emacs@gnu.org; Mon, 13 Sep 2004 20:15:48 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C70z4-0006id-Cu for bug-gnu-emacs@gnu.org; Mon, 13 Sep 2004 20:15:47 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C70z4-0006ia-9Q for bug-gnu-emacs@gnu.org; Mon, 13 Sep 2004 20:15:46 -0400 Original-Received: from [203.15.64.16] (helo=ghostgum.corp.resmed.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C70tR-00028t-E5 for bug-gnu-emacs@gnu.org; Mon, 13 Sep 2004 20:09:58 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Original-Received: from falcon.corp.resmed.org ([172.16.2.141]) by ghostgum.corp.resmed.org with Microsoft SMTPSVC(5.0.2195.6713); Tue, 14 Sep 2004 10:09:49 +1000 Original-Received: by falcon.corp.resmed.org with Internet Mail Service (5.5.2657.72) id ; Tue, 14 Sep 2004 10:09:49 +1000 Original-To: "'bug-gnu-emacs@gnu.org'" X-Mailer: Internet Mail Service (5.5.2657.72) X-OriginalArrivalTime: 14 Sep 2004 00:09:49.0877 (UTC) FILETIME=[26B3D650:01C499EF] X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:8999 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:8999 I have taken to downloading the nightly tarball of the Emacs CVS = repository (I cannot download via CVS itself due to firewall restrictions). I have noticed that some Elisp I use/wrote is failing when running using the = CVS tip versus the 21.3 release. I tracked the problem behaviour to = split-string in subr.el The Elisp Manual (21-2.8) states (in part): When there is a match adjacent to the beginning or end of the string, this does not cause a null string to appear at the beginning or end of the list: (split-string "out to moo" "o+") =3D> ("ut t" " m") But using the CVS tip of Emacs I am getting this: (split-string "out to moo" "o+") =3D> ("" "ut t" " m" "") ^ |- this leading null string should not be there according = to Elisp 21-2.8 manual. Is this a deliberate change to the behaviour of Emacs or is it a bug? = i.e. I was unable to "locate" the current Elisp manual in the repository - lack = of knowing what to search for I guess :-), so I was unable to check the = latest requirements on split-string. Thanks Peter Peter Milliken Software Engineer ResMed Phone: +61 2 9886-5059 Fax: +61 2 9878-5564=20 Warning: Copyright ResMed. Where the contents of this email and/or = attachment includes materials prepared by ResMed, the use of those materials is subject exclusively to the conditions of engagement between = ResMed and the intended recipient. =20 This communication is confidential and may contain legally privileged = information. By the use of email over the Internet or other communication systems, = ResMed is not waiving either confidentiality of, or legal privilege in,the content of the email and of any attachments. If the recipient of this message is not the intended addressee, please = call ResMed immediately on +61 2 9886 5000 Sydney, Australia.