1
0
mirror of https://github.com/romkatv/powerlevel10k.git synced 2024-12-12 19:18:28 +02:00

unfuckup md formatting

This commit is contained in:
romkatv 2020-04-06 19:52:13 +02:00
parent fb117b5f97
commit da58ccbbaf

View File

@ -1,58 +1,112 @@
battery: use the same technique as in vpn_ip to avoid reset=2. battery: use the same technique as in vpn_ip to avoid reset=2.
--- ---
implement fake gitstatus api on top of vcs_info (or plain git?) + worker and use it if there is no implement fake gitstatus api on top of vcs_info (or plain git?) + worker and use it if there is no
gitstatus. gitstatus.
--- ---
- call vcs_info on worker. the tricky question is what to display while "loading". - call vcs_info on worker. the tricky question is what to display while "loading".
--- ---
- add _SHOW_SYSTEM to all *env segments. - add _SHOW_SYSTEM to all *env segments.
--- ---
- support states in SHOW_ON_COMMAND: POWERLEVEL9K_SEGMENT_STATE_SHOW_ON_COMMAND='...' - support states in SHOW_ON_COMMAND: POWERLEVEL9K_SEGMENT_STATE_SHOW_ON_COMMAND='...'
--- ---
add POWERLEVEL9K_${SEGMENT}_${STATE}_SHOW_IN_DIR='pwd_pattern'; implement the same way as add POWERLEVEL9K_${SEGMENT}_${STATE}_SHOW_IN_DIR='pwd_pattern'; implement the same way as
SHOW_ON_UPGLOB. how should it interact with POWERLEVEL9K_${SEGMENT}_DISABLED_DIR_PATTERN? SHOW_ON_UPGLOB. how should it interact with POWERLEVEL9K_${SEGMENT}_DISABLED_DIR_PATTERN?
--- ---
add `p10k upglob`; returns 0 on match and sets REPLY to the directory where match was found. add `p10k upglob`; returns 0 on match and sets REPLY to the directory where match was found.
--- ---
when directory cannot be shortened any further, start chopping off segments from the left and when directory cannot be shortened any further, start chopping off segments from the left and
replacing the chopped off part with `…`. e.g., `…/x/anchor/y/anchor`. the shortest dir replacing the chopped off part with `…`. e.g., `…/x/anchor/y/anchor`. the shortest dir
representation is thus `…/last` or `…/last` depending on whether the last segment is an anchor. representation is thus `…/last` or `…/last` depending on whether the last segment is an anchor.
the replacement parameter's value is `…/` (with a slash) to allow for `x/anchor/y/anchor`. the replacement parameter's value is `…/` (with a slash) to allow for `x/anchor/y/anchor`.
--- ---
- add to faq: how do i display an environment variable in prompt? link it from "extensible" - add to faq: how do i display an environment variable in prompt? link it from "extensible"
--- ---
- add to faq: how do i display an icon in prompt? link it from "extensible" - add to faq: how do i display an icon in prompt? link it from "extensible"
--- ---
- add root_indicator to config templates - add root_indicator to config templates
--- ---
- test chruby and add it to config templates - test chruby and add it to config templates
--- ---
- add ssh to config templates - add ssh to config templates
--- ---
- add swift version to config templates; see if there is a good pattern for PROJECT_ONLY - add swift version to config templates; see if there is a good pattern for PROJECT_ONLY
--- ---
- add swiftenv - add swiftenv
--- ---
- add faq: how to customize directory shortening? mention POWERLEVEL9K_DIR_TRUNCATE_BEFORE_MARKER, - add faq: how to customize directory shortening? mention POWERLEVEL9K_DIR_TRUNCATE_BEFORE_MARKER,
POWERLEVEL9K_DIR_MAX_LENGTH and co., and truncate_to_last. POWERLEVEL9K_DIR_MAX_LENGTH and co., and truncate_to_last.
--- ---
fix a bug in zsh: https://github.com/romkatv/powerlevel10k/issues/502. to reproduce: fix a bug in zsh: https://github.com/romkatv/powerlevel10k/issues/502. to reproduce:
```zsh ```zsh
emulate zsh -o prompt_percent -c 'print -P "%F{#ff0000}red%F{green}%B bold green"' emulate zsh -o prompt_percent -c 'print -P "%F{#ff0000}red%F{green}%B bold green"'
``` ```
--- ---
bug: open a new tab and hit ctrl-p. an empty line will appear before prompt. bug: open a new tab and hit ctrl-p. an empty line will appear before prompt.
--- ---
take a look at https://github.com/skywind3000/z.lua. it claims to have fzf support. would be nice take a look at https://github.com/skywind3000/z.lua. it claims to have fzf support. would be nice
if alt-down showed two groups -- one for subdirs and another for directory history (sorted by if alt-down showed two groups -- one for subdirs and another for directory history (sorted by
frequency of use? by last use? three sections? more key bindings?). frequency of use? by last use? three sections? more key bindings?).
--- ---
add `p10k explain` that prints something like this: add `p10k explain` that prints something like this:
```text ```text
segment icons meaning segment icons meaning
--------------------------
---
---
---
---
---
---
---
---
--
status ✔ ✘ exit code of the last command status ✔ ✘ exit code of the last command
``` ```
@ -64,17 +118,25 @@ green and icons in bold; battery can have an unlimited number of icons, so `...`
segments would have "unknown" icons by default (yellow and not bold); can allow them to segments would have "unknown" icons by default (yellow and not bold); can allow them to
participate by defining `explainprompt_foo` that populates array `reply` with strings like this: participate by defining `explainprompt_foo` that populates array `reply` with strings like this:
'-s STATE -i LOCK_ICON +r'; the first element must be segment description. '-s STATE -i LOCK_ICON +r'; the first element must be segment description.
--- ---
add `docker_context` prompt segment; similar to `kubecontext`; the data should come from add `docker_context` prompt segment; similar to `kubecontext`; the data should come from
`currentContext` field in `~/.docker/config.json` (according to `currentContext` field in `~/.docker/config.json` (according to
https://github.com/starship/starship/issues/995); there is also `DOCKER_CONTEXT`; more info: https://github.com/starship/starship/issues/995); there is also `DOCKER_CONTEXT`; more info:
https://docs.docker.com/engine/reference/commandline/context_use; also https://docs.docker.com/engine/reference/commandline/context_use; also
https://github.com/starship/starship/pull/996. https://github.com/starship/starship/pull/996.
--- ---
support `env` precommand in parser.zsh. support `env` precommand in parser.zsh.
--- ---
Add ruler to configuration wizard. Options: `─`, `·`, `╌`, `┄`, `▁`, `═`. Add ruler to configuration wizard. Options: `─`, `·`, `╌`, `┄`, `▁`, `═`.
--- ---
Add frame styles to the wizard. Add frame styles to the wizard.
```text ```text
@ -95,20 +157,26 @@ Add frame styles to the wizard.
``` ```
Prompt connection should have matching options. Prompt connection should have matching options.
--- ---
Add `POWERLEVEL9K_{LEFT,RIGHT}_SEGMENT_MIRROR_SEPARATOR`. If set, left segments get separated with Add `POWERLEVEL9K_{LEFT,RIGHT}_SEGMENT_MIRROR_SEPARATOR`. If set, left segments get separated with
`POWERLEVEL9K_LEFT_SEGMENT_SEPARATOR` followed by `POWERLEVEL9K_LEFT_SEGMENT_MIRROR_SEPARATOR`. `POWERLEVEL9K_LEFT_SEGMENT_SEPARATOR` followed by `POWERLEVEL9K_LEFT_SEGMENT_MIRROR_SEPARATOR`.
Each is drawn without background. The first with the foreground of left segment, the second with Each is drawn without background. The first with the foreground of left segment, the second with
the background of right segment. To insert space in between, embed it in one of these parameters. the background of right segment. To insert space in between, embed it in one of these parameters.
`POWERLEVEL9K_{LEFT,RIGHT}_SUBSEGMENT_SEPARATOR` is unused. `POWERLEVEL9K_{LEFT,RIGHT}_SUBSEGMENT_SEPARATOR` is unused.
--- ---
Add *Segment Connection* screen to configuration wizard with options *Fused*, *Touching* and Add *Segment Connection* screen to configuration wizard with options *Fused*, *Touching* and
*Disjoint*. The last two differ by the absence/presence of space between `SEGMENT_SEPARATOR` and *Disjoint*. The last two differ by the absence/presence of space between `SEGMENT_SEPARATOR` and
`SEGMENT_MIRROR_SEPARATOR`. `SEGMENT_MIRROR_SEPARATOR`.
*Fused* requires line separator (there is already a screen for it) but the other two options require *Fused* requires line separator (there is already a screen for it) but the other two options require
two filled separators similar to heads and tail. Figure out how to present this choice. two filled separators similar to heads and tail. Figure out how to present this choice.
--- ---
Get rid of `saved_columns` in the wizard and always present all options as if horizontal space was Get rid of `saved_columns` in the wizard and always present all options as if horizontal space was
unlimited. `print_prompt` should print something like this if prompt is too wide: unlimited. `print_prompt` should print something like this if prompt is too wide:
@ -141,11 +209,15 @@ ask_prompt \
There are two prompt questions that don't fit this pattern: `ask_empty_line` and There are two prompt questions that don't fit this pattern: `ask_empty_line` and
`ask_transient_prompt`. The first is easy to adapt (`print_prompt` can print prompt twice if `ask_transient_prompt`. The first is easy to adapt (`print_prompt` can print prompt twice if
`empty_line=1`) but the second will probably have to be hand-coded. `empty_line=1`) but the second will probably have to be hand-coded.
--- ---
Revert `3ef4e68b5fdae654f323af644cbca40f27a8ab97`. Instead of it use `zf_rm -f -- $dst` before Revert `3ef4e68b5fdae654f323af644cbca40f27a8ab97`. Instead of it use `zf_rm -f -- $dst` before
`zf_mv -f -- $src $dst`. `zwc` files are readonly and `zf_mv` fails on NTFS if the target file `zf_mv -f -- $src $dst`. `zwc` files are readonly and `zf_mv` fails on NTFS if the target file
exists and is readonly. exists and is readonly.
--- ---
Optimize auto-wizard check. Optimize auto-wizard check.
```text ```text