From: Tom Tromey <tom@tromey.com>
To: npostavs@users.sourceforge.net
Cc: 6806@debbugs.gnu.org, Tom Tromey <tom@tromey.com>
Subject: bug#6806: another reason for the patch
Date: Sat, 11 Feb 2017 08:19:04 -0700 [thread overview]
Message-ID: <87a89s69hz.fsf@tromey.com> (raw)
In-Reply-To: <871svdps7u.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net's message of "Sat, 04 Feb 2017 16:21:41 -0500")
Noam> So the opened comment was correctly terminated, and a new one started,
Noam> just as documented. Perhaps you don't like that `comment-multi-line' is
Noam> nil by default, but it doesn't look like a bug to me.
I'm not sure what to do about this now.
Should I revert the patch?
If it were solely up to me I would leave the patch in, since I think
non-nil comment-multi-line is more normal in JS code. And, if the patch
is reverted then I think comment-multi-line needs a :safe setting so it
can by set in .dir-locals.el.
Tom
next prev parent reply other threads:[~2017-02-11 15:19 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
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 [this message]
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=87a89s69hz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=6806@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.