agevault uses age, allegedly very secure (aiming to replace pgp/gpg). Comparing it with gocryptfs, from the user perspective, agevault seems simpler, though CLI *exclusive*. As the repository states, "Like age, it features no config options, allowing for a straightforward secure flow". It would also run in all major OS platforms out of the box.But
agevault is also very new. Though age has been around for a while now, I don't see an "audited" link (neither on agevault, nor age).
agevault uses age, allegedly very secure (aiming to replace pgp/gpg). Comparing it with gocryptfs, from the user perspective, agevault seems simpler, though CLI *exclusive*. As the repository states, "Like age, it features no config options, allowing for a straightforward secure flow". It would also run in all major OS platforms out of the box.But
agevault is also very new. Though age has been around for a while now, I don't see an "audited" link (neither on agevault, nor age).
> “The main question is, does it disappear during this re-entry?” says Löhle. “Is everything evaporating, or are there pieces that eventually impact on the ground?”
>
> He expects some parts, such as the satellite’s fuel tanks, to survive. “You could learn from the re-entry that if you build a fuel tank differently, it can break up,” he says.
Archived article at: https://archive.ph/WdUvx
> “The main question is, does it disappear during this re-entry?” says Löhle. “Is everything evaporating, or are there pieces that eventually impact on the ground?”
>
> He expects some parts, such as the satellite’s fuel tanks, to survive. “You could learn from the re-entry that if you build a fuel tank differently, it can break up,” he says.
Archived article at: https://archive.ph/WdUvx
README!
README!
fetch-context branch? It works great!
fetch-context branch? It works great!
set uncollapse_new = yes # open threads when new mail
set uncollapse_jump = yes # jump to unread message when uncollapse
set collapse_unread = no # don't collapse threads with unread mails
Let's see how it goes.
set uncollapse_new = yes # open threads when new mail
set uncollapse_jump = yes # jump to unread message when uncollapse
set collapse_unread = no # don't collapse threads with unread mails
Let's see how it goes.
mutt/neomutt users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
mutt/neomutt users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
vi/vim. I think nano has spoiled me too much. LOL.
vi/vim. I think nano has spoiled me too much. LOL.
au BufNewFile,BufRead jenny-posting.eml setl completefunc=jenny#CompleteMentions fo-=t wrap, from jenny. How would I go to incorporate that there?
au BufNewFile,BufRead jenny-posting.eml setl completefunc=jenny#CompleteMentions fo-=t wrap, from jenny. How would I go to incorporate that there?
startinsert set on my .vimrc, so I will either have to take it out, or exit insert, $, then insert again. I think the way you do it would be the way to go.I tried setting
VISUAL to be something like vim -c 'star!', which does the same thing, but no dice. :-/
startinsert set on my .vimrc, so I will either have to take it out, or exit insert, $, then insert again. I think the way you do it would be the way to go.I tried setting
VISUAL to be something like vim -c 'star!', which does the same thing, but no dice. :-/
vim cursor at the end of the first line on replies, and forks. I have tried adding to this to jenny's configuration:
"editor": "vim \\"+normal $\\"",
But that doesn't work. How would you go about it?
vim cursor at the end of the first line on replies, and forks. I have tried adding to this to jenny's configuration:
"editor": "vim \"+normal $\"",
But that doesn't work. How would you go about it?
D then ~f sender). :-) Phew!
D then ~f sender). :-) Phew!
.tmux.conf that makes it very easy to use the multiplexer, but I agree, Zellij seems pretty robust, and intuitive. I like it! Tried compiling it, as with everything Rust, it failed miserably. Good thing there is a binary release I could download to try!
> A glint in his eye, a sly, Ferengi grin,
> Quark crossed the promenade, a curious thing within.
> No jeweled trinket, no weapon so grand,
> But a simple pail held tight in his hand.
>
> Odo, the Constable, with a brow raised high,
> "A bucket, Quark? What trickery do you try?"
> The Ferengi huckster, with a salesman's flair,
> "A gift, my friend, a constable's rare!"
>
> "For those late-night spills, a morphing mishap,
> This bucket, dear Odo, will catch every scrap.
> And should a suspect turn to goop and flee,
> This pail's the answer, a guarantor, you see!"
>
> Odo's lips twitched, a hint of a smile,
> At Quark's twisted logic, his mercantile style.
> "Perhaps," he conceded, the bucket held tight,
> "A useful addition, in the pursuit of right."
>
> So Quark made his sale, with a wink and a nod,
> A bucket for Odo, a Ferengi oddity, odd.
> But on Deep Space Nine, where chaos takes hold,
> Even a pail can be worth more than gold.
About the account, thanks, but I already have way too many. :-D
> A string of letters, a forgotten name,
> An email crafted, a message to claim.
> We hit send with a click, a hopeful sigh,
> But a bounce-back arrives, a tear in our eye.
>
> "Delivery failed," the message reads cold,
> The address it seems, is a story untold.
> A ghost in the system, a memory's trace,
> Lost in the void of cyberspace.
:-D