Pyzo will not start after fontcolor change - installation

I am currently using Pyzo and changed its font and background color according to the instructions on their website (http://www.pyzo.org/pyzo_themes.html) by changing the init() in the base.py file. Everything was fine until I wanted to change the settings back to normal. When I try to open any .py file Pyzo gives me the error
"Error loading file: local variable fore1 referenced before assignment".
On closing the error message, the Shell just keeps warming up and nothing happens. On the left side where the editor would have been, there is a small white box with a smaller yellow one inside.
Opening up Pyzo on its own does not give the error, but the same problem with the Shell and editor.
I tried:
changing the settings in base.py manually to their default value
copying the backup file I made before the changes back into the directory
uninstalling Pyzo with IOBit Uninstaller to catch all hidden files and reinstall it (about 10 times already)
I thought reinstalling it would resolve the matter but obviously there must be a different issue here. I really hope someone had the same problem, thanks in advance for any help!

Related

VSC Live Server is driving me nuts

I don't get how this thing is so buggy on my mac ugh
Firstly it is such a hassle to open cuz it won't open in chrome without typing in the IP manually (is there still no solution besides changing settings that won't work)??
But most importantly, my CSS file is just not loading...
I did everything already from restart to reinstall, etc.
And when I open the file from Chrome the code does works so it's not my link...
Does anyone have another solution for the CSS to load, please?
To give some feedback (after a LOT of crying and tinkering around)...
I think fixed the CSS file not loading on Live Server? It seems that the extension loads the resources as if the folder the HTML is in is the root, so I had to use a relative path (which took a WHILE to get to its liking as well...)
Still not opening without a fuss though haha...

Code::Blocks stopped working suddenly and doesn't open any more

enter image description here
Tried installing and re-installing but of no use.
Every time it says Keyboard Shortcut Conflict for Ctrl+P. But I can't do anything about it as it doesn't open up. I do have keybinder but I don't know how to sort this out.
Inserted Screenshot of exact error message showed. I even tried installing nightly builds but the same error message pops up. every time.
Deleting the user files (only the "keybinding" files) in the directory below then restating CodeBlocks will help if the problem is just because a key conflict:
directory: C:\Users\YourUserName\AppData\Roaming\CodeBlocks\
Depending on the CodeBlocks version, the file names may be something like; cbKeyBinder10.ini, default.cbKeyBinder10.ini, default.cbKeyBinder20.conf
Important note: To be on the safe side, instead of deleting those files immediately, just rename their extensions as .ini_bak or .conf_bak. If this procedure solves your problem, you can, then, delete the backup files. If not, you can rollback your changes by returning the extensions back to their originals.

Xdebug with PHPStorm 8 -- opens WRONG file at non-existing breakpoint

I am having trouble using Xdebug with PHPStorm. I have searched Google, etc.
I have Xdebug setup on a remote host with my local files mirroring the remote host. I am using the Xdebug Chrome extension.
When I run the debugging through PHPStorm, it OPENS a file and shows a blue-highlighted breakpoint that does NOT exist at that file. It will stay there until I hit "resume" multiple times until I get to the file I actually want to debug. VERY annoying because then the session on Chrome timesout, so I can't debug.
I do not see any code that says xdebug_break(); and I never added a breakpoint to that file. In other words, there are no red markings at the left of the line numbers.
What is going on and how do I fix this? Has anyone else come across this problem?
I have tried skipping and ignoring the file ... still does not work! Yes, I have also viewed breakpoints through a separate window and it does not show the breakpoint that apparently exists.
Check the configuration on PHPStorm stop at first line property and disable it
After that go to Run >> Break at first line in PHP scripts
Try turning it ON and OFF few times. Sometimes it is get stuck in between: showing OFF but in reality it is ON.
This is a well known issue Read: https://youtrack.jetbrains.com/issue/WI-17389
I was having the same problem with my PHPStorm/xdebug config. It turned out I had the path mappings wrong when I mapped the root of the local file directory to the Absolute path on the server - Settings->Languages and Frameworks -> PHP -> Servers.
I fixed the mapping and the system is behaving predictably once again.

Adding LESS Extension to Dreamweaver CS5.5

Work gave me a new Macbook Pro yesterday and I'm having a hard time getting Dreamweaver CS5.5 to work with my LESS files. At first, I was getting an error saying that it couldn't open the filetype, so I hit the Adobe help areas and user forums and found the solution about editing Extensions.txt and MMDocumentTypes.xml. So now I can open the files from my local files side panel, but not from File -> Open. And despite having it listed as a Style Sheet extension, code hinting and coloring isn't working. A bizarre twist is that now if I take out my edits to those files, DW still opens the LESS files without an error. Anyone have any ideas how I can get this fully operational?
Here are a couple of the articles I found in my research and followed as best I could:
http://help.adobe.com/en_US/dreamweaver/cs/extend/WS5b3ccc516d4fbf351e63e3d117f53d6108-7fda.html
http://helpx.adobe.com/dreamweaver/kb/change-add-recognized-file-extensions.html
From what I tried today, it kind of makes sense to me now. I have it working on CS5. To get started, you should show all files on your computer. Spotlight (OS X) makes things super easy to find all instances of those files. Once you find it, CMD + R will reveal the parent folder where the file resides.
The "Extensions.txt" handles whether or not DW can open the file from the modal window/program menu. This file is located in 2 places and you should edit using "text edit" or another baside editing program:
USERS/library/Application Support/Adobe/Deamweaver
CS5/en_US/Configuration/Extensions.txt
Applications/Dreamweaver/Configuration/Extensions.txt
To do that you just need to declare a new type:
As part of the "all documents" list you need to add your SCSS,LESS
extensions
As part of the "stylesheets" list you need to add your SCSS,LESS extensions
CSS,SCSS,LESS:Style Sheets
The second file you need to EDIT, is under the folder "DocumentTypes" in CS6 I believe that folder has moved to:
USERS/library/Application Support/Adobe/Deamweaver CS5/en_US/Configuration/
However, in CS5, I found this folder in Applications/Dreamweaver/Configuration/
From here if you edit "MMDocumentTypes.xml" this file it should explain how those extensions you previously defined in "Extensions.txt" should behave. (Again, use a basic text editor).
I think somewhere on line 140 or so, you'll see the following:
<documenttype id="CSS" internaltype="Text" winfileextension="css" macfileextension="css" file="Default.css" writebyteordermark="false" mimetype="text/css" >
From here add "scss,less" to the 'winfileextension' and 'macfileextension'. Because you're on a Mac, you probably want to make sure its filled out in the 'macfileextension' attribute.
The result should look like this:
<documenttype id="CSS" internaltype="Text" winfileextension="css,scss,less" macfileextension="css,scss,less" file="Default.css" writebyteordermark="false" mimetype="text/css" >
Cheers!

Dimitre Novatchev's XPath visualizer help

I want to try what looks like a really cool tool. I've dl'd the FF version from http://www.huttar.net/dimitre/XPV/TopXML-XPV.html.
I open XPathMain.htm in FireFox, Browse to the provided test1.xml file, click Process File, with the default //* in the XPath window. In FF, I get this:
[Exception... "Access to restricted
URI denied" code: "1012" nsresult:
"0x805303f4 (NS_ERROR_DOM_BAD_URI)"
location:
"file:///Users/doug/Dev/XPV-FF/XPathMain.htm
Line: 43"]
I also opened it in Safari, followed the above, and nothing happened, when I clicked Process File.
Once I get it working, what am I expecting to see? I assume I will see the xml file in the big window with selected nodes highlighted?
I'm on OS X 10.6.6 and FF 3.5.16. Thank you.
I experienced this error also and after a bit of trial and error, I resolved the problem by placing my .xml file in the same directory as XPathMain.htm. It then immediately rendered in the lower window after selecting the Process File button.
Moving the authors.xml file outside the XPV-FF/ generates the same error. Perhaps this is the same origin policy type security?
I am not sure what could be an issue-- I cannot reproduce the reported problem.
Just downloaded and installed FF 4, opened file:///C:/Temp/XPV-FF/XPathMain.htm
and then specified:
C:\Temp\XPV-FF\authors.xml
The XPV works as expected.
Please, try to work with the file authors.xml that comes with the XPV and is in the same folder as the XPV starting page. If you can work with this file, this definitely means that there is a permission problem with the file that has the reported issue.

Resources