After creating a new virtual environment in anaconda/conda I've found that I have this ridiculously long prompt that has a bunch of git information in it. Besides taking 2/3 of a line on my terminal, it lags by a few seconds every time I hit enter, presumably because it is re-analyzing for changes. How can I get rid if this and go back to normal? There's nothing in my bashrc that has anything to do with this. It appears to be related to "liquid prompt".
Whenever I start a new session in PhpStorm embedded terminal it doesn't have any history of previously entered commands and by pressing Up key it usually shows some command I executed ages ago via macOS terminal.
Is it possible to make the embedded terminal preserve history of commands, that were entered in another embedded terminal before.
Not possible currently, please follow IDEA-155571 and linked tickets for updates
I have been working with two terminal windows in my Mac (dev/prod), both had shown the commands and results history (scrolling up) for the last 6 months of work, which was very helpful to run periodic commands and to check past errors.
Yesterday I turn off my mac and closed both terminal windows manually, but today when opening the terminal it has no history at all. There is a way to recover the windows with all the history for past commands and their results?
I know there is a .bash_history file but it only shows commands typed but not the results.
Thanks in advance.
Bash's history only store executed commands, not their output, and only a limited number of them (usually 500, as defined by environment variable HISTFILESIZE). This won't help in your situation.
From what I can see, it appears that Terminal store save window's state (including console history) inside directory /Users/<user>/Library/Saved Application State/com.apple.Terminal.savedState/. Files in this directory are modified in real time whenever new events occurs in the terminal window, and unless I am mistaken, should be included in Time Machine backups. Therefore, it seems that if you can restore files in this directory from some former backup, you should get back your history. You could even try some "file undelete" tools in that directory, though these tools are rather rare on OS X.
The procedure for this should be that you first quit Terminal, then restore the whole directory (for example using Time Machine), then simply launch Terminal. These saved state files use a custom binary format, that you can't be read otherwise than by the Terminal program itself.
By the way, it might be worth mentioning that you can, at anytime, save the content of a Terminal window to a text file, from the Shell menu. You might consider doing it periodically, in the future, given that your terminal's history appears to have some significant value...
if using zsh check your /etc/zshrc for the history file location, mine has
# Save command history
HISTFILE=${ZDOTDIR:-$HOME}/.zsh_history
HISTSIZE=2000
SAVEHIST=1000
also check your ~/.zshrc incase the defaults for these have been changed
I'm trying to start learning parse cloud code. When I launch the parse.exe via my command line, various terrible things happen. For example, if I try to launch it using any kind of a command, but it's not set to "launch as administrator", I will see no text from the program(it will expect me to input my email and password, yet I will see no text I would see if I launched it as administrator). If I run it as administrator, it ends up consistently crashing during any activity. For example, if I try to go for >parse list, I will get to login, the list of apps appears and then the window instantly closes. Strictly following the tutorial(https://www.parse.com/apps/quickstart#cloud_code/windows) crashes midway as well. Doing >parse new for my existing app creates parse.local and parse.project files in the specified directory, but none of the rest files expected. I cannot seem to find the I'm pretty much lost here. Am I doing something wrong? I have the latest parse.exe thing, redownloaded it from multiple locations provided by parse.
I am trying to run some commands using the console in windows 8. My problem is that I have a hard time debugging an application I build, as the response I get after some commands is too big. I have maximized the window but I can only view some lines (50-60 does not matter).
How can I view everything from the beginning to the end?