Commit graph

13 commits

Author SHA1 Message Date
Jan De Dobbeleer 66941ddb43 fix: correct cross platform home location
resolves #24
2020-10-05 17:19:05 +02:00
Jan De Dobbeleer 9ffa132174 feat: ignore folders for segments 2020-10-05 17:19:05 +02:00
Jan De Dobbeleer 3e18c241ab refactor: rename for clarity 2020-10-05 17:19:05 +02:00
Jan De Dobbeleer 82c8483603 refactor: offsets match functionality 2020-10-05 17:19:05 +02:00
Jan De Dobbeleer afaaace35b refactor: final_space is better name
I\'m coming for you Avocato
2020-10-05 17:19:05 +02:00
Jan De Dobbeleer 1d8e7b2458 refactor: change powerline config to segment 2020-10-05 17:19:05 +02:00
Jan De Dobbeleer 9a508142fc refactor: understandable offset properties 2020-10-05 17:19:05 +02:00
Jan De Dobbeleer f478255bbf refactor: escape color sequences on zsh 2020-09-24 19:34:19 +02:00
Jan De Dobbeleer f410c32f6e refactor: remove powerline bg color 2020-09-21 20:29:50 +02:00
Jan De Dobbeleer db212d513f fix: ignore segments without writer 2020-09-17 17:47:32 +02:00
Jan De Dobbeleer 6fd9f0bdd9 fix: render newline correctly cross platform/shell
Powershell has an issue rendering multiline prompts when it comes to
PSReadline on MacOS. To mitigate that, we make it a multiline
prompt by moving the cursor all the way to the end. That way, PSReadline
believes this is still a one line prompt and everything works as
expected.

https://github.com/PowerShell/PowerShell/issues/3687
2020-09-17 12:38:01 +02:00
Jan De Dobbeleer 9b9405978e fix: make newline compatible cross shell
When using PowerShell, "\n" isn't recognized as a newline character.
To resolve this, moving the cursor down 1 line is more interesting
as it will work in any shell using ANSI escape sequences (which we
depends upon).
2020-09-16 10:46:50 +02:00
Jan De Dobbeleer c4d1c75781 feat: initial commit 2020-09-12 08:57:18 +02:00