unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Emacs-Devel List <emacs-devel@gnu.org>
Subject: eww and bookmarks
Date: Wed, 27 May 2020 03:18:50 -0400	[thread overview]
Message-ID: <20200527071850.rgaqnelquirmuzyx@E15-2016.optimum.net> (raw)

For tinfoil-hat reasons, I'm hesitant about the idea of having a single
bookmark list for both local and network resources, and both emacs and
non-emacs launching. I don't want a situation where there might be
uncertainty which program is about to be launched or whether the network
is going to accessed and what follow-on 'stuff' my device will end up
doing.

That doesn't mean I oppose the notion of a single 'grand unified'
bookmark list, just that I would want some clear indication in advance
of what is about to happen should I open any specific link.

Maybe what would be sufficient for those concerns would be a pair of
visual cues: one for 'local/network', and a second for 'emacs/external'.
Then an interested user could query a bookmark's details for further
information, or just click-through. The visual cues might not even need
to take up additional screen space: maybe it would be sufficient to
underline network bookmarks, and to italicize bookmarks that launch
external programs.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



             reply	other threads:[~2020-05-27  7:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  7:18 Boruch Baum [this message]
2020-05-27 14:40 ` eww and bookmarks Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2020-05-20 11:48 Matthias Meulien
2020-05-20 16:29 ` Drew Adams
2020-05-20 16:35   ` Noam Postavsky
2020-05-20 16:40     ` Drew Adams
2020-05-20 20:13     ` Matthias Meulien
2020-05-23 22:56       ` Michael Heerdegen
2020-05-24  8:44         ` Matthias Meulien
2020-05-24 14:14           ` Alfred M. Szmidt
2020-05-24 19:06             ` Karl Fogel
2020-05-25  4:35             ` Michael Heerdegen
2020-05-25  5:26               ` Alfred M. Szmidt
2020-05-26  2:17                 ` Michael Heerdegen
2020-06-10 15:39                   ` Lars Ingebrigtsen
2020-06-10 20:03                     ` Drew Adams
2020-05-25 12:51               ` Stefan Monnier
2020-05-25 13:52                 ` Marcin Borkowski
2020-05-25 15:03                 ` Alfred M. Szmidt
2020-05-25 15:24                   ` Stefan Monnier
2020-05-25 23:40                   ` Michael Heerdegen
     [not found]                 ` <e23432dd-212b-4bf0-8e8c-185988c653f0@default>
2020-05-26  1:04                   ` Michael Heerdegen
2020-05-27  5:10                     ` Drew Adams
2020-05-25  4:28           ` Michael Heerdegen
2020-05-25 14:35             ` T.V Raman
2020-05-20 22:14     ` Michael Heerdegen
2020-06-07 15:09       ` Michael Heerdegen
2020-06-07 15:30         ` Basil L. Contovounesios
2020-06-07 16:13           ` Michael Heerdegen
2020-06-07 16:36             ` Tomas Hlavaty
2020-06-07 18:23             ` Basil L. Contovounesios
2020-06-08 14:49               ` Michael Heerdegen
2020-06-08 16:54                 ` Basil L. Contovounesios
2020-06-10 12:01                   ` Michael Heerdegen
2020-06-07 16:36           ` Lars Ingebrigtsen
2020-06-07 18:23             ` Basil L. Contovounesios
2020-06-08 14:42           ` Michael Heerdegen
2020-06-08 16:58             ` Basil L. Contovounesios
2020-06-10 12:06               ` Michael Heerdegen
2020-10-26 18:15                 ` Adam Porter
2020-10-26 18:33                   ` Drew Adams
2020-10-26 18:43                   ` Lars Ingebrigtsen
2020-10-26 19:05                     ` Adam Porter
2020-10-26 19:26                   ` Karl Fogel
2020-06-07 16:31         ` Clément Pit-Claudel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200527071850.rgaqnelquirmuzyx@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).