From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: npostavs@users.sourceforge.net Newsgroups: gmane.emacs.bugs Subject: bug#6806: another reason for the patch Date: Sat, 04 Feb 2017 16:21:41 -0500 Message-ID: <871svdps7u.fsf@users.sourceforge.net> References: <874m0xhsp9.fsf@tromey.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1486243279 9555 195.159.176.226 (4 Feb 2017 21:21:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 4 Feb 2017 21:21:19 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Cc: 6806@debbugs.gnu.org To: Tom Tromey Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Feb 04 22:21:12 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ca7lf-0001zi-Rj for geb-bug-gnu-emacs@m.gmane.org; Sat, 04 Feb 2017 22:21:11 +0100 Original-Received: from localhost ([::1]:40896 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ca7li-0003Vc-5W for geb-bug-gnu-emacs@m.gmane.org; Sat, 04 Feb 2017 16:21:14 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ca7lb-0003VK-8a for bug-gnu-emacs@gnu.org; Sat, 04 Feb 2017 16:21:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ca7lW-0007Xy-Mf for bug-gnu-emacs@gnu.org; Sat, 04 Feb 2017 16:21:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:58140) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ca7lW-0007Xu-IE for bug-gnu-emacs@gnu.org; Sat, 04 Feb 2017 16:21:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ca7lW-0008SP-7M for bug-gnu-emacs@gnu.org; Sat, 04 Feb 2017 16:21:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: npostavs@users.sourceforge.net Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 04 Feb 2017 21:21:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 6806 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 6806-submit@debbugs.gnu.org id=B6806.148624323932458 (code B ref 6806); Sat, 04 Feb 2017 21:21:02 +0000 Original-Received: (at 6806) by debbugs.gnu.org; 4 Feb 2017 21:20:39 +0000 Original-Received: from localhost ([127.0.0.1]:56339 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ca7l9-0008RS-7f for submit@debbugs.gnu.org; Sat, 04 Feb 2017 16:20:39 -0500 Original-Received: from mail-io0-f178.google.com ([209.85.223.178]:33630) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ca7l8-0008RF-0k for 6806@debbugs.gnu.org; Sat, 04 Feb 2017 16:20:38 -0500 Original-Received: by mail-io0-f178.google.com with SMTP id v96so42053030ioi.0 for <6806@debbugs.gnu.org>; Sat, 04 Feb 2017 13:20:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=GqUA9AczWRrFHQIt4YkSkX7uLVwoGeCn7ALQS2JaZKo=; b=prdQXrMYSybgmHuwTHG/sc5JzfVnD0UP/3KQUfHEE57mtUpAjfdy4Q8vHtUSKP8nRD LZQ2cj761FVBLmd1nvZtYWqRFjcbXRsTOQFQwrJr38Ym3C5MJrSEnwshggnDRLpDD4kF T5V19NNhjRLUZ1J1JlZcWBm9i42W+h5quQzlgYIq6m/RoLtuZAT6r83C9K2wsp1H1ZzE 1FE9CMxf4gUHFsgxPwsSMjHDhYalhRE5SHDbTaPMZ5ELfl6NYzRFsvllwoX2QGgZGWI5 CoJQMGI0TKgJBqLqxiAqLs2Di8yczAW5fiYk378DHl8tcJiKM6Gbx+KJlBIm7ZqNxjPL cm9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=GqUA9AczWRrFHQIt4YkSkX7uLVwoGeCn7ALQS2JaZKo=; b=DxyYDuqHJ4XPkoLm55wiC5gDx1OHsB9us2Tcuhr40HmWq/b86cwcyM/m+bLarteS84 IJj+eq9XI7xtiSRr0zAZnCeiEufGZYfFa0XJv+TEAcmiozjxmZ8wEWgodNseKMUlErwK Vlw/VNnT+cP1XJOqJ2RnNqEbSPGtCHLMvKWSwaP+okei/VF+7lZju3A6YtxogmMW+KqL tt2U3Un2hMuQ8utYL/UFK9dtA/D1ek4gz4r+tExSba4NvhV+lt3jkSP9qrGMmy9ks+R0 cZSCQlTkgFAR7PGKDQr3+PuFdt46Fd/V4wFAC48KLUNUILOmFurXSWwpJ/15uu+0k3KC fpaQ== X-Gm-Message-State: AMke39mPe6Tk1i4WIcfgdj9t8SdsL/iJSRISbJvuVz1ZZvWA7qMwr8gGOR5DKvFF1mv4Fw== X-Received: by 10.107.159.14 with SMTP id i14mr2146312ioe.143.1486243232497; Sat, 04 Feb 2017 13:20:32 -0800 (PST) Original-Received: from zony ([45.2.7.65]) by smtp.googlemail.com with ESMTPSA id u63sm4994490ioi.4.2017.02.04.13.20.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 04 Feb 2017 13:20:31 -0800 (PST) In-Reply-To: <874m0xhsp9.fsf@tromey.com> (Tom Tromey's message of "Tue, 17 Jan 2017 21:56:18 -0700") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org 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 Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:128967 Archived-At: Tom Tromey writes: > Hi. I'd like to resurrect this bug. > > While working in JS I found a bug, which I tracked down to the same > change indicated here. Basically, auto-fill in JS mode will sometimes > insert a "/*" on a filled line, where it should not. > > You can see a precise recipe in the new test case, in the attached > patch. > > One funny thing is that if you do this interactively (in my real-world > case I had auto-fill-mode enabled), you have to be sure that there isn't > a newline after point. If there is a newline, the filling works > properly. > > Anyway, let me know what you think. I'd like to check this in, but, > given the comments in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=6806#23 > I suppose I would not close the bug. Sorry I missed this before you pushed the patch, but I'm not sure this is a bug. If I revert the setting of `comment-multi-line' then with your test scenario, the result of auto fill is /* test test test test test test test test test test test test test */ /* test test test So the opened comment was correctly terminated, and a new one started, just as documented. Perhaps you don't like that `comment-multi-line' is nil by default, but it doesn't look like a bug to me.