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 14:07:19 +0000 Message-ID: <875xz57hzo.fsf@jeremybryant.net> References: <874jetaxri.fsf@jeremybryant.net> <86fryc1vsh.fsf@gnu.org> <87y1c398u8.fsf@jeremybryant.net> <867cjnz7rc.fsf@gnu.org> <87jznnbbax.fsf@dataswamp.org> <86v877xqez.fsf@gnu.org> <87mssh7owx.fsf@jeremybryant.net> <86sf293fwm.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="17111"; mail-complaints-to="usenet@ciao.gmane.io" Cc: incal@dataswamp.org, 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 15:15:22 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 1rWGnf-0004A9-Cv for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Feb 2024 15:15:21 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWGmh-0007lV-SQ; Sat, 03 Feb 2024 09:14:19 -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 1rWGmg-0007l2-E3 for emacs-devel@gnu.org; Sat, 03 Feb 2024 09:14:18 -0500 Original-Received: from out-172.mta0.migadu.com ([2001:41d0:1004:224b::ac]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWGmd-0003cY-94 for emacs-devel@gnu.org; Sat, 03 Feb 2024 09:14:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1706969648; 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=buGbTe+3ntQslgmL+LNcN2suNvJHj8BxhtRp+MQbbok=; b=kaYXgEq8ExZHaSOAH2HbYyZn2FJRP5VlmgD/YzwmDuJgWVjow9ooPSsokXw7dYZZgi4yGt YRrooXJ4CC3+v2TjWeKOy4Lcw8jBJwXRQDA0dajucF20Qiwr3tMdkBITInoRsGtn7eGf0f 0EihXY6n2KPC/G2NOHOz4svDsH5OPlMapj65vOLVGTYPB/6+y0ywXu4ApZFW1L3ovWnhJL ia9IEvfvbU2pgBRMxoSfJk7DE5bZZWPjPDz+sJ3tVW8/Ovz/+/Y1foXgbi7fED4nsHJdMa feT07Ux59a/0lizBqam/2/2xfy+Oz+MK5EuzkUIVJ0g2bmWueIN0zI2vHaz+Sw== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-reply-to: <86sf293fwm.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:1004:224b::ac; envelope-from=jb@jeremybryant.net; helo=out-172.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:315831 Archived-At: >> > Patches welcome, of course. >> >> Would it be useful to have a few 'starter' commented init files / >> configurations. >> This would be a built-in version of personal init files, but very small, >> and commented. > > I think the idea was to have an interactive feature, whereby a user is > asked questions regarding his/her preferences and needs, and the > related features are then enabled. > > A related idea was to come up with mostly-independent groups of > settings that are suitable for some general usage pattern. For > example, someone who needs to develop Python programs might want > certain optional features enabled. > > Having init files like you suggest once again places the burden on the > users to read the comments and decide what to do about them. I think > this is not the optimal solution. I understand. How should this be implemented, would this be a new file in the Emacs tree, or part of an existing file. I can volunteer to work on an early prototype. > >> > Some Emacs commands I suggest for this are: >> > >> > C-u M-x apropos >> > M-x apropos-documentation >> > C-h R elisp RET followed by 'i' (Info-index) and the subject >> >> Would it make sense to have a specific small section in the Emacs manual >> that >> Then a link to that manual section could be provided early on >> A sort of 'discoverability start point'? > > We already have it: see the beginning of the "Help" node in the user > manual. Good. As part of a discoverability feature, perhaps we could link to this node in more places, eg in C-h C-h itself