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: How to make Emacs popular again. Date: Sat, 10 Oct 2020 10:52:01 +0300 Message-ID: <83a6wu5xi6.fsf@gnu.org> References: <835z7vjrg3.fsf@gnu.org> <83tuvegkmo.fsf@gnu.org> <83tuvdf6kf.fsf@gnu.org> <20201002161307.GK3520@protected.rcdrun.com> <83o8lkeh3o.fsf@gnu.org> <20201002163308.GM3520@protected.rcdrun.com> <83eemfepnq.fsf@gnu.org> <831riefnwq.fsf@gnu.org> <87blhalf0r.fsf@logand.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24449"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Tomas Hlavaty Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 10 09:52:35 2020 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 1kR9g9-0006Ed-Tt for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 09:52:33 +0200 Original-Received: from localhost ([::1]:49800 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kR9g8-0002L8-TG for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Oct 2020 03:52:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39800) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kR9ff-0001vy-Hk for emacs-devel@gnu.org; Sat, 10 Oct 2020 03:52:04 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33910) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kR9fe-00067h-O6; Sat, 10 Oct 2020 03:52:02 -0400 Original-Received: from [176.228.60.248] (port=2006 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kR9fe-0002RV-43; Sat, 10 Oct 2020 03:52:02 -0400 In-Reply-To: <87blhalf0r.fsf@logand.com> (message from Tomas Hlavaty on Sat, 10 Oct 2020 09:24:36 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:257306 Archived-At: > From: Tomas Hlavaty > Date: Sat, 10 Oct 2020 09:24:36 +0200 > > >> My point is that this should work even if you don't have > >> a network connection, provided you have a local copy > >> of Wiktionary. > > > > EWW is not the solution for that use case. > > It is not obvious to me why. Because for that EWW will need to be taught the relevant protocol, wouldn't it? Try this: M-x eww RET dict://dict.org RET What do you get? > For example, I've been using eww with off-line Common Lisp HyperSpec and > it works well. A key bound to hyperspec-lookup function will simply > open relevant local html file. EWW does support file:// URLs, that's why showing human-readable files works. But that doesn't mean it knows about any URL scheme out there, it only knows about the ones we taught it. A dictionary file is not just a human-readable text file, so inserting its contents in a buffer is not enough to find a word in a dictionary and show its definition. You need to write the code which uncompresses the dictionary, looks up the definition, and displays it. And once you wrote that code, why use EWW at all for showing word definitions, instead of having a command that just visits the dictionary file and does that processing? IOW, EWW is a handy tool for retrieving content using known URL schemes. It makes no sense to me to teach it about a "scheme" that accesses a local file which needs special processing, because EWW will not help us do the job, and it is much simpler to just read that file into a buffer directly.