From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?S=c3=a9bastien_Miquel?= Subject: Re: Bug: org-indent-region doesn't restore cursor position when org-src-tab-acts-natively is t [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)] Date: Sun, 9 Feb 2020 16:26:34 +0100 Message-ID: <4545c239-c8bf-fa16-2591-b0ee541ea732@posteo.eu> References: <603f9c4e-c621-7592-5b20-a7354c11d5d2@posteo.eu> <87zhdz1par.fsf@gnu.org> <878slijpzg.fsf@gnu.org> Reply-To: sebastien.miquel@posteo.eu Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:49841) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j0oTr-0003hN-Iw for emacs-orgmode@gnu.org; Sun, 09 Feb 2020 10:26:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j0oTq-00010F-5z for emacs-orgmode@gnu.org; Sun, 09 Feb 2020 10:26:43 -0500 Received: from mout01.posteo.de ([185.67.36.65]:54668) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j0oTp-0000tU-MD for emacs-orgmode@gnu.org; Sun, 09 Feb 2020 10:26:42 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 988A616005C for ; Sun, 9 Feb 2020 16:26:36 +0100 (CET) In-Reply-To: <878slijpzg.fsf@gnu.org> Content-Language: fr List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Bastien Cc: emacs-orgmode@gnu.org Thank you for looking into this. As far as I can tell, this is still broken in 9.3.3, which has your fix=20 included. I've updated org to 9.3.3, describe-function brings me to the org.el=20 file with your save-window-excursion modification, and I've deleted the=20 .elc file just in case. > Hi S=C3=A9bastien, > > S=C3=A9bastien Miquel writes: > >> Thank you for your reply. >> >> I can still reproduce with latest Org > Mh, yes, I can reproduce this now, and this is fixed in maint. > > Thanks! >