From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: on hyperlinks (bookmarks) Date: Sun, 8 Nov 2020 23:26:47 +0300 Message-ID: References: <20201106091525.mzkxrssm7o43jvff@E15-2016.optimum.net> <20201108093604.rb3lpyqw4mvmwtdt@E15-2016.optimum.net> <20201108124020.jmxb4luvq6fot7xg@E15-2016.optimum.net> <6d8882a5-23aa-4fab-b222-30928dc17eb9@default> <63ff3d93-1a2d-40f0-9577-826e1dac0337@default> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12541"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: Emacs-Devel List , Boruch Baum , Arthur Miller , Stefan Monnier To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 08 22:51:20 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 1kbsal-000399-QX for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Nov 2020 22:51:19 +0100 Original-Received: from localhost ([::1]:44640 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kbsak-0008LS-TJ for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Nov 2020 16:51:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33926) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbsZW-0007RL-6L for emacs-devel@gnu.org; Sun, 08 Nov 2020 16:50:02 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:55519) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbsZU-0007Jt-9B for emacs-devel@gnu.org; Sun, 08 Nov 2020 16:50:01 -0500 Original-Received: from localhost ([::ffff:197.157.34.177]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C000C.000000005FA867E3.00007413; Sun, 08 Nov 2020 21:49:22 +0000 Content-Disposition: inline In-Reply-To: <63ff3d93-1a2d-40f0-9577-826e1dac0337@default> Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/08 16:49:27 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:258929 Archived-At: * Drew Adams [2020-11-08 22:50]: > > > main characteristics of Emacs bookmarks are these, IMO: > > > > > > 1. They're persistent. > > > (They don't have to be, but they can be.) > > > > Yes, they are. Only they are designed for single users, not for > > collaborative sharing. > > I can't speak to the general topic of collaborative > sharing, but a bookmark file can of course be shared, > just as any other file can be. And you can access a > bookmark file as a remote file. And I imagine that a > bookmark file could be accessible from, say, a > repository URL, etc. > > Again, I'm no expert on such things - I don't use > them, myself. But there's nothing special about a > bookmark file, compared to other plain-text files. > > I guess I'm saying that I don't think Emacs bookmarks > are particularly "designed for (only) single users". > Unless one thinks that files, in general, are so > designed. I have not expressed myself correctly. I wanted to say that Emacs could provide central sharing feautres. Example could be when there would be a bookmark file to which all users on same system could write and read from it. That would be analogous to site-lisp directory. If I remember well back in time games scores were centrally shared with other users. I may be wrong. Similar fashion could be used for various packages to create the collective data or useful information for a group without thinking how to share those files, transfer, etc. In other words that leads to database backed systems that were well designed for collective collaboration. But if two users can write to same bookmark file that is one solution. > > `eww' lacks function to bookmark specific page on specific line. I can > > of course add eww bookmark with `w' but that does not reference > > specific line or specific search on the page. > > The EWW bookmarks created with Bookmark+ record a > URL, which can include an anchor - e.g., a location > within an HTML page. Is there really a notion of > "lines" and line numbers in a displayed web page? > If so, if you can record it then it can be added to > what's recorded in an EWW bookmark. That is good, I will research it. > > If there are no #names it becomes impossible for many browsers to > > obtain finely grained reference or back link. For `eww' it would be > > relatively easy to do that feature and include it in {C-x r m RET} to > > be bookmarked by Emacs system, not eww system. > > If you're talking about adding support for #name, > that's already present (with Bookmark+). If you > mean add, in some way, support for addressing a > particular line of a web page, I don't know how > that would be easy to do (but I'm no expert on > such things). I think that eww now does support moving to #names but recently, like maybe some months ago did not. I see it supports here.