Edd Barrett
Edd Barrett
One possible scheme: - the history file is loaded into memory at startup - each shell immediately writes history to the history file AND into to the in-memory copy -...
You could do something like: - At startup, give each shell a "probably unique" ID (say, a random 32/64-bit number) - When writing a history line into the history file,...
A refinement to the above: when an instance writes it's first line of history into the histfile, it could check that no other entry in the file used the same...
Having thought about this more: > For now, I'm considering adding only the first option rather than implementing the both options at once. This would give users most of what...
Do I see it correctly that there's no way to silence these warnings, short of `#![allow(dead_code)]` at the module level?
Is there any harm in unconditionally marking the generated functions `#[allow(dead_code)]`? This would be a simple fix.
> #![allow(dead_code)] hide all dead code in that module. Therefore, I do not recommend using it. Indeed, that's awful. > You may add something like drop(Foo::new().into_bytes()) somewhere in you code....
@chabapok I've raised the PR, but to be honest this repo doesn't appear to be maintained and as a result, I'm reluctant to use it for anything. The tests were...
To be clear, SSL is fine as-is for encryption purposes, but host authentication (proving the server identity) is not impemented. Pushing to v0.3