The docs say all I need to do is add this:
[extensions]
progress = # shows progress bar for certain tasks
but when I try to clone this repo it doesn't let me because the extension can't be found. It says it's packaged with 1.5 and later and I'm running 1.9.2:
> hg --version
Mercurial Distributed SCM (version 1.9.2)
(see https://www.mercurial-scm.org for more information)
Any ideas on why it's not loading?
The problem is coming from the "comment" you added on the line. According to the documentation :
Lines beginning with # or ; are ignored and may be used to provide
comments.
You can't put a comment like this where you did. Just replace your config with :
[extensions]
# shows progress bar for certain tasks
progress=
And everything will be fine.
Secondly, as I understand you have activated the extension on the server side ? This extension must be activated on the client side.
Related
I am playing around with phpstorm and somehow I activated version control. I don't need it. Now all my tabs are different: orange text on gray background. All files in the file view are orange. How do I disable version control?
Go to Settings -> Version Control and remove the folder from which you would like to remove version control tracking (coloring tabs etc.) It will naturally not remove version control from your project (as in deleting the .git/ folder for instance).
The ultimate way is to disable all version control plugins (under Settings -> Plugins): CVS Integration, Git Integration, GitHub, hg4idea, Perforce Integration, Subversion Integration. After restarting PhpStorm Settings -> Version Control tab will be gone.
Note that this will disable version control for all of your projects.
You can just remove vcs.xml from .idea folder and then restart PhpStorm
In phpStorm 2022.1.3+, go to
Preferences > Version Control > Directory Mappings
Then remove the directories you don't want to watch, as Greg suggested.
Go to Settings -> Version Control and remove the folder from which you would liek to remove version control.
I have not enough reputation to +1 Greg's answer or comment, but... for those who are interrested : the same goes for Webstorm.
I had this problem and I used from 2 of notes in these answers in these page together.
As Greg has mentioned in one of replies, your git repository is in .git sub directory inside directory that you want to manage it with version control system. When you define a git repository, PhpStorm automatically generate it and with creating this sub directory, it adds a file for handling mapping between itself and version control system. It calls vcs.xml and it's located in .idea sub directory.
It's not enough to remove only .git directory. When you remove .git, you will get an error in PhpStorm every time that you open your project due to not matching vcs.xml for mapping between PhpStorm and git repository of your project. So after removing .git directory, you must also remove vcs.xml files from .idea and now you won't have any error or warning in your PhpStorm.
It doesn't need to restart PhpStorm at all and after this, colors of all of files that was mentioned in questions return to normal colors in PhpStorm.
My PhpStorm ver7.0 doesn't show line status in editor (added lines, modified line, deleted lines). How can I show them (I installed Tortoise SVN and checkout my project)?
Please make sure you have enabled version control for the project directory in Settings | Version Control, just map the project root to Subversion.
I'm using IntelliJ Ultimate 11.1 with the bundled HG plugin. When I change a file it appears in the changes view but disappears when I switch to another app. TortoiseHG still sees the change, i.e. 'hg status' shows the files, but IntelliJ just doesn't show it.
I have tried changing the configuration options but without success.
The solution was setting IntelliJ to monitor the repository root and not the source code root.
I had just barely gotten the Mercurial-Reviewboard plugin working with TortoiseHG 2.4.2 when I upgraded to TortoiseHG 2.4.3 and it stopped working.
It's now throwing the following error when I click the "Post Review" button.
"postreview plugin version 4.1.0"
"'module' object has no attribute 'findoutgoing'"
I've tried many different branches of the plugin and have had zero luck. The one I have right now is Fredrik Haard's and can be found here:https://bitbucket.org/haard/mercurial-reviewboard
Unfortunately he hasn't updated it in some time.
I've tried looking through the source for the plugin but know next to nothing about Python in general and Mercurial plugins in specific.
If anyone can help in any way I'd greatly appreciate it.
I had this same error "'module' object has no attribute 'findoutgoing'", using the following:
TortoiseHG: 2.4.3 (with Mercurial-2.3.2, Python-2.7.3, PyQt-4.9.3, Qt-4.8.2)
Reviewboard: 1.6.13
Mercurial-reviewboard plugin: windix-mercurial-reviewboard (4.1.0) from 2012-08-30 and with the following change in reviewboard.py at line 400:
self._api_post('/account/login/', {
instead of
self._api_post('/api/json/accounts/login/', {
I only have a local repository, towards which Reviewboard points using the path on the disk.
The problem was fixed as soon as I added in the .hg/hgrc file of that repository, the following:
[paths]
default = http://localhost:8003
where 8003 is the port I configured for the same repo, in the same file inside that repo.
I have two more local repos, in the same situation - no remote base - configured for 8000 and 8005 respectively, I am now able to post review requests from the TortoiseHG user interface for all of them (after having added for each of these repos, the [paths] section and the default url like above).
I hope this helps!
While still having some problems, 'my' fork works for me right now although there are encoding errors for source files that are non-ascii. If it does not work for you (commit from 2012-24-10), and the problems you have are not related to encoding (working on those), could you please describe what is happening/provide log messages?
I have installed Mercurial from the Ubuntu package repository. However I don't know how to enable extensions (q* commands). How should I do that? The help shows that
enabled extensions:
style (no help text available)
I want to enable mq and hgk.
Enable extensions in hgrc.
extensions
Mercurial has an extension mechanism for adding new features. To
enable an extension, create an entry for it in this section.
If you know that the extension is already in Python's search path, you
can give the name of the module, followed by =, with nothing after the
=.
Otherwise, give a name that you choose, followed by =, followed by the
path to the .py file (including the file name extension) that
defines the extension.
...
Example for ~/.hgrc:
[extensions]
# (the mq extension will get loaded from Mercurial's path)
mq =
# (this extension will get loaded from the file specified)
myfeature = ~/.hgext/myfeature.py
http://www.selenic.com/mercurial/hgrc.5.html#extensions
You can also enable an extension without editing the hgrc, if you want to do it one off. [Source]
hg --config extensions.histedit= --help
The documentation of both extensions shows how to enable them : MQ, Hgk.
The usual way to enable an extension is to add a line to your .hgrc (or Mercurial.ini on some Windows system). It is explained in the hgrc documentation.
In your following case, add this to your configuration file :
[extensions]
mq =
hgk=
You can put it in your global configuration file or the repository one, depending if you want to have the extensions activated in every repository or just a specific one.
The output of hg help extensions starts with
Using additional features
Mercurial has the ability to add new features through the use of
extensions. Extensions may add new commands, add options to existing
commands, change the default behavior of commands, or implement hooks.
Extensions are not loaded by default for a variety of reasons: they can
increase startup overhead; they may be meant for advanced usage only; they
may provide potentially dangerous abilities (such as letting you destroy
or modify history); they might not be ready for prime time; or they may
alter some usual behaviors of stock Mercurial. It is thus up to the user
to activate extensions as needed.
To enable the "foo" extension, either shipped with Mercurial or in the
Python search path, create an entry for it in your configuration file,
like this:
[extensions]
foo =
You may also specify the full path to an extension:
[extensions]
myfeature = ~/.hgext/myfeature.py
So just add
[extensions]
mq =
to enable the MQ extension.