From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 10367@debbugs.gnu.org,
Daniel Colascione <dan.colascione@gmail.com>,
Leo <sdl.web@gmail.com>
Subject: bug#10367: 23.3.50; M-j in js-mode
Date: Fri, 16 Jul 2021 14:39:29 +0200 [thread overview]
Message-ID: <87r1fy8mbi.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnUUFUBoRZbZ0ZiSX-8MuMUVdqBEVQvOu=HN3TmhHq9ZQ@mail.gmail.com> (Stefan Kangas's message of "Wed, 25 Nov 2020 02:24:48 -0800")
Stefan Kangas <stefan@marxist.se> writes:
>> Any objection to binding M-j to c-indent-new-comment-line in js-mode?
>>
>> (Yes, yes, I know we should fix indent-new-comment-line to do what
>> c-indent-new-comment-line does, but I specifically designed js-mode to be
>> compatible with cc-mode editing functions, and this change will work for now.)
>
> There has been no objections within 9 years. But I don't use js-mode,
> so I don't know what the best behavior here is. Does it make more sense
> for js-mode users? If so, it seems like you should perhaps just go
> ahead and make that change?
It seems like this has changed in the years since this was reported. In
both c-mode and js-mode, `M-j' is bound to `default-indent-new-line',
and behaves the same in both modes, as far as I can tell.
So I'm closing this bug report. If there's something I'm
misunderstanding here, please respond to the debbugs address and we'll
reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-07-16 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 3:25 bug#10367: 23.3.50; M-j in js-mode Leo
2011-12-26 3:29 ` Daniel Colascione
2020-11-25 10:24 ` Stefan Kangas
2021-07-16 12:39 ` Lars Ingebrigtsen [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1fy8mbi.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=10367@debbugs.gnu.org \
--cc=dan.colascione@gmail.com \
--cc=sdl.web@gmail.com \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).