From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id qSqHGw2/AmUu5RUAWB0awg (envelope-from ) for ; Thu, 14 Sep 2023 04:06:37 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=scIXCdx/; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 672CF1E0C3; Thu, 14 Sep 2023 04:06:37 -0400 (EDT) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 59FFD1E028 for ; Thu, 14 Sep 2023 04:06:35 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C5524385842A for ; Thu, 14 Sep 2023 08:06:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C5524385842A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1694678794; bh=cLTw/C4092KATtyGVG0xwQQrtcs/zPPBwnKidumNzSY=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=scIXCdx/SUW74adtv6khyUaEZS+CP4Th99pJkNMceo6WkkWhv+RvuvKxSDhiu4Em9 9xDQoptkWvgfYPeddleS8Rwc3jaQembQ8tFNx7dWjjojm2eBza97I4DltQrBqW4BgZ ypqz5sjF6FjKd2P2WZ0y90wKAkPyj3La1Q662nm4= Received: from mail-oo1-xc2a.google.com (mail-oo1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) by sourceware.org (Postfix) with ESMTPS id 120B73858C27 for ; Thu, 14 Sep 2023 08:06:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 120B73858C27 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-573ac2fa37aso382475eaf.3 for ; Thu, 14 Sep 2023 01:06:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694678768; x=1695283568; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=cLTw/C4092KATtyGVG0xwQQrtcs/zPPBwnKidumNzSY=; b=EG9l5jXtNbXed0ywHTBXJGQR90HdXsnpj4ks87ig/xs90ZGadocTXfIK8g5aubUcBx JlSnEnI/hMYcpF7Qw5L3N0NBcHFaQYoDdbru+GHyY8iLBo+XmZ/GuQ/UJ6DGIkvpUV9k lgS5eIrOzh+iB8mUxBUh5/GmnF5nuFQfb4X00qCCRynfZazt/j1hQy+MBZRKuXmbG1G1 cKq1igmNgL7moI0ww2bgQy6u23f6T8YaG/r2tRK5SncAUH4UbDSuJRPLjH6/WA7cfzMG V0UBU6MyGWaD4dsukTwFwTVNzo2EzD1q0JVtqN4b5JQPymQASv4PZIuiCRN+3qlbhkK1 e80g== X-Gm-Message-State: AOJu0YzJjr6hVMOM8NzJEC5/wDQR8McZ9eW9OHGThHZuChR2M8asT8+C JIzRhzNk4cdgtHJAZ5uGYf9sKjEHqlwqooEQ9uI= X-Google-Smtp-Source: AGHT+IEoX1tZlG2LUzSNrPigotyz1SeHE9xhcizUWy7kzH7us+ZgC01ony8m6zA3JobsAS3uTPkfkOsRk5T//7ElQsk= X-Received: by 2002:a05:6870:7d18:b0:1d6:3d6a:fb37 with SMTP id os24-20020a0568707d1800b001d63d6afb37mr473833oab.46.1694678768260; Thu, 14 Sep 2023 01:06:08 -0700 (PDT) MIME-Version: 1.0 References: <838rhnawf9.fsf@gnu.org> <87ilgltt15.fsf@redhat.com> In-Reply-To: Date: Thu, 14 Sep 2023 01:05:57 -0700 Message-ID: Subject: Re: [PATCH] gdb/tui: add 'set tui mouse-events off' to restore mouse selection To: Pedro Alves , Eli Zaretskii , gdb-patches@sourceware.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: strager via Gdb-patches Reply-To: strager Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" It looks like my patch hasn't landed in GDB. Did it slip through the cracks= ? On Thu, Feb 2, 2023 at 11:59=E2=80=AFAM strager wro= te: > > On Thu, Feb 2, 2023 at 11:50 AM Pedro Alves wrote: > > I noticed the new command doesn't have a "set" callback, so I guess thi= s means > > that you have to disable and re-enable the TUI for the setting to take = effect? > > Or does it take effect immediately somehow? > > I tested it and it does take effect immediately. (I was surprised > too.) I think it's because you enter readline after you type the 'set' > command, and the mousemask code runs every readline.