Skip to content

Conversation

rubo77
Copy link

@rubo77 rubo77 commented Jul 23, 2016

No description provided.

biggnou and others added 16 commits September 29, 2014 15:01
This is a nice evil-ish thing to do, a lot less harmful than the cd-rm or the fork bomb.
Signed-off-by: benaryorg <binary@benary.org>
 lQaosFsLsvt7ytmrcwP1y8FTw0nNVRzS6sGIeryjZLxhV9v2//6iRqpmMnScwDjn
 CpMhBLvQ2SK8JZ6/cl0qmtm4gblLDHYMbrewNJr3SSuFNZknDphbWRTxUMDX6Msd
 flJmN+bp4J6Vwpv8F0jUIH6wLrACqzu0ZJe3pujbATsd2EqpmPQiGDm2CCrwblbH
 C/9EjcdNrmDzZorzEeHFj30KLszAiazB2OLM8ikvOVHdmA9ifGEM/rSxONTOyuD0
 KU2ufNuHtMEh7Fsi9dEVu4Wnr5SmzFlrTAbEH0gyHSdSDNKL12ZK8/9HbGgR5I0=
 =nwRX
 -----END PGP SIGNATURE-----

Disable `alias` and `unalias`

Closes mathiasbynens#49.
In `bash`, `until` is just the same as `while !`. User may sometimes use this too, so we should invert it too.

I can't figure out when `for !` gives something that's not a syntax error, hence I removed it.
Removing obsolete constructs like `$[ expr ]` and `sleep NUMs` makes the script more portable, or at least easier to port to ksh and other POSIX shells as well as environments with other types of `sleep` (POSIX `sleep` doesn't require accepting suffixes.)

I have also added comments for users/screwers of other shells. Unfortunately I am too lazy to write those `if [ "$BASH" ]` code, and not to mention that figuring out if a shell is ksh and its version can be tricky.
Take longer and longer to SSH to the box
@benaryorg
Copy link
Collaborator

adding function to functions might be arguably more readable but sadly isn't compatible with all shells.

@benaryorg
Copy link
Collaborator

Also, please have a look at what I wrote at #30.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants