From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jeremy Bryant Newsgroups: gmane.emacs.devel Subject: Re: discoverability, better defaults and which-key in Emacs Date: Sat, 03 Feb 2024 11:30:09 +0000 Message-ID: <87v8757pa6.fsf@jeremybryant.net> References: <874jetaxri.fsf@jeremybryant.net> <86fryc1vsh.fsf@gnu.org> <87y1c398u8.fsf@jeremybryant.net> <867cjnz7rc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18904"; mail-complaints-to="usenet@ciao.gmane.io" Cc: justin@burkett.cc, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 03 12:37:28 2024 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 1rWEKu-0004kN-3O for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Feb 2024 12:37:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWEKE-0007nr-7v; Sat, 03 Feb 2024 06:36:46 -0500 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 1rWEKC-0007nQ-4w for emacs-devel@gnu.org; Sat, 03 Feb 2024 06:36:44 -0500 Original-Received: from out-185.mta0.migadu.com ([2001:41d0:1004:224b::b9]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWEKA-0003d7-AO for emacs-devel@gnu.org; Sat, 03 Feb 2024 06:36:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1706960197; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Wt3gXeZRsvjzynbFvXkElWf5yTf9Q8zBvsI++yEuedc=; b=Uo0gw6hXc7DIO+dGVa+GBmVZV4BhqA5hnj24jQFCDqaCKq9I+KcGUx0TbEu4WzmDAFEZNt yXgRFNRou6uxeP3a8SMRc5iMdCp2qBqOtbQcKSBd4RddrrVJ/SV5wb2xZdtIOKi4+Shlqj zNiQppNrfc2vvgT8EikbfBUvsYDTttlSw9Cm07HLBqhRMF4yUPGtE+wSizXNa7LkShWgnQ l1voleJxiO6BtyQQdaTKz0u66aUJmYU0DZlzgPEyUAGzYxj/FQFASjrRqjVqntvS8dtvSw PcHIlkorDCez59BgMkeh3zU/ZvVOguAWWdZjnad+mx3HlBFbC4wqxAU9rUliZQ== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-reply-to: <867cjnz7rc.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:1004:224b::b9; envelope-from=jb@jeremybryant.net; helo=out-185.mta0.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:315817 Archived-At: Eli, >> >> Here is a suggestion - include which-key in core and potentially enable >> >> by for new users. >> > >> > How do we detect "new users"? >> >> Good question, how about a user entry on the splashscreen? > > I don't think I understand, please elaborate. Do you mean we will ask > users to say, up front, that they consider themselves "new users", > each time they start a new Emacs session? Perhaps something like a persistent 'new user or discoverability' flag. This would be toggled by the user, and could be suggested by Emacs based on heuristics such as - Absence of init file (.emacs) - First launch of Emacs, maybe a reminder later > >> > Another idea is to add a feature whereby, after some delay after the >> > user types an incomplete key sequence, the buffer usually popped by >> > C-h or '?' pops up automatically. This would be a smaller change in >> > the UX, which might therefore be more easily acceptable even by >> > not-so-new users. >> >> Interesting, which buffer and part of the code is this? >> (it seems to appear in *Help*) > > Yes, it appears in *Help*, and is produced by describe-prefix-bindings > (via prefix-help-command). Thank you for the suggestion, I will look at this part of the code.