GNU bug report logs - #72184
31.0.50; typescript-ts-mode does not bind RET to newline-and-indent

Previous Next

Full log

Message #14 received at 72184 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: jostein <at> secure.kjonigsen.net, Dmitry Gutov <dmitry <at> gutov.dev>
Cc: acorallo <at> gnu.org, 72184 <at> debbugs.gnu.org
Subject: Re: bug#72184: 31.0.50;
 typescript-ts-mode does not bind RET to newline-and-indent
Date: Sat, 27 Jul 2024 10:21:09 +0300

> Cc: 72184 <at> debbugs.gnu.org
> Date: Sat, 20 Jul 2024 03:22:47 +0300
> From: Dmitry Gutov <dmitry <at> gutov.dev>
> 
> On 19/07/2024 00:30, Andrea Corallo wrote:
> > Jostein Kjønigsen<jostein <at> secure.kjonigsen.net>  writes:
> > 
> >> When using typescript-ts-mode in a bare config without any custom hooks defined,
> >> RET ends up being bound (by default) to `newline`.
> >>
> >> This is suboptimal, given that users typically want newlines to be indented.
> >>
> >> RET should instead be bound to `newline-and-indent`.
> > Hi,
> > 
> > AFAIK this is what we tipically do, like: c-mode, c-ts-mode, lisp-mode,
> > emacs-lisp-mode etc.  Why 'typescript-ts-mode' should be different?
> 
> Right, we normally handle automatic indentation using 
> electric-indent-mode (which is on by default).
> 
> If RET behaves incorrectly in typescript-ts-mode somehow, more details 
> should be provided.

Jostein, could you please respond, so that we could make progress
here?

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.