pub struct Message<'a>(/* private fields */);Expand description
Streams an OpenPGP message.
Wraps an io::Writer for use with the streaming subsystem. The
Message is a stack of filters that create the desired message
structure. Literal data must be framed using the
LiteralWriter filter. Once all the has been written, the
Message must be finalized using Message::finalize.
Implementations§
Source§impl<'a> Message<'a>
impl<'a> Message<'a>
Sourcepub fn new<W>(w: W) -> Message<'a> ⓘ
pub fn new<W>(w: W) -> Message<'a> ⓘ
Starts streaming an OpenPGP message.
§Examples
use sequoia_openpgp as openpgp;
use openpgp::serialize::stream::{Message, LiteralWriter};
let message = Message::new(&mut sink);
// Construct the writer stack here.
let mut message = LiteralWriter::new(message).build()?;
// Write literal data to `message` here.
// ...
// Finalize the message.
message.finalize()?;Sourcepub fn finalize_one(self) -> Result<Option<Message<'a>>, Error>
pub fn finalize_one(self) -> Result<Option<Message<'a>>, Error>
Finalizes the topmost writer, returning the underlying writer.
Finalizes the topmost writer, i.e. flushes any buffered data, and pops it of the stack. This allows for fine-grained control of the resulting message, but must be done with great care. If done improperly, the resulting message may be malformed.
§Examples
This demonstrates how to create a compressed, signed message from a detached signature.
use std::io::Write;
use std::convert::TryFrom;
use sequoia_openpgp as openpgp;
use openpgp::packet::{Packet, Signature, one_pass_sig::OnePassSig3};
use openpgp::serialize::Serialize;
use openpgp::serialize::stream::{Message, Compressor, LiteralWriter};
let data: &[u8] = // ...
let sig: Signature = // ...
let message = Message::new(&mut sink);
let mut message = Compressor::new(message).build()?;
// First, write a one-pass-signature packet.
Packet::from(OnePassSig3::try_from(&sig)?)
.serialize(&mut message)?;
// Then, add the literal data.
let mut message = LiteralWriter::new(message).build()?;
message.write_all(data)?;
// Finally, pop the `LiteralWriter` off the stack to write the
// signature.
let mut message = message.finalize_one()?.unwrap();
Packet::from(sig).serialize(&mut message)?;
// Finalize the message.
message.finalize()?;Sourcepub fn finalize(self) -> Result<(), Error>
pub fn finalize(self) -> Result<(), Error>
Finalizes the message.
Finalizes all writers on the stack, flushing any buffered data.
§Note
Failing to finalize the message may result in corrupted messages.
§Examples
use sequoia_openpgp as openpgp;
use openpgp::serialize::stream::{Message, LiteralWriter};
let message = Message::new(&mut sink);
// Construct the writer stack here.
let mut message = LiteralWriter::new(message).build()?;
// Write literal data to `message` here.
// ...
// Finalize the message.
message.finalize()?;Trait Implementations§
Source§impl<'a> Write for Message<'a>
impl<'a> Write for Message<'a>
Source§fn write(&mut self, buf: &[u8]) -> Result<usize, Error>
fn write(&mut self, buf: &[u8]) -> Result<usize, Error>
Source§fn flush(&mut self) -> Result<(), Error>
fn flush(&mut self) -> Result<(), Error>
Source§fn is_write_vectored(&self) -> bool
fn is_write_vectored(&self) -> bool
can_vector)1.0.0 · Source§fn write_all(&mut self, buf: &[u8]) -> Result<(), Error>
fn write_all(&mut self, buf: &[u8]) -> Result<(), Error>
Source§fn write_all_vectored(&mut self, bufs: &mut [IoSlice<'_>]) -> Result<(), Error>
fn write_all_vectored(&mut self, bufs: &mut [IoSlice<'_>]) -> Result<(), Error>
write_all_vectored)Auto Trait Implementations§
impl<'a> !RefUnwindSafe for Message<'a>
impl<'a> !UnwindSafe for Message<'a>
impl<'a> Freeze for Message<'a>
impl<'a> Send for Message<'a>
impl<'a> Sync for Message<'a>
impl<'a> Unpin for Message<'a>
impl<'a> UnsafeUnpin for Message<'a>
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<W> ElfWrite for W
impl<W> ElfWrite for W
Source§fn write_word(
&mut self,
class: Class,
byte_order: ByteOrder,
value: u64,
) -> Result<(), Error>
fn write_word( &mut self, class: Class, byte_order: ByteOrder, value: u64, ) -> Result<(), Error>
Source§fn write_word_as_u32(
&mut self,
class: Class,
byte_order: ByteOrder,
value: u32,
) -> Result<(), Error>
fn write_word_as_u32( &mut self, class: Class, byte_order: ByteOrder, value: u32, ) -> Result<(), Error>
value.Source§impl<T> ExecutableCommand for T
impl<T> ExecutableCommand for T
Source§fn execute(&mut self, command: impl Command) -> Result<&mut T, Error>
fn execute(&mut self, command: impl Command) -> Result<&mut T, Error>
Executes the given command directly.
The given command its ANSI escape code will be written and flushed onto Self.
§Arguments
-
The command that you want to execute directly.
§Example
use std::io;
use crossterm::{ExecutableCommand, style::Print};
fn main() -> io::Result<()> {
// will be executed directly
io::stdout()
.execute(Print("sum:\n".to_string()))?
.execute(Print(format!("1 + 1= {} ", 1 + 1)))?;
Ok(())
// ==== Output ====
// sum:
// 1 + 1 = 2
}Have a look over at the Command API for more details.
§Notes
- In the case of UNIX and Windows 10, ANSI codes are written to the given ‘writer’.
- In case of Windows versions lower than 10, a direct WinAPI call will be made.
The reason for this is that Windows versions lower than 10 do not support ANSI codes,
and can therefore not be written to the given
writer. Therefore, there is no difference between execute and queue for those old Windows versions.
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self> ⓘ
fn instrument(self, span: Span) -> Instrumented<Self> ⓘ
Source§fn in_current_span(self) -> Instrumented<Self> ⓘ
fn in_current_span(self) -> Instrumented<Self> ⓘ
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self> ⓘ
fn into_either(self, into_left: bool) -> Either<Self, Self> ⓘ
self into a Left variant of Either<Self, Self>
if into_left is true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self> ⓘ
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self> ⓘ
self into a Left variant of Either<Self, Self>
if into_left(&self) returns true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreimpl<T> MaybeSend for T
impl<T> MaybeSync for T
Source§impl<T> Pointable for T
impl<T> Pointable for T
Source§impl<T> PolicyExt for Twhere
T: ?Sized,
impl<T> PolicyExt for Twhere
T: ?Sized,
Source§impl<T> QueueableCommand for T
impl<T> QueueableCommand for T
Source§fn queue(&mut self, command: impl Command) -> Result<&mut T, Error>
fn queue(&mut self, command: impl Command) -> Result<&mut T, Error>
Queues the given command for further execution.
Queued commands will be executed in the following cases:
- When
flushis called manually on the given type implementingio::Write. - The terminal will
flushautomatically if the buffer is full. - Each line is flushed in case of
stdout, because it is line buffered.
§Arguments
-
The command that you want to queue for later execution.
§Examples
use std::io::{self, Write};
use crossterm::{QueueableCommand, style::Print};
fn main() -> io::Result<()> {
let mut stdout = io::stdout();
// `Print` will executed executed when `flush` is called.
stdout
.queue(Print("foo 1\n".to_string()))?
.queue(Print("foo 2".to_string()))?;
// some other code (no execution happening here) ...
// when calling `flush` on `stdout`, all commands will be written to the stdout and therefore executed.
stdout.flush()?;
Ok(())
// ==== Output ====
// foo 1
// foo 2
}Have a look over at the Command API for more details.
§Notes
- In the case of UNIX and Windows 10, ANSI codes are written to the given ‘writer’.
- In case of Windows versions lower than 10, a direct WinAPI call will be made.
The reason for this is that Windows versions lower than 10 do not support ANSI codes,
and can therefore not be written to the given
writer. Therefore, there is no difference between execute and queue for those old Windows versions.
Source§impl<W> SynchronizedUpdate for W
impl<W> SynchronizedUpdate for W
Source§fn sync_update<T>(
&mut self,
operations: impl FnOnce(&mut W) -> T,
) -> Result<T, Error>
fn sync_update<T>( &mut self, operations: impl FnOnce(&mut W) -> T, ) -> Result<T, Error>
Performs a set of actions within a synchronous update.
Updates will be suspended in the terminal, the function will be executed against self, updates will be resumed, and a flush will be performed.
§Arguments
-
Function
A function that performs the operations that must execute in a synchronized update.
§Examples
use std::io;
use crossterm::{ExecutableCommand, SynchronizedUpdate, style::Print};
fn main() -> io::Result<()> {
let mut stdout = io::stdout();
stdout.sync_update(|stdout| {
stdout.execute(Print("foo 1\n".to_string()))?;
stdout.execute(Print("foo 2".to_string()))?;
// The effects of the print command will not be present in the terminal
// buffer, but not visible in the terminal.
std::io::Result::Ok(())
})?;
// The effects of the commands will be visible.
Ok(())
// ==== Output ====
// foo 1
// foo 2
}§Notes
This command is performed only using ANSI codes, and will do nothing on terminals that do not support ANSI codes, or this specific extension.
When rendering the screen of the terminal, the Emulator usually iterates through each visible grid cell and renders its current state. With applications updating the screen a at higher frequency this can cause tearing.
This mode attempts to mitigate that.
When the synchronization mode is enabled following render calls will keep rendering the last rendered state. The terminal Emulator keeps processing incoming text and sequences. When the synchronized update mode is disabled again the renderer may fetch the latest screen buffer state again, effectively avoiding the tearing effect by unintentionally rendering in the middle a of an application screen update.