sources.list(5) says:
> The recommended locations for keyrings are
> /usr/share/keyrings for keyrings managed by packages, and
> /etc/apt/keyrings for keyrings managed by the system operator.
* option to configure PromptInputLine prompt
- Introduces an option to set custom prompt text
- If 'prompt' not passed in parameters, default value of "> " used
* commit: update documentation for PromptInputLine
* Update docs/config/lua/keyassignment/PromptInputLine.md
---------
Co-authored-by: Wez Furlong <wez@wezfurlong.org>
* Add a CloseWithoutClear copy mode key assignment
Closing the copy overlay currently unconditionally clears the viewport,
in particular resetting scroll. For the search overlay, we don't
necessarily want to scroll back to the prompt after finding a match --
indeed, the old search overlay (which didn't use copy mode) had this
behaviour.
Add a CloseWithoutClear key assignment which has this desired behaviour,
and make it the default for ESC in search mode.
* Change CloseWithoutClear into normal Close, and add ResetViewport
* Remove ResetViewport, add helper for keys
The implementation of this is a bit gnarly, because we have
an optional value with a default that *is* populated by the
dynamic config stuff, but that isn't part of the derive(Debug)
impl.
closes: https://github.com/wez/wezterm/issues/5547
Centralize the thread local state management into the selector module
to make it a bit more convenient to consume from the various other
locations.
closes: https://github.com/wez/wezterm/issues/5532
This has more intuitive sorting; eg: `line` used to show the first match
as `linux_endeavour` but now matches `LINEAR B IDEOGRAM VESSEL B212`
first, which feels more relevant (has an exact prefix match).
refs: https://github.com/wez/wezterm/issues/5532
If someone removed the directory structure, or otherwise messed with
the files, there was a good chance that we'd end up in a panic.
This commit improves the error messaging produced by the blob
lease layer to provide the path as context, log the error,
and then translate the error case to an empty frame so that
the rest of the rendering machinery can proceed in a more reasonable
way.
We take care to log this sort of corrupt frame error only once,
as it is most likely to occur in an animated gif and will thus
trigger multiple times per second for such a file.
refs: #5422
