-
-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove empty line #509
Comments
Note that with shell integration a terminal can use some other visual separator between commands, so the empty line is redundant. |
I locally patch like this: diff --git a/pure.zsh b/pure.zsh
index ddb0e30..3dad87d 100644
--- a/pure.zsh
+++ b/pure.zsh
@@ -176,7 +176,7 @@ prompt_pure_preprompt_render() {
if [[ $1 == precmd ]]; then
# Initial newline, for spaciousness.
- print
+ # print
elif [[ $prompt_pure_last_prompt != $expanded_prompt ]]; then
# Redraw the prompt.
prompt_pure_reset_prompt It is prefer to keep current behavior for other users, so how about create new option value like |
You can hack around pure's current opinion with a custom implementation of print() {
[ 0 -eq $# -a "prompt_pure_precmd" = "${funcstack[-1]}" ] || builtin print "$@";
} This implementation of Put this in your .zshrc before initializing pure and you're good to go. Future updates to how pure behaves may invalidate this hack. Caveat emptor. |
@bishopb Is there anyway to prevent the new line only when the terminal is When I open a new terminal this happens: The custom |
@james-prado, not easily: you'd have to provide context to that |
@bishopb Thanks for the reply. Yea that's a fair bit to go through just to remove a new line. I've learned to live with it for now. |
Using @bishopb's function and a slightly modified function from stackoverflow this works for new tabs/windows, but not for |
There is an empty line between subsequent prompts. This can be seen in the image that it is in the README. For example, there is a line between "Exit 1" and "~".
Is it possible to remove this line? I find it wastes to much space.
The text was updated successfully, but these errors were encountered: