From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Upcoming merge of adaptive-wrap Date: Sat, 27 Jan 2024 03:44:59 +0200 Message-ID: <37bf6ee2-3bc0-49e8-aa55-70c77b6c5bf2@gutov.dev> References: <878r4eqjh8.fsf.ref@yahoo.com> <878r4eqjh8.fsf@yahoo.com> <875xzgookd.fsf@yahoo.com> <1e6f618f-5572-40e4-addb-016b467def37@gutov.dev> <87il3gn89u.fsf@yahoo.com> <87bk98n3l3.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16771"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: emacs-devel@gnu.org, Stephen Berman To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 27 02:45:57 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 1rTXlc-0004AA-Gv for ged-emacs-devel@m.gmane-mx.org; Sat, 27 Jan 2024 02:45:57 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rTXku-0007TZ-7T; Fri, 26 Jan 2024 20:45:12 -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 1rTXkq-0007T8-10 for emacs-devel@gnu.org; Fri, 26 Jan 2024 20:45:08 -0500 Original-Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rTXkn-00050F-3n for emacs-devel@gnu.org; Fri, 26 Jan 2024 20:45:07 -0500 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E55525C0103; Fri, 26 Jan 2024 20:45:02 -0500 (EST) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 26 Jan 2024 20:45:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1706319902; x=1706406302; bh=kTFD5uwwm3WJZvhaU8hJMLIF1eeijK1OxzPAwopwPFo=; b= K2p9iqhpCJg/22PsRc0EwzLzV/Jrvypuhw2uvTgbGQfVGlA3r44Kqp5whU/Svp8t fLJETMd33+PNMUYm5U9jcuZq4TYnMqotnB9fIUMyUkmOj6Fs/DUusJgNAICC2B3W nGm2w8+1MathlVQ0JZ2N9EdEmuGtY+ccXoFENIVR1uIwlR4h7JHN1J/uxKHaudam GUWw8kdg5Dcswz7DSUulCVdsLLgDp97hxARJnGzGjlijjzo8Ld/HVjfFF6cUsqo9 P4oCQ5wc1NE9QsWTUQ1hN055iHBC/MgdWNnkT2iI0YEqNkSyTEvdl2qV+xOnG59q s64Ez+BgU3tWO+D1v7YXQg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1706319902; x= 1706406302; bh=kTFD5uwwm3WJZvhaU8hJMLIF1eeijK1OxzPAwopwPFo=; b=K 1YXbHuVTGb0XafjYvmukAZdli+t+xXOhD9fFILpjwZcV5H3NtZVO/UJTEBT4H8WW tSNeuvdVnotngbla0p2YUzYUTw0WodBj4WLjfOU0n6BhRtuy5CSsk/ehWv/2LkL8 G2pMIZ0L2+kjOfkp3ypDKz01TdhljkwcXaYUysTYpNJUDLbNlucmul4aUkHphAm7 lu00LvYjLjEnnxxI5JKyyciOVr8HvIDs00EbF7dkKON9tGgl/4kJrWbOJShX4Eik 6A5eDkyBJVfupS8uttbyDTQJlRxf6dZ+z2G7D+pbFVZqFU+ENHaR91dxUyotlWRD 03tnppdndhNhnI4UW8EHQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdelkedgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhepteduleejgeehtefgheegjeekueehvdevieekueeftddvtdevfefhvdevgedu jeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepug hmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 26 Jan 2024 20:45:01 -0500 (EST) Content-Language: en-US In-Reply-To: <87bk98n3l3.fsf@yahoo.com> Received-SPF: pass client-ip=66.111.4.26; envelope-from=dmitry@gutov.dev; helo=out2-smtp.messagingengine.com X-Spam_score_int: -26 X-Spam_score: -2.7 X-Spam_bar: -- X-Spam_report: (-2.7 / 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_SBL_A=0.1 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:315450 Archived-At: On 26/01/2024 06:03, Po Lu wrote: > Dmitry Gutov writes: > >> If you're talking about getting a feature known to the maximum number >> of users possible (and not just hardcore ones who are with us for >> decades and scrutinize every new release), a lot of those potential >> users either have been using Emacs a while and don't read NEWS for >> every release, or will install their first Emacs of some later version >> than the one that the feature X has been added (and thus will miss all >> older NEWS files). > > I have been using Emacs for "a while", and I read NEWS with every new > release with no difficulty whatsoever. Regardless of the extent of our > users' inclination to read NEWS, Emacs's facilities for searching > through multiple files are more than adequate for locating features > there, and even if not, it is not reasonable to argue that a drastic > difference in detail is nullified by arranging items in a one-line > format. But would they, largely? You actually have to visit the directory which hosts NEWS on your system (where is it installed to?), mark all previous NEWS files and do the search. That's non-trivial. > Compare: > > adaptive-wrap Smart line-wrapping with wrap-prefix > > with: > > * Editing Changes in Emacs 30.1 > > ** New minor mode 'visual-wrap-prefix-mode'. > > When enabled, continuation lines displayed for a folded long line will > receive a 'wrap-prefix' automatically computed from surrounding context > by the function 'fill-context-prefix', which generally indents > continuation lines as if the line were filled with 'M-q', or similar. > > I don't think any of us are capable of arguing with a straight face that > the first example will earn adaptive-wrap more users than will the > second. If you sit every user behind a screen and force them to read either of the texts entirely, sure. But that's not how it usually works. > Not to mention that other documentation will be installed to > accommodate users who are not upgrading Emacs, which you have not taken > into account at all. It's a good explanation (easier to understand than the summary, I agree), but I'm curious what would you improve in the summary to make it more recognizable. Any particular keywords? From where I'm standing, even after reading the description, all the important ones seem to be there: "wrap", "adaptive", "line-wrapping", "wrap-prefix". Even if you're reading the NEWS, you probably don't carefully scan every entry, so there must be some particular words which might have piqued your interest in the way that the current summary does not. >> 1139 one-liner summaries, OTOH, are always searchable with C-s. > > And how do you suggest users search for adaptive-wrap, armed with little > information beyond that feature's behavior? For the terse descriptions > in the package list to be useful, the user must already be aware of the > name of the package being sought or the description its author has > chosen. The one-liner description indeed needs to be recognizable enough.