lscolors | LSCOLORS Generator | Generator Utils library

A segmentation fault happens when the code try to access a memory region that is not available.

Accessing an array out of bounds doesn't means that the memory before or after the area occupied by the array is not available: The compiler or the runtime usually put all varibales or data in general in a given block of memory. If your array is the last item of such a memory block, the accessing it with a to big index will produce a Segmentaion Fault but is the array is in the middle of the memory block, you will just access memory used for other data, giving unexpected result and undefined behavior.

If the array (In may example, but valid for anything) is written, accessing available memory will not produce a segmentation fault but will overwrite something else. It may produce unexpected results or crash or segmentation fault later! This kind of bug is frequently very difficult to find because the unexpected result/behavior looks completely independent of the root cause.

%F and %f act more like 'start color' and 'stop color', so they need to surround the text and operators that you want to colorize. Also, very few named colors are supported (just black, red, green, yellow, blue, magenta, cyan and white); you'll have better luck with the numeric values from the xterm column of this table.

Try this:

You're making two mistakes in your .zshrc file:

1. If you do source $ZSH/oh-my-zsh.sh, then you shouldn't also do autoload -U compinit && compinit, because the former includes the latter.
2. plugins=( ... ) should be done before doing source $ZSH/oh-my-zsh.sh. The former does not do anything by itself.

So, change the top of your .zshrc file to this:

Put the LS_COLORS export in your ~.zshrc file not oh-my-zsh.sh. So it would look something like this:

I'm running High Sierra. I don't know if you just updated the software and still have the bash settings in your system, but if that is the case you should be able to switch back to bash if that is easier. I found this website explains it, but simply, change back to bash with:

Finally found a solution. Much thanks to @SalchiPapa who took his time out to personally videocall me and solve the issue. Solution right now is to not run IJulia from root

What worked for me :

$su user-not-root

$julia

using IJulia;notebook(detached=true) This should show ProcessRunning at the end.

run(path/to/jupyter notebook list) with pair of backticks inside run().

This gave me the url and token appended to it . That worked out well.

I suggest that the community help solve this issue. I have linked this answer to a Github issue here