From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.bugs Subject: bug#36250: [PATCH] Improve a bit frame-resize-pixelwise documentation Date: Fri, 28 Jun 2019 16:59:45 +0300 Message-ID: <1561730385.29740.0@yandex.ru> References: <1560707992.19774.0@yandex.ru> <20190618203502.31223-1-Hi-Angel@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="237988"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36250@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jun 28 16:21:25 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hgrki-000zlq-Bk for geb-bug-gnu-emacs@m.gmane.org; Fri, 28 Jun 2019 16:21:24 +0200 Original-Received: from localhost ([::1]:60524 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgrkh-0006VD-CG for geb-bug-gnu-emacs@m.gmane.org; Fri, 28 Jun 2019 10:21:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34779) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgrQB-0006tU-LP for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:00:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hgrQ5-00009z-LJ for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:00:11 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57388) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hgrQ5-00009l-HX for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:00:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hgrQ3-00046K-6H for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:00:05 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Konstantin Kharlamov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 28 Jun 2019 14:00:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36250 X-GNU-PR-Package: emacs Original-Received: via spool by 36250-submit@debbugs.gnu.org id=B36250.156173039815730 (code B ref 36250); Fri, 28 Jun 2019 14:00:03 +0000 Original-Received: (at 36250) by debbugs.gnu.org; 28 Jun 2019 13:59:58 +0000 Original-Received: from localhost ([127.0.0.1]:42699 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hgrPy-00045d-Bm for submit@debbugs.gnu.org; Fri, 28 Jun 2019 09:59:58 -0400 Original-Received: from forward103p.mail.yandex.net ([77.88.28.106]:40003) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hgrPv-00045P-KC for 36250@debbugs.gnu.org; Fri, 28 Jun 2019 09:59:57 -0400 Original-Received: from mxback15j.mail.yandex.net (mxback15j.mail.yandex.net [IPv6:2a02:6b8:0:1619::91]) by forward103p.mail.yandex.net (Yandex) with ESMTP id 82E4618C1DAB; Fri, 28 Jun 2019 16:59:48 +0300 (MSK) Original-Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback15j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id VQ9esrri2u-xmTil5Tu; Fri, 28 Jun 2019 16:59:48 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1561730388; bh=lWYWlY2pc0F9czfWtwwH35czfaCFHP0+40EYU5I84uQ=; h=In-Reply-To:Cc:To:Subject:From:References:Date:Message-Id; b=hAy55swMpGxPzJBWdA9lO8WSMw17Gz+Bb/y9S7t2rQ+qHQA0hgmfFjWl32Naoie/O v9Ca9h/YJNeRJuh+dVw783trJn+9EkSmepKW7u4FwTzo8+oLZtIgT5gw9t70WlkW6K 8BXSffBHUVKo6gIhPPNcs+0k2n410wG5+wUklxGU= Authentication-Results: mxback15j.mail.yandex.net; dkim=pass header.i=@yandex.ru Original-Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id vHbiz8kyMt-xkw8SHpL; Fri, 28 Jun 2019 16:59:46 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) In-Reply-To: <83zhm1hmt2.fsf@gnu.org> X-Mailer: geary/3.33.1 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:161724 Archived-At: =C2 =CF=F2, =E8=FE=ED 28, 2019 at 16:16, Eli Zaretskii =20 =ED=E0=EF=E8=F1=E0=EB: >> Date: Fri, 28 Jun 2019 14:27:14 +0300 >> From: Konstantin Kharlamov >> Cc: 36250@debbugs.gnu.org >>=20 >> > I don't see why you needed to remove part of the text. It isn't a >> > repetition: the first sentence talks about frames in general, the >> > second only about the initial frame. The bit about the init file=20 >> is >> > only relevant to the latter. >>=20 >> The specific part of text being removed sounds as"in order to set=20 >> the >> size of a frame in pixels, ", which explains what happens when=20 >> variable >> is non-nil. >>=20 >> However, if you read both of two paragraphs of documentation, you=20 >> may >> find that the 1st paragraph already explains the technical details >> behind the variable, and the "non-nil" word in particular appears=20 >> twice. >>=20 >> At that point, if reader came to 2nd paragraph, they probably know=20 >> what >> Emacs does when variable is non-nil; or at least they know where to >> look that up. So, repeating that part again does nothing aside of >> wasting one's mental resources used to parse the sentence. >=20 > I think you read "resize a frame" and "set the size of a frame" as > referring to the same operation. But they aren't: the former is about > changing the size of an existing frame with a mouse or with > set-frame-size, whereas the latter is about doing other things that > implicitly require the frame's size to have pixel resolution. >=20 > So no, this is not repetition, and should not be removed. Right, but the 1st paragraph also says "If this is non-nil, [=85] frame=20 sizes can increase/decrease by one pixel". I.e. this says that setting=20 the variable to non-nil makes further operations on frames to have=20 one-pixel resolution =97 which is the same as what the "in order to set=20 the size of a frame in pixels," tries to convey. =