From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 0FqrOLbwo2EaFgEAgWs5BA (envelope-from ) for ; Sun, 28 Nov 2021 22:12:22 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id yGFMNLbwo2HOSAAAB5/wlQ (envelope-from ) for ; Sun, 28 Nov 2021 21:12:22 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7E8EA29DED for ; Sun, 28 Nov 2021 22:12:22 +0100 (CET) Received: from localhost ([::1]:33556 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mrRTA-0002t9-Db for larch@yhetil.org; Sun, 28 Nov 2021 16:12:20 -0500 Received: from eggs.gnu.org ([209.51.188.92]:38780) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrRSY-0002sl-EB for emacs-orgmode@gnu.org; Sun, 28 Nov 2021 16:11:42 -0500 Received: from mx03.uni-tuebingen.de ([134.2.5.213]:41492) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mrRSW-00071D-D9 for emacs-orgmode@gnu.org; Sun, 28 Nov 2021 16:11:42 -0500 Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) by mx03.uni-tuebingen.de (Postfix) with ESMTPSA id 3B28320CA6F1; Sun, 28 Nov 2021 22:11:35 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailauth.nyi.internal (Postfix) with ESMTP id 32E8D27C0054; Sun, 28 Nov 2021 16:11:30 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 28 Nov 2021 16:11:30 -0500 X-ME-Sender: X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrheeigddugeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffujghffffkgggtgfesthhqtd dttddtjeenucfhrhhomheptfhitghhrghrugcunfgrfihrvghntggvuceorhhitghhrghr ugdrlhgrfihrvghntggvsehunhhiqdhtuhgvsghinhhgvghnrdguvgeqnecuggftrfgrth htvghrnhepkefgheduffevteeijedvudfgtdelhedtffegkedvfeeuheeggfevffffjedu ffeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprh iflhdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidquddujeekgeehuddvkedq udeltddvjeelgeegqdhrihgthhgrrhgurdhlrgifrhgvnhgtvgeppehunhhiqdhtuhgvsg hinhhgvghnrdguvgesfhgrshhtmhgrihhlrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 28 Nov 2021 16:11:29 -0500 (EST) Received: from rwl by aquinas with local (Exim 4.92) (envelope-from ) id 1mrQc2-0007Ra-HA; Sun, 28 Nov 2021 21:17:26 +0100 From: Richard Lawrence To: Colin Baxter =?utf-8?Q?=F0=9F=98=BA?= Subject: Re: Is M-j broken for you in Org on Emacs 27 and 28? In-Reply-To: <87v90cpcdx.fsf@yandex.com> References: <87lf18fue9.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> <87v90cpcdx.fsf@yandex.com> Date: Sun, 28 Nov 2021 21:17:26 +0100 Message-ID: <87ilwcf31l.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=134.2.5.213; envelope-from=richard.lawrence@uni-tuebingen.de; helo=mx03.uni-tuebingen.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1638133942; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=yU4KY6topUyqNNJcS/f6RjRdGej+NzL3rCVEeehDJ+M=; b=LRkbnncnxBjR8iyCu6uw8w34JrvnBCh9KEdZOemHZupoDLYPS3PiuEmktkOsFTv+8Cp7hp byNTX5DO40oSNAa1JzTmiPuiQdmiYoXj/XC17NSRag/zmN1HM4pjFdRFsu4V8DAQ//WNiQ wXyih/effOuICUKJebMYrZQ71TZc87qSaYtRVOy5ncIAMrN7eFZda/udGemFQ7wRZ2aDLI MAlqcj1HR4FeZZb3Zi+vKaWSt7XVhVQGkYjdXnAO7L9YTHUtqfQ8+FJEra+G+ds595Fv9u 13tj7scmEi2cfExiJpR53qUXSdpYBNPgIkxETL27X2/k+y9+8B4J71dywrybww== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1638133942; a=rsa-sha256; cv=none; b=Ex6XJcKUhRtLwDDV3gnc2QZLJFPXZvwN2vfnT0Esw1jDNhA8FnisdSCk4CwhAyCeHToFHF svq1JCIHeNppoiZFcDplGFqzQJ7+YtCdU7q0QzSjKqLPf5jsFgrGabfM28/C9c9CW0dogS wR9c+C5OEvEazuYbKxEFZTRVlQQuSpnqkZDjTT+W7TLI7aQVdcOtH9Ze9+K6NMrcKekxtu yqYB3NQHSCYnlkqZtIEtLeGtc38Sdz19lyEGBF2lanETdFyBE04n0tuaydkXVlZqPsWr5l XsjGz0ECveGMsz1KfEDGzyRelQ9DPVzoE8saFppx/tB3Gb39mPpptE5h9AFibA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -2.01 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 7E8EA29DED X-Spam-Score: -2.01 X-Migadu-Scanner: scn0.migadu.com X-TUID: Kzr64huLRNXP Colin Baxter =F0=9F=98=BA writes: > I confirm that it also appears broken to me in emacs-27.2, with the same > error as you found. I have never noticed it before, possibly because I > use C-j rather than M-j. Thanks for confirming. Do you know what the difference between C-j and M-j is "supposed" to be? They both do very mode-dependent things. I guess M-j is more explicitly aimed at continuing comments (which is probably why I started using it), but it has always worked great for me as a newline-and-indent-like-I-want command outside of comments too. --=20 Best, Richard