I have recently installed OhMyZsh, with Powerlevel10k theme. I know this is git related, but,
what means the *10 or the ?1 signs and numbers?
Thanks in advance.
my terminal screenshot
I have installed szh, with oh my szh, then, installed Powerlevel10k theme, then trying to customize that i found that numbers on my terminal
*10 means there are 10 stashes in your repo. (git stash list)
?1 means your working copy is dirty i.e. there are new, edited or deleted files in the repo (git status).
Here is Powerlevel10k reference for vcs: https://github.com/Powerlevel9k/powerlevel9k#vcs-symbols
Related
I am a newbie with Zsh + Oh My Zsh and have my prompt set to randomly choose between a couple of themes.
ZSH_THEME_RANDOM_CANDIDATES=( "robbyrussell" "kafeitu" "avit")
However, I've customized these a bit to make them more like the way I want them.
A side-effect of this is that now, when I get prompted to update Zsh, I cannot:
[oh-my-zsh] Would you like to update? [Y/n] Y
Updating Oh My Zsh
error: Pulling is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit.
fatal: Exiting because of an unresolved conflict.
There was an error updating. Try again later?
How can I have customized themes and still maintain the repo such that I can pull down updates?
Thanks.
It turns out there's a custom folder at ~/.oh-my-zsh/custom directory just for this purpose.
To customize one of the many themes, you just copy a theme in the main theme directory at ~/.oh-my-zsh/themes to ~/.oh-my-zsh/custom/themes and edit it as you like. The setting in .zshrc for ZSH_THEME="[theme name]" will look into this custom area first before looking in the main themes folder.
Documentation: https://github.com/ohmyzsh/ohmyzsh/wiki/Customization#overriding-and-adding-themes
For some apparent reason i can't commit to a new repo which i just made.
Git for desktop says the following:
Trying the first line in cmd gives the following error...
There indeed is no folder in Roaming called 'SPB_Data', nor would i know what it is for or why git even gets pointed that way..
I've tried a lot of things already and can't find anything that seems to help.
It seems that the git installation got messed up for some reason, i think...
How do i fix this?
I'm on windows 10
Some software set probably set you %HOME variable wrongly. Refer to the comment on this answer. And then you probably have to set your %HOME to the correct directory, as explained in this answer to the same question.
As said in my comment :
have you tried to re-install git, maybe your installation failed? and for the
first error its normal , git just wants you to specify your username and email
to show who comited on the repository
To clarify the problem: your git installation normally set a %HOME% Variable but its pretty unreliable and probably the root of your problem. As shown in your error message git can't find the config files with your %HOMe% variable so you need to manually change it or re-install git.
As seen in this answer https://stackoverflow.com/a/4051282/7141618 , you can verify where your %HOME% path points to and if its the wrong directory you can change it using the windows tool like in this link: https://www.computerhope.com/issues/ch000549.htm , to sum it up open you settings, then click on advanced system setting, open the advanced tab and there should be a environement variable button that you can click to edit them.Finally just edit the %HOME% path to fit your git installation folder
Sorry if this isn't the place for this, I don't know where else I'd ask.
For Mac OSX El Capitan
I am trying to edit the property _staticHtmlFileExts
The variable used to be defined in src/file/FileUtils.js, but has since been moved to src/LiveDevelopment/LiveDevelopmentUtils.js.
When I go to Show Developer Tools within Brackets, I can view the sources, and very easily find /LiveDevelopment/ (and the child JS file)...
But any changes I make to the file are not saves on the system, and thus do not persist on successive opens of the Brackets app.
When I try to find the same file on my system, it is nowhere to be found...
I have hidden folders set to display (which they all do, when present), so I do not believe this to be the issue.
How come I can view the files in the Dev Tools, but not on my system? How, or where, can I make the change permanently?
The build installed with the Brackets.dmg installed minified, concatenated source file (main.js under ~/Application/Brackets.app/Contents/www/) along with a source map, which is why you can see the sources in developer tools, but you cannot see the original source files.
See the article How to hack on Brackets for instructions on setting up a development environment if you want to modify the files themselves.
For reference, the steps are as follows:
Install the latest Brackets build (this gives you the native shell binaries which you'll use in step 6)
Fork the brackets repo
Clone your fork of the repo: git clone https://github.com/<username>/brackets
Fetch submodules: cd brackets && git submodule update --init
Add an "upstream" remote: git remote add upstream https://github.com/adobe/brackets
Run setup_for_hacking script with tools/setup_for_hacking.sh "/Applications/Brackets.app"
Note that the steps 2 and 3 are optional if you are just making modifications for yourself. If so, you can just clone straight from the master (git clone https://github.com/adobe/brackets).
I heard about the awesomeness of vim, so naturally I said "vim me up". After, countless Youtube videos and Googling for hours, I was ready to install my pluggins ( so I thought). I was able to install NERDTree thru Pathogen and I was feeling good about myself since I'm new to Mac(OSX 10.9) and coding in general. So, I then proceeded to install the next pluggin Snipmate using instructions from https://github.com/garbas/vim-snipmate
% cd ~/.vim/bundle
% git clone https://github.com/tomtom/tlib_vim.git
% git clone https://github.com/MarcWeber/vim-addon-mw-utils.git
% git clone https://github.com/garbas/vim-snipmate.git
% git clone https://github.com/honza/vim-snippets.git
Snipmate did not work. So, I deleted these directories by rm -rf {directories}
then tried to install it again using instructions from http://spf13.com/post/vim-plugins-snipmate this time
cd ~/.vim
mv snippets snippets.orig
git clone git://github.com/scrooloose/snipmate-snippets.git snippets
Maybe I shouldn't have done since I now have these errors everytime I open vim.
Warning in snipMate.vim: Snippet c) is already defined. See :h multi_snip for help on snippets with multiple matches.
Warning in snipMate.vim: Snippet date is already defined. See :h multi_snip for help on snippets with multiple matches.
Warning in snipMate.vim: Snippet ddate is already defined. See :h multi_snip for help on snippets with multiple matches.
Do you think if I could uninstall those files, that I had deleted, would it rid of these errors and maybe snipmate would work?
How do you uninstall git clone command? Am I right in thinking these?
That's because you still have the snippets defined in "snippets.orig". If you delete the folder (or if you want to keep it move it to a directory outside of .vim) and you should be fine.
I have pathogen setup and working fine under Linux, but when I try to use the some configuration with gvim73 under windows it doesn't work at all. I don't get any errors but it does nothing.
Here is my dotfiles repository up on git. I've checked this out to ~/vimfiles and I added the following to _vimrc:
filetype off
call pathogen#helptags()
call pathogen#runtime_append_all_bundles()
I've tried just about everything including putting the autoload/pathogen.vim and bundles/ folders in the /vim73 directory under program files. Nothing.
Does anyone have some experience with this? I'm assuming there is something windows specific that needs to happen to make this work.
Edit: It is probably also worth noting I can run pathogen#runtime_append_all_bundles() even using tab completion so pathogen is being loaded, but my plugins are just not working.
I'm not sure it will help but here is my working configuration:
d:\soft\vim\vim73\ - gvim itself, i.e.
pathogen.vim is copied into the
d:\soft\vim\vim73\autoload\
d:\soft\vim\vimfiles\bundle - directory
for plugins
Corresponding lines from configuration file d:\soft\vim\_vimrc:
" Use pathogen to load plugins from bundle directory
filetype off
call pathogen#runtime_append_all_bundles()
call pathogen#helptags()
Also I changed pathogen#helptags because original didn't work for my paths:
dir[0 : strlen($VIM)-1] !=# $VIM has been changed to stridx(dir, "bundle") != -1
It's an old question, but I had the same issue and solution as the OP, and it has a mildly annoying origin. I was using the following script to install everything on Windows (Vista+ and run as admin if you want the mklink part to work):
cd "%UserProfile%"
rmdir vimfiles /S /Q
git clone http://github.com/brymck/dotvim.git vimfiles
del _vimrc
mklink _vimrc vimfiles\vimrc
cd vimfiles
git submodule init
git submodule update
The above is just a Windows-y version of a Vimcast on syncing your Vim preferences with GitHub and is fairly straightforward, so I figure others may be doing something similar.
Anyway, your experience may differ (and this doesn't apply to Cygwin), but when I just copied and pasted this into the terminal, git submodule update got "eaten" while git submodule init was running. I didn't figure it out initially because this had never happened to me on Linux. In short, wait until everything else has completed before running git submodule update and you should be golden. (Also, FWIW, I'm using the current version of pathogen, which was last updated September 25, 2011.)
For me renaming the .vim folder into vimfiles solved the problem for Vim 7.4.
I had some kind of issue on Windows when I used the pathogen version provided by Vim.org
However, using github pathogen head, the issue was fixed.
I think the latest release from Vim.org is from January last year, and the latest commit on github is from November.
Specifically, I had this issue with after directory:
https://github.com/tpope/vim-pathogen/issues/closed#issue/12
I know this is a long time ago, but maybe it will help someone ... I had the same issue. It wouldn't give me any errors, but no plugins would be loaded. I then RTFM and noticed that he explicitly states at the top of this page that it should go in your vimrc not gvimrc. After I changed that I had no problems.