From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#32473: Broken menu entry in manual, section 4.1 Date: Tue, 21 Aug 2018 23:35:37 +0200 Message-ID: <87tvnnl7x2.fsf@gnu.org> References: <3168413.eluxrC5Pv8@aleksandar-ixtreme-m5740> <87k1olfiek.fsf@gnu.org> <3105889.ghd2rdMcOe@aleksandar-ixtreme-m5740> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53770) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsEOf-00033p-7K for bug-guix@gnu.org; Tue, 21 Aug 2018 17:41:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fsEOd-0003QN-Em for bug-guix@gnu.org; Tue, 21 Aug 2018 17:41:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:52097) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fsEOb-0003Pu-TR for bug-guix@gnu.org; Tue, 21 Aug 2018 17:41:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fsEOb-00061P-QY for bug-guix@gnu.org; Tue, 21 Aug 2018 17:41:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsENu-0000kA-69 for bug-guix@gnu.org; Tue, 21 Aug 2018 17:40:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fsEJO-0007IQ-KD for bug-guix@gnu.org; Tue, 21 Aug 2018 17:35:39 -0400 In-Reply-To: <3105889.ghd2rdMcOe@aleksandar-ixtreme-m5740> (HiPhish's message of "Tue, 21 Aug 2018 12:56:40 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: HiPhish Cc: 32473@debbugs.gnu.org HiPhish skribis: > On Montag, 20. August 2018 12:21:07 CEST you wrote: >> > The standalone Info reader tolerates it, but not the Info.vim reader, >> > which >> > considers the space to be part of the target node name. Neither the >> > Texinfo >> > manual (section 4.9) nor the Info manual seem to allow for this extra >> > space, so it looks like a bug in the manual to me. >>=20 >> Would it make sense for Info.vim to be bug-compatible? > > I considered that, but I don't think it's a good idea: it's better to fix= a=20 > bug (when feasible of course) than to sweep it under the rug with some ha= ck.=20 > If the bug is fixed, it's fixed for everyone, if I make Info.vim bug- > compatible I make my reader harder to maintain and that bug still persist= s and=20 > will eventually bite someone when they want to implement their own Info=20 > reader. Yes, that makes a lot of sense to me. Thanks for your feedback! Ludo=E2=80=99.