From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Brahimi Saifullah Newsgroups: gmane.emacs.devel Subject: Re: Scroll bars on macOS builds Date: Sat, 22 Jan 2022 20:10:26 -0300 Message-ID: <845yqbxt7h.fsf@gmail.com> References: <108046697.471165.1640987931513@mail1.libero.it> <1555566770.476092.1641148898999@mail1.libero.it> <366682291.727051.1641946326079@mail1.libero.it> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28499"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (windows-nt) Cc: Angelo Graziosi , "emacs-devel@gnu.org" To: Alan Third Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 23 00:12:04 2022 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 1nBPYC-0007Gi-Oe for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Jan 2022 00:12:04 +0100 Original-Received: from localhost ([::1]:33540 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nBPYB-0003Pp-LX for ged-emacs-devel@m.gmane-mx.org; Sat, 22 Jan 2022 18:12:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47340) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nBPWx-0002at-9Z for emacs-devel@gnu.org; Sat, 22 Jan 2022 18:10:48 -0500 Original-Received: from [2607:f8b0:4864:20::32d] (port=43960 helo=mail-ot1-x32d.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nBPWt-00066R-OZ for emacs-devel@gnu.org; Sat, 22 Jan 2022 18:10:46 -0500 Original-Received: by mail-ot1-x32d.google.com with SMTP id q13-20020a9d4b0d000000b0059b1209d708so16874564otf.10 for ; Sat, 22 Jan 2022 15:10:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=ywq1TIWHroqLJV7TXRRDifiYM+xOnNdADnOZA0tAFkw=; b=BfQFGkk969Omd1tWtVAfrblMhCqlXtQYz3oyGnbDcUS+eA3ty5tuUIFjtpWgp0PRNx 0wmLA2uHj0aXA51A4BcaX7et2TErAqJCgJKIDYorC6oFj5ZrqN5M7/M5rJBUmmi9iMOF pIrQD+muGlmaid1mLnulSNtug4N9p4/RlwW0oosuoQ5Uj6y6OAMiOmYpbBzOvjjimj4Y aL8iawJoyWSP5O0xKsHxGFp/+/xHreqbSBMnp7pV34uqSCIflCMhySW1iWdp1fNDC7/B GsevX/xO6b9OpEKbbfpbKNieIY5s18l+lNQ5N3uQAIon/nFVs9SbRz0sloQ1D2l2Y/fi x86w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=ywq1TIWHroqLJV7TXRRDifiYM+xOnNdADnOZA0tAFkw=; b=U+VCo07bxNPypYHTvtK8tHdFvyBK/2SlhrI3Zrbd7A6v68ZdOxhE+S/oInZ8CSKLtE g7MhEf3qA8QCFpYbHvZfjINiy0GmoeMt1LhxP2DndpQQztut/KhmQgtp/45790PM9Tzp SLuAhVNomahtADUdCb5lFmM5WXVz3Li2YPfsC2soQROTNF0VrsqknWtz0bV+LTP9JEd8 jnNOEHtXhq0PV3wECsTtdwuTE6lUZD1tnYqIlZYasAzgc6RiBBZri1gH3Csdzm6LfsRG EI5zbRhfO9WET0jmznYDlyfPqbGOOyDiUez9Esvv5/Zq+OU4e7atsztIuRNo/BTQOIvk 4+qA== X-Gm-Message-State: AOAM531xpDPisQHlY/Bxtsbw7/wgo4OpHu4/zhEU2kMZYBNVb5lzkKU2 mSQr5SLQ50iV+wMEwVIe4CCTKu50bfl5aA== X-Google-Smtp-Source: ABdhPJz8GehGF8cnXHoWkhznyix0d1bkNUcyA7/TlY0oxHoKVl6/hSjrUdTEenPW+7k1EbA+V0zqeQ== X-Received: by 2002:a9d:66d:: with SMTP id 100mr7261256otn.40.1642893030726; Sat, 22 Jan 2022 15:10:30 -0800 (PST) Original-Received: from COMPUTADOR ([2804:14d:90bc:8171:1094:922a:903c:dc53]) by smtp.googlemail.com with ESMTPSA id q188sm624230oig.15.2022.01.22.15.10.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 22 Jan 2022 15:10:30 -0800 (PST) In-Reply-To: (Alan Third's message of "Sat, 22 Jan 2022 11:33:36 +0000") X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::32d (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::32d; envelope-from=brahimi.saifullah@gmail.com; helo=mail-ot1-x32d.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, PDS_HP_HELO_NORDNS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, 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" Xref: news.gmane.io gmane.emacs.devel:285236 Archived-At: Alan Mackenzie writes: > With the current state of the git branch, flymake on a .el file now > seems to be working for me. Yes, Flymake is working perfectly now. I did notice an issue with the warning for unused forms: value returned from (# 1 1) is unused (from byte-compiling a file that consists of "(+ 1 1)") I expect that the symbol should be used, not the symbol with positions. But it looks like this just got fixed a few hours ago in master while my build was from before the merge. While further testing this I also found a couple problems relating to unused function arguments -- I'm unsure if they have anything to do with the latest round of changes or not. First, a bug: (defun f (a b c) ; ^^^ Warning: Unused lexical argument `a' ; Warning: Unused lexical argument `b' "A B C." (+ 1 1)) ; ^^^ Warning: Unused lexical argument `c' You should be able to reproduce it by copying the above function somewhere and byte compiling (sans the). If the function consists of a single form, the position returned for the last "unused lexical argument" will wrongly point to it. In this example, the warning about C being unused will instead point to `+'. The second issue is that, even when the unused lexical argument warnings work correctly, they always point to the "defun," and not to the actual argument in question. Not the end of the world of course, but it would be nice for them to be more accurate. > Again, many thanks for the help. And thanks for the work you've done, faulty warning positions had always been an annoyance of mine :)