8000 No visible error when a compile step fails · Issue #1641 · TrenchBroom/TrenchBroom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No visible error when a compile step fails #1641

Closed
JackViney96 opened this issue Jan 13, 2017 · 0 comments
Closed

No visible error when a compile step fails #1641

JackViney96 opened this issue Jan 13, 2017 · 0 comments
Assignees
@kduske
Labels
Prio:2 Medium priority: Non crash bugs that impede the user, features that add new functionality. Type:Bug Errors and problems
Milestone
TrenchBroom 2.0.0

Comments

@JackViney96
Copy link

Referring to http://www.celephais.net/board/view_thread.php?id=60908&start=2477 and the following posts; there should be some kind of user feedback indicating that a stage of a compile process has failed.
@kduske kduske added this to the TrenchBroom 2.0.0 milestone Jan 13, 2017
@kduske kduske added Platform:All Prio:2 Medium priority: Non crash bugs that impede the user, features that add new functionality. Type:Bug Errors and problems and removed Status:Ready labels Jan 13, 2017
@kduske kduske self-assigned this Jan 13, 2017
kduske added a commit that referenced this issue Jan 13, 2017
@kduske
#1641: Print an error message when an error occurs while interpolatin…
e1041c7 
…g EL expression in compilation window.
@kduske kduske mentioned this issue Jan 13, 2017
Merged
kduske added a commit that referenced this issue Jan 14, 2017
@kduske
#1641: Print an error message when an error occurs while interpolatin…
82b193f 
…g EL expression in compilation window. (#1644)
@kduske kduske closed this as completed Jan 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kduske kduske

Labels
Prio:2 Medium priority: Non crash bugs that impede the user, features that add new functionality. Type:Bug Errors and problems
Projects
None yet
Milestone
TrenchBroom 2.0.0
Development

No branches or pull requests
2 participants
@kduske @JackViney96
0