{"action":"closed","issue":{"url":"https://api.github.com/repos/lzybkr/PSReadLine/issues/359","repository_url":"https://api.github.com/repos/lzybkr/PSReadLine","labels_url":"https://api.github.com/repos/lzybkr/PSReadLine/issues/359/labels{/name}","comments_url":"https://api.github.com/repos/lzybkr/PSReadLine/issues/359/comments","events_url":"https://api.github.com/repos/lzybkr/PSReadLine/issues/359/events","html_url":"https://github.com/lzybkr/PSReadLine/issues/359","id":142101615,"number":359,"title":"Handle last command status and syntax errors in one prompt","user":{"login":"eugenesvk","id":12956286,"avatar_url":"https://avatars0.githubusercontent.com/u/12956286?v=4","gravatar_id":"","url":"https://api.github.com/users/eugenesvk","html_url":"https://github.com/eugenesvk","followers_url":"https://api.github.com/users/eugenesvk/followers","following_url":"https://api.github.com/users/eugenesvk/following{/other_user}","gists_url":"https://api.github.com/users/eugenesvk/gists{/gist_id}","starred_url":"https://api.github.com/users/eugenesvk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eugenesvk/subscriptions","organizations_url":"https://api.github.com/users/eugenesvk/orgs","repos_url":"https://api.github.com/users/eugenesvk/repos","events_url":"https://api.github.com/users/eugenesvk/events{/privacy}","received_events_url":"https://api.github.com/users/eugenesvk/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-03-19T21:22:53Z","updated_at":"2017-11-04T18:45:00Z","closed_at":"2017-11-04T18:45:00Z","author_association":"NONE","body":"In all my shells I have the last symbol showing status of last command (e.g. `current/path >_` with `>` in **green** if last command was a success and `>` in *_red *_if it was an error).\nNow, your awesome addon has a very nice feature of warning me on syntax errors by coloring the last prompt symbol in red. However, this doesn't really work if my last command was an error as the last symbol is already red.\nIs there a way I could combine both error indicators? I see a few ways of achieving this:\n1. Make PSReadLine replace last e.g. space with a symbol (e.g. `current/path >_` would turn into `current/path >!`, last space would be replaced with `!` warning you about the syntax error (`_` is a space as genuine space doesn't get displayed in the end of the code comment)).\n2. Make PSReadLine use a different color (maybe there is a separate syntax-error color option I've missed)\n3. Change font to bold/underline on error (as far as I understand that's impossible thanks to some stupid design decision by MS)\n4. (the one I'm using now) Add an invisible symbol `!` (same color as background) in the end so that PSReadLine would color it. However, this forces me to have two spaces in the end instead of one as I must have a `Return \" \"` at the end of my prompt function due to another smart design choice by MS). Maybe there is a fix for this I'm just not aware of\n5. Something else?\n"}}
{"actor":{"display_login":"lzybkr"}}