Add "rev" detail to default view of keys#246
Conversation
orhun
left a comment
There was a problem hiding this comment.
Maybe instead of adding (rev) to the beginning of the entries, we can change the style for preserving the alignment.
| @@ -1,8 +1,11 @@ | |||
| use clap::ValueEnum; | |||
| use core::panic; | |||
There was a problem hiding this comment.
No need to import stuff from core.
There was a problem hiding this comment.
Ignore this, I was using panic for dumb testing. How can I enable tracing logging to STDOUT btw?
There was a problem hiding this comment.
RUST_LOG=trace cargo r doesn't help as the TUI takes over STDOUT
There was a problem hiding this comment.
There is a logging widget in the TUI: https://github.com/orhun/gpg-tui?tab=readme-ov-file#show-logs
You can also save logs to a file.
Any suggestions on changing the style? This is better as it means the tests will have far less breakage (we won't need to revise it) |
|
Maybe the revoked/invalid/etc keys can be gray or italic, indicating that they are not available. What do you think? |
|
That's a good idea!! |
Description
Brief POC wip to learn the internals and add "rev" detail to the top level view of keys
Motivation and Context
This helps to quickly visualise what has and has not been revoked. Ideally I plan to add a default filtering option to hide revoked keys,
How Has This Been Tested?
Manually, tests need updating.
Output (if appropriate):
You should see
(rev)at the top-level view of keys.Types of changes
Checklist:
Outstanding tasks: