From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kelly Dean Newsgroups: gmane.emacs.devel Subject: Re: Correspondence between web-pages and Info-pages Date: Thu, 01 Jan 2015 04:24:35 +0000 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1420086385 22720 80.91.229.3 (1 Jan 2015 04:26:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Jan 2015 04:26:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 01 05:26:18 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Y6XKz-0006AI-KK for ged-emacs-devel@m.gmane.org; Thu, 01 Jan 2015 05:26:17 +0100 Original-Received: from localhost ([::1]:41984 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y6XKy-0005T2-T9 for ged-emacs-devel@m.gmane.org; Wed, 31 Dec 2014 23:26:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42918) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y6XKm-0005Sj-N1 for emacs-devel@gnu.org; Wed, 31 Dec 2014 23:26:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y6XKi-0000fj-N5 for emacs-devel@gnu.org; Wed, 31 Dec 2014 23:26:04 -0500 Original-Received: from relay6-d.mail.gandi.net ([2001:4b98:c:538::198]:50976) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y6XKi-0000fd-H7 for emacs-devel@gnu.org; Wed, 31 Dec 2014 23:26:00 -0500 Original-Received: from mfilter3-d.gandi.net (mfilter3-d.gandi.net [217.70.178.133]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id D2589FB887; Thu, 1 Jan 2015 05:25:59 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter3-d.gandi.net Original-Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter3-d.gandi.net (mfilter3-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id ZV6F-Lh0CZZV; Thu, 1 Jan 2015 05:25:58 +0100 (CET) X-Originating-IP: 162.248.99.114 Original-Received: from localhost (114-99-248-162-static.reverse.queryfoundry.net [162.248.99.114]) (Authenticated sender: kelly@prtime.org) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id C74ACFB86E; Thu, 1 Jan 2015 05:25:56 +0100 (CET) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4b98:c:538::198 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:180915 Archived-At: Stefan Monnier wrote: >> Don't overlook two important parts of this: using the same name both for >> user input and for display, > > That's good, yes, but is a UI issue which can be fixed regardless of > Info-vs-HTML-vs-whateverelse and regardless of which kind of names > we use. > > IOW it's unrelated to the discussion at hand. But I wasn't responding to the main discussion (of whether to replace Info). I just responded to the side discussion (for which you created a new subject line) of the names/syntax used for the UI for Info. >> and using different names for different formats >> of a page (Info vs. HTML). > > No: I specifically don't want to use different names for different formats. > Instead I want to use a single name that works both in your web-browser > and in Emacs, and that gives the best experience possible in both cases > (i.e. in a web-browser it needs to be HTML, and inside Emacs it would > have to be Info for now and maybe some HTML-Info in some future). But in my original message, I proposed a solution that provides exactly what you're asking for (a single name that works in both web browsers and Info browsers), by using redirects to the HTML or Info page (each of which has its own name). I explained how it would work, and I think it covers all the issues raised in this subthread about how these names should work.