yardnsm/blox-zsh-theme

:computer: Clean, modular ZSH theme

blox-zsh-theme's Issues

Todos

The theme is not perfect. Let's make it so.

• Add the number of bg tasks
• Fix spacing
• Add more options to blocks, colors mostly.
• When re-sourcing zshrc, a } is added next to the git info. Fix this.
• Add a notice about spacing issues, recommend to use a percent-braces construct (%{…%}) when needed/
• Improve README a bit
• Update screenshots to match updates (not so many changes)

Automatically setup hooks

This will eliminate the need for coupled setups, such as in:
https://github.com/yardnsm/blox-zsh-theme/blob/master/blox.zsh#L81-L83

I suggest enumerating all of the used blocks and try to run the blox_block__${BLOCK_NAME}_hook__preexec and blox_block__${BLOCK_NAME}_hook__precmd for the preexec and the precmd hooks accordingly.

Also, support for more hooks could be nice.

Resizing the terminal causes lines to disappear

I use this theme with terminator, and opening a new terminal window below (using ctrl+O) often causes the previous terminal window to lose lines. I'm not totally sure what's causing this, but this problem doesn't occur with other zsh themes. I suspect it has to do with resizing code that clears too many lines.

Add options for removing git commit hash and newline

I like this theme a lot, just a couple suggestions for more options. I think it would be nice to have the option to remove the commit hash and the newline between prompts.

maybe auto completiotion?

Hi guys,

I've installed now oh-my-zsh. using theme "linuxonly".
I took me a long tim e to install QEMU.

root@think-01:pts/1->/root (0)
qemu
zsh: command not found: qemu

NOW WITH TAB

root@think-01:pts/1->/root (127)

_qemu
_qemu _qemu_log_items

so thats it. now in bash... and TAB

root@think-01:pts/1->/root (127)

bash

root@think-01:~# qemu-
qemu-img qemu-system-alpha qemu-system-m68k qemu-system-mipsel qemu-system-ppc64le qemu-system-sparc qemu-system-xtensaeb
qemu-io qemu-system-arm qemu-system-microblaze qemu-system-moxie qemu-system-riscv32 qemu-system-sparc64
qemu-make-debian-root qemu-system-cris qemu-system-microblazeel qemu-system-nios2 qemu-system-riscv64 qemu-system-tricore
qemu-nbd qemu-system-hppa qemu-system-mips qemu-system-or1k qemu-system-s390x qemu-system-unicore32
qemu-pr-helper qemu-system-i386 qemu-system-mips64 qemu-system-ppc qemu-system-sh4 qemu-system-x86_64
qemu-system-aarch64 qemu-system-lm32 qemu-system-mips64el qemu-system-ppc64 qemu-system-sh4eb qemu-system-xtensa

everythings there. what do am i wrong?

Thanks for your oppinions.

CTRL+L doesn't show upper segments

The issue arises when I'm clearing the screen. If I use clear it works perfectly (it clears the screen and both upper and lower segments are displayed)

However, when I use CTRL+L the screen is cleared but the upper segments are not displayed

Any idea on how I can fix this?

Add more blocks and update existing ones

New blocks:

• exec_time - last command's execute time
• pyenv - display the python version being used by pyenv
• virtualenv - display the name of the currently used virtual env

Improvements for existing blocks

• nodejs block should be visible if there's at least one file matching /^\.(m)?(j|t)s(x)?$/
• cwd - Display ... when cwd is truncated
• git - add an indicator for stashed files

Literal `tab_label` as cwd

I don't understand, what exactly is happening, but when some directories, instead of the home-adjusted path, a literal tab_label is printed as part of the prompt (blox_hook__title) after it was rendered correctly once:

/srv/www/projekt master[hash] ✘ $                                                                                             [[12:17]
 ❯

 ~tab_label master[hash] ✘ $                                                                                                         [12:17]
 ❯

If I change to title hook to

# ---------------------------------------------
# Hooks

# Set the title to cwd
function blox_hook__title() {
    echo -ne "\e]2;${PWD/${HOME}/\~}\a"
}

this does not happen. I do think it has to be something in my zsh setup, but I'm at a loss, what it could be.

(Feel free to close this as "Not a problem /here/", I just thought I'd ask)

Add some tests

Because why not? :D

BLOX_CONF__PROMPT_PREFIX can only be disabled via unset

The changes introduced in #3 makes it such that BLOX_CONF__PROMPT_PREFIX can only be disabled by unsetting it after sourcing blox.zsh. The expansion done here means any null/empty value for that variable will be replaced with \n, effectively meaning you cannot disable the prompt prefix.