-
Notifications
You must be signed in to change notification settings - Fork 165
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
Give more helpful warning when using tabs in continuations #3375
Conversation
0a0959f
to
bba65fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, very useful! Some nitpicking, though
Codecov Report
@@ Coverage Diff @@
## master #3375 +/- ##
==========================================
+ Coverage 85.14% 85.33% +0.19%
==========================================
Files 697 696 -1
Lines 344069 342430 -1639
==========================================
- Hits 292941 292208 -733
+ Misses 51128 50222 -906
|
This rejects continuations using 'tab' inside tests. They can be confusing for users because GAP does not treat them as continuations, but instead a line of output. They are rejected, rather than treated as continuations, because we do not want different parts of GAP to handle continuations differently, or really start changing the definition of something so fundamental. This does break any tests which start an output line with '>\t', but no such tests seem to exist and would be easily confused with a continuation.
e6b3002
to
7af058a
Compare
All cleaned up. Also, did a quick cleanup using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
This rejects continuations using 'tab' inside tests. They can
be confusing for users because GAP does not treat them as
continuations, but instead a line of output.
They are rejected, rather than treated as continuations, because
we do not want different parts of GAP to handle continuations
differently, or really start changing the definition of something
so fundamental.
This does break any tests which start an output line with '>\t',
but no such tests seem to exist and would be easily confused with
a continuation.
Fixes #3068 (by giving a nice error) while hopefully not breaking any tests (unlike my previous attempt at fixing this, which broke Browse).