Bash output about teamocil HOT 8 CLOSED

Hi David, I do not know a way of executing commands without echoing them. However, I modified the behavior of Teamocil (b727311) so it merges every commands it has to run for the split (filters, export TEAMOCIL, commands) and join them with && so it reduces the amount of echoed lines. For example, your example is now:

export TEAMOCIL=1 && git status
~/Projects ∴ export TEAMOCIL=1 && git status
# On branch develop
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)

That's the best I could do 😄 Let me know if you have other ideas on how we can improve this.

Thanks for the report!

from teamocil.

you could use the clear command before your git status or we could just clear system methods like the export TEAMOCIL=1

export TEAMOCIL=1 && clear && git status

# On branch ability-defined
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#   modified:   spec/rules/event_rules_spec.rb
#
no changes added to commit (use "git add" and/or "git commit -a")

if you want to hide

from teamocil.

That's a good idea, but I don’t think it’s a good idea to clear out the whole session, since users might have some kind of motd message they want to see in each split.

from teamocil.

this is why is better for the user to just opt-in the feature, they can add the command to their list.

I prefer to see what you are sending to my shell.

from teamocil.

Oh I see, you were suggesting it to @davejacobs — I though you meant it for teamocil’s default behavior :)

from teamocil.

Ah okay, thanks guys. Thanks for the change, I'll add clear to my scripts. I understand you can't prevent the command from showing up as you execute it, but is there a way to prevent it from showing up twice like it does now?

from teamocil.

In fact, the reason the command is showing up twice is that we send it to the split before the prompt is capturing user input. Since the prompt is not ready, it just displays whatever data we send. When the shell is ready, it takes the data, show it in the prompt and execute it, but the command is still showing up one line above. You can reproduce this behavior by adding a line like this in your ~/.bashrc or ~/.zshrc:

sleep 3

Start a new shell and type anything on the keyboard during the three seconds it sleeps. When the shell starts, whatever you type will now be in your prompt and still showing up.

A way to get rid of the commands is to add clear as the first line of your ~/.bashrc or ~/.zshrc so when your shell is ready to start, it will clear everything that was sent before.

from teamocil.

Gotcha, thanks for the clarification.

from teamocil.