All my projects are contained within the same (Mercurial) repository because these projects are rather small.
So I have this folder "Workspace" containing other folders "Project A", "Project B" and so on.
And the ".hg" folder.
In IntelliJ, the "changes window" shows all uncomitted changes from all projects. If I open "Project A", it displays also changes of "Project B" and vice versa.
But I just want to see those uncomitted changes of the current project's folder.
Is there any setting which could resolve this issue?
The Changes view always shows all changes under the VCS roots associated with the project. You can use the "Group by Directory" button to separate the changes under Project A and Project B.
Related
So I just noticed that my PhpStorm has set a background color to my project and also the structure is weird. All best explained by some screenshots.
This is how it is looking now, I cannot even see my App folder etc here:
After I click on Project in the top and then select Project Files, I can see my structure again like normal:
My question is, what does this mean and how can I set it "back to normal"? As for me, "normal" means the following:
I can see all my files in Project and also there is no brown background color.
What I have done so far, as suggested from Google searches, is:
Close the project, remove it from recent projects and opening it again in PhpStorm.
Removing the .idea folder and opening my project again.
Reload All From Disk.
Invalidate Caches.
P.S. This is a new Laravel project, with only some minor changes and all files added to git, and also just did one last commit. Nothing "fixes" this.
This "yellowish" background means that the IDE treats those files/folders as excluded or not part of the project (i.e. outside of the project). This can be caused by some broken/out-of-sync project config file (for whatever reason, e.g. when making a project and there is incomplete .idea folder already / merge conflict etc).
Deleting .idea subfolder while IDE is closed and then reopening the project is enough to fix it (use "Open" and point to the project root folder and PhpStorm will make a new project from existing files).
Related forum thread/tickets:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/4404912351506/comments/4404921897746
https://youtrack.jetbrains.com/issue/IDEA-271728
https://youtrack.jetbrains.com/issue/IDEA-296960
I have two separate Drupal 8 sites that I am working on locally; each has a separate project in PhpStorm. There is nothing shared between projects.
When I'm working on "Project A" I am getting "Multiple definition exists for class..." messages all over the place. Strangely, when I command click on an instance of one of these classes I am presented a choice of which definition I want to open: the one from "Project A" (.../path/to/class) or the same class from "Project B" (/absolute/path/to/projectb/path/to/class).
How can I get PhpStorm to stop looking in "Project B" for class definitions?
version info:
PhpStorm 2017.3.6
Build #PS-173.4674.46, built on March 15, 2018 ...
I'm new to Mercurial and MercurialEclipse, and I think I'm not quite understanding this:
After I pull from the central repository (with Update After Pull selected), it is my understanding that all files are loaded form the central repo to my local repo. However, after I pull, I'm seeing the following:
Doesn't the star icon indicate that there are differences between my local copy and the central copy?
What am I missing here? How do I make sure that my files are the most recent copies?
Try right-clicking on your Eclipse project and select Team --> Refresh Status. I often have to do that for the status icons to be updated.
Edit: if you want to override all local changes, select the checkbox "Clean update (override local changes)" in the Pull dialog of Eclipse.
When you update it merges the local changes you have with the changes in the revision you are updating to. In the update dialog if you select the "force" checkbox it will revert any uncommitted changes. Other ways to remove your local changes are updating by right clicking on a revision in the history view and selecting "switch to", or use the "revert" dialog.
In Sublime Text (2 & 3) I find I accidentally remove all folders from the project when I don't want to (this option is poorly placed in the menu, with no obvious undo or warning and is arguably similar to a 'clear' button on a form).
I often have many folders open in a project each one a leaf in the folder tree structure, which is my workflow, so naturally this is a nasty break in my work if it's accidentally triggered!
I would like to know if I can either disable this option or undo it if I accidentally trigger it?
Aside from a backup, a version control system, or a versioning feature on your file system, there is unfortunately no way of undoing the "Remove all Folders from Project" command, because as soon as the command is fired the folders are removed from the .sublime-project file, and the file is saved. However, there is a way to disable the command. The methods vary between Sublime Text 2 and 3, so I'll go over 2 first.
In Sublime Text 2, click on Preferences -> Browse Packages... to open the Packages folder, whose location varies by operating system. Go into the Default folder, and open Main.sublime-menu in Sublime (it's a JSON file). Search for "close_folder_list" and find the line that looks like this (it's line 737 in version 2.0.2):
{ "command": "close_folder_list", "caption": "Remove all Folders from Project", "mnemonic": "m" },
Now, you can either simply delete the entire line, or comment it out by putting // as the first characters on the line. Save the file, then click on the Project menu to see that the option is gone.
If you're using Sublime Text 3, you'll need a workaround to access the Packages/Default folder and its contents, as in this version most of the packages that you would normally have seen in the Packages directory in ST2 are zipped into .sublime-package files and stored elsewhere. However, there's a plugin for that! Make sure you have Package Control installed, then open the Command Palette, type pci to bring up Package Control: Install Package, and search for PackageResourceViewer. Install it, open the Command Palette again, type prv, and select PackageResourceViewer: Edit Package Resource. Scroll down to Default, click on it or hit Enter, then scroll down to Main.sublime-menu and select it to open it for editing. You can now follow the instructions above to find the line containing "close_folder_list" (it should be line 795) and either delete it or comment it out.
If you'd like to keep the menu item, but move it to a different spot, you can do that as well. For example, if you'd like it at the very bottom of the menu, separated by a divider, delete the original line, put the cursor below the "refresh_folder_list" line, and paste in the following:
{ "caption": "-" },
{ "command": "close_folder_list", "caption": "Remove all Folders from Project", "mnemonic": "m" },
so it looks like this:
I'm new to vault and not a huge fan so far, but I need to do something which would be easy in SVN or Mercurial but I can't figure out how to in Vault.
I need to Get a copy of the repository files as they were at a specific version. I've tried listing thei history and doing a get on a version, but that seems to only get the files that were checked in at that version.
How do I get the whole repository as it was at that version?
You can use labels on folders and files to set a "version", then in vault right-click on the folder/files, choose "show labels", and "check out" this label. For more reading, see the vault documentation on labels at http://download.sourcegear.com/misc/vaultpro/help/client/vaultprohelp.html
Within the Vault client:
Right-click on the directory you wish to have in its entirety at a given point in time
"Show History"
Select radio button "View folder history by version"
Make other settings, such as how far back you wish to go, hit "OK"
Mark "Version" you want, select "Get Tree"
The only feasible option will be to overwrite in place, so you may want to change the working directory at this point.