all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: "Andrea Corallo" <acorallo@gnu.org>,
	"Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: 72184@debbugs.gnu.org
Subject: bug#72184: 31.0.50; typescript-ts-mode does not bind RET to newline-and-indent
Date: Sat, 20 Jul 2024 03:22:47 +0300	[thread overview]
Message-ID: <31020dbe-3268-47e3-94c9-8c7acef452fd@gutov.dev> (raw)
In-Reply-To: <yp1a5ie9ymf.fsf@fencepost.gnu.org>

On 19/07/2024 00:30, Andrea Corallo wrote:
> Jostein Kjønigsen<jostein@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.





  reply	other threads:[~2024-07-20  0:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 21:05 bug#72184: 31.0.50; typescript-ts-mode does not bind RET to newline-and-indent Jostein Kjønigsen
2024-07-18 21:30 ` Andrea Corallo
2024-07-20  0:22   ` Dmitry Gutov [this message]
2024-07-27  7:21     ` Eli Zaretskii
2024-07-27 11:50       ` Jostein Kjønigsen
2024-07-27 12:20         ` Eli Zaretskii
2024-07-31  8:55       ` Jostein Kjønigsen
2024-08-01  0:42         ` Dmitry Gutov
2024-08-15 10:03           ` Jostein Kjønigsen
2024-08-17 10:11             ` Eli Zaretskii

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=31020dbe-3268-47e3-94c9-8c7acef452fd@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=72184@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=jostein@secure.kjonigsen.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.