-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Some improvements #846
Some improvements #846
Conversation
Inspired by Brett Cannon's advise [1]. 1: https://snarky.ca/how-to-use-your-project-travis-to-help-test-python-itself/
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.
I don't have much context for most of these issues, but the changes seem fine! Is the plan to "Rebase and merge" this using github, or were you just thinking of pushing directly to master? I'd prefer the former if that's ok with you.
@@ -420,7 +422,8 @@ rule with lower `priority` will be matched first; | |||
* `THEFUCK_HISTORY_LIMIT` – how many history commands will be scanned, like `2000`; | |||
* `THEFUCK_ALTER_HISTORY` – push fixed command to history `true/false`; | |||
* `THEFUCK_WAIT_SLOW_COMMAND` – max amount of time in seconds for getting previous command output if it in `slow_commands` list; | |||
* `THEFUCK_SLOW_COMMANDS` – list of slow commands, like `lein:gradle`. | |||
* `THEFUCK_SLOW_COMMANDS` – list of slow commands, like `lein:gradle`; | |||
* `THEFUCK_NUM_CLOSE_MATCHES` – maximum number of close matches to suggest, like `5`. |
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.
Should we just switch to putting a ;
on the last line (instead of .
), so the diff can be smaller going forward?
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.
I had the exact same thought. But the next thought was "Wait. It's text, not code". Perhaps it makes sense to have a period there. For me it will look like an unfinished list.
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.
Hmm yeah, that makes sense too. Alternatively, since we already have the bullet points, maybe it makes sense to remove the semicolon/period entirely? Obviously this would be a separate change.
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.
I believe that's a good one, reasonable change. 👍
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.
Thanks, I'll wait until this is closed to make that change (if I remember)
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.
@josephfrazier I think it should be ok to remove ;
, as it's not required by grammar rules
Thanks for the review, @josephfrazier! "Rebase and merge", absolutely! I also prefer it :-) |
Oh, let me add some tests to |
a425464
to
01c015b
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.
Looks good!
Diff is huge, thanks 😀! |
* nvbn#833: do not require sudo on TravisCI * #N/A: Add Python dev releases to TravisCI pipeline Inspired by Brett Cannon's advise [1]. 1: https://snarky.ca/how-to-use-your-project-travis-to-help-test-python-itself/ * nvbn#837: try and kill proc and its children * #N/A: show shell information on `thefuck --version` * #N/A: omit default arguments to get_close_matches * nvbn#842: add settings var to control number of close matches * #N/A: remove `n` from the list of `get_closest`'s args
Please don't merge yet. I'd like these changes to be reviewed. Once it's all good I'll push to master. Thanks!