zsh_history | Backup and restore ZSH history | Continuous Backup library

os.system("ls -al") won't return the output you normally see in the shell but only the return code. 0 if the command was executed successfully, 1 if not, etc. Read more about this here.

But you can use subprocess.check_output()to do so. Be aware, that the command must be passed to the method as a list of commands / parameters:

I'm not positive, but I believe the leading colon allows you to execute the history file as a script.

: is a do-nothing command: it ignores its arguments then completes with an exit status of 0. In this case, the argument is the string :0; the semicolon is a command terminator.

You can try it out at the prompt:

There isn't a node specific history file for execs unless you created one by logging the arguments. There can be lower level OS logging that captures this type of data, like an audit log.

Passing a password on the command line is still considered the least secure way. Try -f to pass a file or -d for a file descriptor instead (or ssh keys should always be the first port of call)

The man page explains...

The -p option should be considered the least secure of all of sshpass's options. All system users can see the password in the command line with a simple "ps" command. Sshpass makes a minimal attempt to hide the password, but such attempts are doomed to create race conditions without actually solving the problem. Users of sshpass are encouraged to use one of the other password passing techniques, which are all more secure.

In particular, people writing programs that are meant to communicate the password programatically are encouraged to use an anonymous pipe and pass the pipe's reading end to sshpass using the -d option.

Following this answer on SuperUser StackExchange, I would assume that you have to create .zshrc, .bashrc, etc., on your own. As far as I can tell, you just need a .zshrc for what you are doing. Then you can continue with the setup from the tutorial.

.zsh_history keeps the history of commands you entered in zsh. So yes, it's safe to delete, the only thing that happens is that your history will be gone.

You ran git init in your home directory. This created a Git repository in your home directory which covers everything in your home directory and all the subdirectories. All the existing files are "untracked" until you git add them.

You probably don't want that. Git stores all its information in a .git directory, so you can get rid of this repository by deleting ~/.git/. Later you might try putting all your dotfiles into a Git repository.

If you want to initialize a Git repository in a specific directory, either change to that directory and then git init, or git init .

I recognize some of these directories, but others I have never seen. Is this a problem? should I delete them?

No, it is not a problem. No, do not delete them.

Operating systems often hide certain important "system" files and directories vital for your system to run from you to prevent you from accidentally modifying or deleting them. Often that means dotfiles like .bash_profile or directories like Library/. They're worth looking into to understand more about how your Mac works.

But https:/ is probably a mistake.

Also, where could I find a good tutorial on Git, everything on YouTube seems too superficial.

I recommend Pro Git by Scott Chacon and Ben Straub. It's free and very good.

Also Github's Using Git. Some is Github specific, but a lot is general Git tutorials.

To understand how Git works, try my own Git For Ages 4 And Up.

When you say git init, you are doing two things:

• You create a (normally invisible) .git folder in the current directory.

• You place the current directory and all its subdirectories recursively under git control.

So, if you whip out the Terminal and say

You can run this command :