all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57856@debbugs.gnu.org
Subject: bug#57856: 28.2; bookmark context strings in encrypted files
Date: Fri, 16 Sep 2022 09:30:19 -0300	[thread overview]
Message-ID: <877d23h4df.fsf@gmail.com> (raw)
In-Reply-To: <87mtaz8quf.fsf@gnus.org>

Hi Lars,

Thanks again for the very prompt response.

On Fri, 16 Sep 2022 at 14:07, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Gustavo Barros <gusbrs.2016@gmail.com> writes:
>
>> It could be argued that it is unwise to set a bookmark in this
>> context. But, well, users do all kind of stuff.  Besides, Emacs
>> provides no hint that this may be risky (as far as I can tell).  So 
>> it
>> would be nice if Emacs would be a little more conservative here, and
>> locally set `bookmark-search-size' to 0 in buffers visiting encrypted
>> files.
>
> I think that makes sense.  Alternatively, we could prompt the user for
> what to do in these files?
>
> Anybody have any opinions?

If this were to be left to user discretion, I'd suggest a variable 
rather than a prompt.  What would we ask?  "This file is encrypted. Set 
bookmark, yes or no?"  "Why wouldn't I? Yes."  For the value of 
`bookmark-search-size'?  "What's that? Default. RET"  The general point 
is, how many users should we expect to know "at prompt time" that 
`bookmark.el' stores part of the buffer in the bookmark file and what it 
represents for an encrypted file?

But, to be honest, I'm not even sure if this being optional is 
particularly meaningful.  Do you see any use case where one would 
actually want to store unencrypted context of an encrypted file?

Best regards,
Gustavo.





  reply	other threads:[~2022-09-16 12:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 11:08 bug#57856: 28.2; bookmark context strings in encrypted files Gustavo Barros
2022-09-16 12:07 ` Lars Ingebrigtsen
2022-09-16 12:30   ` Gustavo Barros [this message]
2022-09-16 13:01     ` Lars Ingebrigtsen
2022-09-16 13:18       ` Michael Albinus
2022-09-18 10:19         ` Lars Ingebrigtsen
2022-09-18 10:43           ` Michael Albinus
2022-09-19  7:42             ` Lars Ingebrigtsen
2022-09-19  9:00               ` Michael Albinus
2022-09-19 12:03                 ` Lars Ingebrigtsen
2022-09-19 12:16                   ` Michael Albinus
2022-09-19 12:34                     ` Lars Ingebrigtsen
2022-09-19 13:03                       ` Michael Albinus
2022-09-19 18:44                         ` Lars Ingebrigtsen
2022-09-20 14:49                           ` Michael Albinus
2022-09-20 14:53                             ` Lars Ingebrigtsen
2022-09-20 15:00                               ` Michael Albinus
2022-09-20 15:03                             ` Gustavo Barros
2022-09-20 16:19                               ` Michael Albinus
2022-09-19 11:13               ` Gustavo Barros

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

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

  git send-email \
    --in-reply-to=877d23h4df.fsf@gmail.com \
    --to=gusbrs.2016@gmail.com \
    --cc=57856@debbugs.gnu.org \
    --cc=larsi@gnus.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.