From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: discoverability, better defaults and which-key in Emacs Date: Sat, 03 Feb 2024 17:15:03 +0200 Message-ID: <86plxd37go.fsf@gnu.org> 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> <875xz57hzo.fsf@jeremybryant.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33832"; mail-complaints-to="usenet@ciao.gmane.io" Cc: incal@dataswamp.org, emacs-devel@gnu.org To: Jeremy Bryant Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 03 16:15:54 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 1rWHkI-0008cj-MQ for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Feb 2024 16:15:54 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWHjb-0002Lw-Ri; Sat, 03 Feb 2024 10:15:11 -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 1rWHjX-0002LX-Fl for emacs-devel@gnu.org; Sat, 03 Feb 2024 10:15:07 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWHjW-0001qs-A4; Sat, 03 Feb 2024 10:15:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=hmS6crmm1KarM4aHBk7GzE9cPFIgSH6dq8gJ+xWi2II=; b=XGoZBBG27JTD dglnTQc/KncC0d2L4++vPMzzt5cLrpjQVxVeiJL/WGFLexPu5E8vbaFwNGzEd5VuO0mElRn3u5KwH C2OBQluBhnOQNY7yo4DIKUKpvYKGR6HLDozGORkJkDO7baCkDADLLC6g4kRPcD7+rzeyfBBkCeYAb JsBzIlHbNLt7Mz2IVwJTDJQfnb+YQgmusmYf9kprCSfgmvc/x8K5xBBO6O9iC43U7YLR3trVzIdYI Ja9psBhiP/rvWPWLfmiE8W+O4W3d9bkKfgNSJ75p6FsR4mNYzndb25ITk3RXQ/ETrEBrDUKGACmi0 7K7jQ09PIRkw9SOLwZGP/w==; In-Reply-To: <875xz57hzo.fsf@jeremybryant.net> (message from Jeremy Bryant on Sat, 03 Feb 2024 14:07:19 +0000) 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:315832 Archived-At: > From: Jeremy Bryant > Cc: incal@dataswamp.org, emacs-devel@gnu.org > Date: Sat, 03 Feb 2024 14:07:19 +0000 > > > 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. I think a separate file is the best, thanks. > Good. As part of a discoverability feature, perhaps we could link to > this node in more places, eg in C-h C-h itself We could do that, but there's always the discoverability of "C-h C-h" itself...