From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: treesit indentation "blinking" Date: Thu, 30 Mar 2023 12:36:25 +0300 Message-ID: <4d8df485-adcb-64f3-742f-37c9a9a40f65@yandex.ru> References: <87h6ucik61.fsf@dancol.org> <0F406D08-56D4-4B21-B94D-A47681606911@gmail.com> <1870bcadd28.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> <1870cce6690.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> <35A837A9-59B4-4F1F-A5FA-8483C8024D76@gmail.com> <187104f6b48.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> <21d018e5-a730-12e3-f97c-fffa4f646ccf@yandex.ru> <83v8ioc2ou.fsf@gnu.org> <87sfdsx0r2.fsf@gmail.com> <87lejgsf0m.fsf@gmail.com> <83pm8s70o3.fsf@gnu.org> <83mt3u65vw.fsf@gnu.org> <87y1newqus.fsf@gmail.com> <6987b4f9-bb90-07cf-b64c-612574dff29e@yandex.ru> <87tty2wpt8.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7422"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Cc: Eli Zaretskii , dancol@dancol.org, casouri@gmail.com, emacs-devel@gnu.org, theo@thornhill.no To: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 30 11:37:05 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phoiN-0001ey-US for ged-emacs-devel@m.gmane-mx.org; Thu, 30 Mar 2023 11:37:03 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1phohr-0001MY-T0; Thu, 30 Mar 2023 05:36:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phohq-0001MI-Rf for emacs-devel@gnu.org; Thu, 30 Mar 2023 05:36:30 -0400 Original-Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1phohp-0002LG-5d; Thu, 30 Mar 2023 05:36:30 -0400 Original-Received: by mail-wm1-x334.google.com with SMTP id l37so10496486wms.2; Thu, 30 Mar 2023 02:36:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680168987; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=DZt7yIlF8E1fmzh+bpyhBEOEOdodXOgcup19rt7PbSo=; b=ITKVSTlL/jC9oLzPg8WoBSwjK549XOtrKd+nVqqkI343bEHwK0otN3w9DPB6hpu4QI N8DDqiFLKfzWHqWAYJyhiq6qZa6ZNyxjj7y8ANU0bIVI1eSOUglnXSG6UYL1w4FldPCd vXO7AYo1fBsa1iAZldpFLWPTeV+dTDRkHAUnqsiMWSu7CsU6aQ2O6zsZRNQtU+qTR6yw uGDCfccytW7Sl1UlmfhPn1cZxcmSubZxuDLqFFuk+GwOm7KTro5vVwFXCeZ9apz3ozIM 3RLglbhhbqOBuNGE3jbXZ0R1OlyPXPgaJsvMMN7XOJFSklcktgtUmL3YCau1obkftgyr TdNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680168987; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DZt7yIlF8E1fmzh+bpyhBEOEOdodXOgcup19rt7PbSo=; b=bh4Qe/qQUwNfLgmcJHXdyWO40AGLjmNSWVMbYV48fPVl3o2rLan39WsG3wo4lXkHaW XkRW0NnaSXZWSTh0G7y5KJaIKFS38LoTw0lJKWDe94hhhu6P2aV/UoZDgCUATO2M2244 lHP31p7MF1amWnSOf1ScbC0OT4Mwpm8HfEXHoMTyM+9PlDTfJxTEwyNb4t4MXKWofYcp Pz3PzTuM056Hw7wjiizOOgBhNO9FMdxob60CFo+re/DP709NUC1ugsxOIeXXpqGtQAHO 1LN9ZE3mb67LIU6bU2p6VT4y3qav9pUHwwT/A7OUIiLCrcgg5oTGNJn5AnGxbL6EWSCs Ep4w== X-Gm-Message-State: AAQBX9crFSw3k0YD2psjtn1gnYn3K2Wu+h00WSqBefgw1ody82j/f1e+ An9H+kG67Yxc/B4ukp/jl11ZUEqGI31EKA== X-Google-Smtp-Source: AKy350alt21ao2lv3JLoQaB+3Weov54i6BC/QU27GPd9FCg6lQ2KeiJF5rYt06+U7jBWR94XB6u1Eg== X-Received: by 2002:a7b:c444:0:b0:3ef:72e7:fce2 with SMTP id l4-20020a7bc444000000b003ef72e7fce2mr8450090wmi.17.1680168987158; Thu, 30 Mar 2023 02:36:27 -0700 (PDT) Original-Received: from [192.168.1.2] ([31.216.80.60]) by smtp.googlemail.com with ESMTPSA id v7-20020a5d4b07000000b002c56af32e8csm32124290wrq.35.2023.03.30.02.36.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Mar 2023 02:36:26 -0700 (PDT) Content-Language: en-US In-Reply-To: <87tty2wpt8.fsf@gmail.com> Received-SPF: pass client-ip=2a00:1450:4864:20::334; envelope-from=raaahh@gmail.com; helo=mail-wm1-x334.google.com X-Spam_score_int: -14 X-Spam_score: -1.5 X-Spam_bar: - X-Spam_report: (-1.5 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304847 Archived-At: On 30/03/2023 12:28, João Távora wrote: > This problematic already counts as "bouncing" to me, for some meaning of > "bouncing". c++-mode doesn't behave like that because indentation is > already where it is supposed to be if you type that sequence of > keystrokes. Okay, if that's what you meant. I think this one (indentation after RET in an incomplete function definition) should be fixed in the indentation rules. The contents of electric-indent-chars won't fix it either way. > And did you try the final example that I showed in the animated gif? > That's even more "bouncy", at least in my book. Yep, I see that. Also seems like something that could be improved in the indentation rules. When there is just one or no semis inside for's parens, we get ERROR nodes. I guess some rule is hit that should not be hit.