pub struct ClipboardEnabled;Expand description
When true (default), an explicit yank (y, yy, Visual
y) also copies to the system clipboard, and paste of the
unnamed register reads it — the clipboard is the default yank
target. Delete / change / x stay in registers and never touch
the clipboard (the yank-only rule — no incidental clobber).
false = pure registers; only the explicit "+ / "*
registers reach the clipboard.
A plain boolean by deliberate design (clipboard.md §5):
lattice rejects vim’s crude unnamed / unnamedplus string
names in favour of a self-documenting on/off.
Implementations§
Source§impl ClipboardEnabled
impl ClipboardEnabled
Sourcepub fn build_spec() -> Option<bool>
pub fn build_spec() -> Option<bool>
Build the runtime spec for this declaration.
Used by the registry’s self-registration boot
path; not generally called by hand. Direct
construction of Option<T> is the macro’s
internal-only path – consumer code uses
config.get_typed::<#name_ident>() to read
and config.set_typed::<#name_ident>(...) to
write.
Trait Implementations§
Source§impl HasGroup for ClipboardEnabled
impl HasGroup for ClipboardEnabled
Source§const GROUP_NAME: &'static str = <crate::Editor as ::lattice_config::OptionGroup>::NAME
const GROUP_NAME: &'static str = <crate::Editor as ::lattice_config::OptionGroup>::NAME
"editor", "lsp", …). The macro
pulls this from the group = SomeGroup; directive at the
declaration block’s head.Source§impl OptionDecl for ClipboardEnabled
impl OptionDecl for ClipboardEnabled
Source§const NAME: &'static str = ClipboardEnabled
const NAME: &'static str = ClipboardEnabled
:set <NAME>=…,
TOML keys, completion candidates, :describe-option.
Internal access is type-driven. The macro derives this
from the option’s identifier (with namespace prefix when
declared via mode_options!); manually-typed NAMEs are
not supported for built-in options.Source§const DOC: &'static str = ClipboardEnabled
const DOC: &'static str = ClipboardEnabled
:describe-option, the :customize
form’s per-row help, and :apropos results.Source§const CUSTOMIZABLE: bool = true
const CUSTOMIZABLE: bool = true
true (the default) ⇒ option
appears in :set autocomplete + the :customize group
view. false ⇒ plugin / engine-internal state, hidden
from user surfaces. Equivalent of emacs’s defvar vs
defcustom. (See mode-architecture.md §6.5.3.)Source§fn default_value() -> Self::Value
fn default_value() -> Self::Value
const) so non-const-constructible types like String
can be defaults.