Re: Encryption is not considered a change by the :x command

I knew I forgot something :)

So the OS is Debian 10 (Buster), VIm 8.1(18 May 2018, compiled 15 Jun 2019 16:41:15), +cryptv.

On Saturday, May 9, 2020 at 7:10:17 AM UTC+3, Tony Mechelynck wrote:

On Sat, May 9, 2020 at 5:39 AM Ninu-Ciprian Marginean
<ninu.cipri...@gmail.com> wrote:
>
> When we look at the quickref documentation we find:
>
> :xit    :x[it][!] [file]      like ":wq" but write only when changes have
>                                    been made
>
> If we open an existing file and we do not do any changes except for changing the encryption key(with the ":X" command) and then use the ":x" command to exit, the changes to the encryption key will not be applied. Note that the ":X" is not mandatory to be used, the behavior is the same even if we use ":set key=value". By changing the encryption key I mean all 3 scenarios(1 - file is not encrypted to file is encrypted; 2 - file is encrypted to file is encrypted, but with a different key; 3 - file is encrypted to file is not encrypted), since a key with an empty value means the file is not encrypted.
>
> Note that ":wq" does change the encryption.
>
> Is this a bug? Is it intended? Anyways, I just wanted to leave this here for people to know the workaround. If it's a bug, I'm willing to report one on github.

If it's a bug (I'm not sure) most developers read this mailing list too anyway.

Which Vim version? (The latest and greatest is 8.2.717 as of this
writing.) Which OS? When you type :version (in Normal mode and
followed by Enter) does it say +cryptv or -cryptv? (I would expect +
but it _is_ possible to compile Vim without encryption support) I
think there has been something of that kind but it was already quite
some time ago; but anyway, when reporting a problem (with _any_
software, not just Vim) it is always better to report which version of
the software has the problem, on which OS, and which relevant
serttings are enabled.

It is not clear to me whether it is intended or not that after setting
or changing the encryption key but making no other change, the file is
not considered 'modified'. I suppose that if you want to set or change
the key but make no other change (yet) in the file you should write it
immediately (possibly with :wq followed by :bw to make sure that none
of that file's text remains in memory).

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/320201f3-92c7-4605-96e3-07dfea306a9f%40googlegroups.com.