Editing .asc file through scp about vim-gnupg

[jamessan]

The problem here is that NetRW handles the file retrieval from the remote system and populating Vim's buffer with the contents of the file. Once it has done that, it sets the buffer's "filename" to a special name (e.g., scp://host/path/to/file) and that's the file that vim-gnupg sees when it gets a chance to run. Obviously, this isn't something that gnupg can access, so it fails to do anything useful with that filename.

NetRW doesn't provide any hooks to allow plugins like vim-gnupg to be part of the process, so I don't think there's really much that I can do. You're better off just transferring the file locally and doing the edit or using something like sshfs, although that has its own issues.

[noteed]

Thank you.

Syntax highlighting plugins seem to inspect, say, the shabang line to discover the language a file is written in when the extension is missing. Couldn't vim-gnupg do something similar ?

[jamessan]

The problem isn't that vim-gnupg doesn't know it needs to run. The plugin is trying to do its job, but there's isn't a local file for it to work with, nor a way to ensure that its BufReadCmd/BufWriteCmd autocommands and NetRW's autocommands are called in the proper order.

Basically, NetRW would need to define an API where other plugins could register themselves as a filter for NetRW's read/write commands. Currently, NetRW hardcodes its own set of filters instead of providing a way for any plugin to hook into the process.

[noteed]

Ok, thank you again for your answer.