-
Notifications
You must be signed in to change notification settings - Fork 209
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
Errors in sourcing when launching a new terminal #79
Comments
bkhouri
changed the title
Errors source when launching a new termina
Errors in sourcing when launching a new terminal
Feb 15, 2019
Hi, in case this is still a problem could you post the output of Meanwhile I'll look into it. |
I could find the job control output ( |
benaryorg
added a commit
to benaryorg/evil.sh
that referenced
this issue
Jun 29, 2019
need to start every background job in its own subshell so that we can redirect the job control output to /dev/null. Plus a quotation fix there. Signed-off-by: benaryorg <[email protected]>
benaryorg
added a commit
to benaryorg/evil.sh
that referenced
this issue
Jun 29, 2019
Need to start every background job in its own subshell so that we can redirect the job control output to /dev/null. Plus a quotation fix there. Signed-off-by: benaryorg <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I love this idea, and I want to apply on to co-workers. However, when adding
source /path/to/evil.sh
as the last line in the.bash_profile
, error occur when a new terminal is started.I only tried setting
EVIL_BEHAVIOUR
toinsane
orannoying
.On my Mac, running
macOS Mojave
, I get the following when I start a terminal with EVIL_BEHAVIOUR set toinsane
And I get the following when set to
annoying
This error will make it obvious that something is awry in the system.
The text was updated successfully, but these errors were encountered: