From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nathan Weizenbaum <nweiz@google.com>
Cc: 6806@debbugs.gnu.org
Subject: bug#6806: Set comment-multi-line in js-mode
Date: Sat, 11 Sep 2010 15:54:37 +0200 [thread overview]
Message-ID: <jwvvd6c1j3u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <AANLkTi=dackW-xN=KG2jDqnm=hph7J-6PsodT7uMArSt@mail.gmail.com> (Nathan Weizenbaum's message of "Mon, 9 Aug 2010 10:56:56 -0700")
> My fix doesn't actually fix the "/* */" issue, unfortunately. However, it
> doesn't break "//" either; note that comment-multi-line is t for e.g.
> c-mode, and comment-indent-new-line works for "//" there.
Indeed, I misremembered. Feel free to install this patch.
Stefan
> On Mon, Aug 9, 2010 at 4:33 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
>> > js-mode doesn't set the comment-multi-line variable. This results in
>> > comment-indent-new-line behaving improperly when used in a multi-line
>> > comment, which also affects auto-fill-mode, according to the
>> documentation
>> > for comment-multi-line.
>>
>> If I understand and remember correctly, this is not the right fix for
>> your problem: setting comment-multi-line to t will fix your problem with
>> "/*..*/" but will introduce another for "//....\n" and vice-versa.
>>
>>
>> Stefan
>>
next prev parent reply other threads:[~2010-09-11 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 18:36 bug#6806: Set comment-multi-line in js-mode Nathan Weizenbaum
2010-08-08 20:40 ` Chong Yidong
2010-08-09 0:14 ` Nathan Weizenbaum
2010-08-09 11:33 ` Stefan Monnier
2010-08-09 17:56 ` Nathan Weizenbaum
2010-09-11 13:54 ` Stefan Monnier [this message]
2010-09-28 18:11 ` Chong Yidong
2017-01-18 4:56 ` bug#6806: another reason for the patch Tom Tromey
2017-02-04 21:21 ` npostavs
2017-02-04 21:34 ` npostavs
2017-02-11 15:19 ` Tom Tromey
2017-02-12 4:21 ` npostavs
2017-02-12 6:16 ` Tom Tromey
2017-02-15 4:50 ` npostavs
2017-02-04 20:29 ` bug#6806: checked in " Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvvd6c1j3u.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6806@debbugs.gnu.org \
--cc=nweiz@google.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.