Open gfranz opened 12 years ago
I am getting a unable to open packages/Coldfusion/ColdFusionCFC.tmLanguage error when using the Git install method. I did have the package manager of the plugin installed previously, and perhaps I need to do some manual clean up work? Thanks
for me the problem went away after I restarted the machine.
On 10/17/2013 1:31 PM, spills wrote:
I am getting a unable to open packages/Coldfusion/ColdFusionCFC.tmLanguage error when using the Git install method. I did have the package manager of the plugin installed previously, and perhaps I need to do some manual clean up work? Thanks
— Reply to this email directly or view it on GitHub https://github.com/SublimeText/ColdFusion/issues/106#issuecomment-26549332.
Igal Sapir Railo Core Developer http://getRailo.org/
OOPs forgot this is ST3 (Build 3047) on Win 8 64.
I'll give that try thanks.
No luck on getting the development branch to work with ST3 so far.
So I tried using the portable version and I get no errors but also the plugin is not seen at all.
Got it working with the portable version but, I had to put the Coldfusion folder in
Hand installing the Dev pack is the only thing that has worked for me.
Same problem... no greater than character - Sublime Text 3, Win 7. My install method: I unzipped this package into the C:\Users\UserName\AppData\Roaming\Sublime Text 3\Packages folder (I found this folder by selecting "Browse Packages..." from the Preferences menu. Can someone point me to specific NEWBIE install instructions? What does "install directly from git" mean and how do I do that? Do I need to install git and then install the git package? Sorry, but this is confusing to me.
The easiest method is to download this zip file, and use it instead: (no git necessary)
https://github.com/SublimeText/ColdFusion/archive/development.zip
This gets you the "development" branch from github as a zip file - which is what you need for Sublime Text 3.
Thanks! I manually installed the dev build and the problem with the closing ">" went away. May I suggest that you clarify ST3 install instructions.
As of 8/17 - This is still a problem, even with the dev branch, which I have installed. It doesn't happen all the time, but I still run into the issue. Quitting Sublime Text 3 and then restarting fixes the problem. Weird.
Unfortunately it doesn't happen on my build @redtopia so tell me when it happens. I made some updates right now but I suspect it's being caused by Sublime bailing and not loading the coldfusion-plugin.py file when it encounters something it didn't expect. I just started doing some CF again so I'll try to make some more updates in the coming weeks.
Not sure, but it might happen after I wake my machine up... sometimes windows reports some sort of funky process error, and I think it might be sublime, but I'm not sure.
This is my first ever post here so am not sure how much information you will need so here goes. I am running OS X mavericks with ST3 3065 I have package control installed and I manually installed coldfusion via the git instructions, I have tried the uninstall of the plugin option I made sure I removed all record of it, I tried the touching the file suggestion earlier, that didnt work. I have restarted my machine a couple of times. I am still not able to to use the > key at all, the only way I am able to even get the language to show up in the list is to include the ColdFusion.sublime-package file that I had from a previous attempted installation. I also tried copying the folder from Contents/MacOS/Packages/ into the Installed packages folder to see if that would work and nothing happened, so does anyone have any other suggestions/instructions on how to do it properly if I have done it wrong or am I to resign myself to just doing copy paste?
using the dev package solved this problem for me...Thanks for having this discussion. I am enjoying Sublime with CF :)
Oh joy! This works. Thanks for the tip. Finally I can edit these files at work with syntax highlighting.
I've been struggling with this issue for a couple days. None of the above solutions worked for me. I've removed and reinstalled different versions and builds of Sublime, removed and reinstalled the package via git and zip; checked out different branches, created new branches to test... all without success.
By using sublime.log_commands(True)
in the console, I could see that it was calling the close_cftag command. I changed the command name in Default.sublime-keymap and added some messages and new commands to coldfusion-plugin.py. No matter what, any commands defined in coldfusion-plugin.py would not run and no error was thrown. I created a new .py file in %APPDATA%\Packages
and my "Hello, World!" command ran just fine when mapped to the ">" key. That's when I realized there might be a path issue.
It turns out, I had been placing the ColdFusion package in the wrong folder. I assumed the "User" folder was where I (the user) was supposed to store my packages so I was putting it here:
%APPDATA%\Packages\User\ColdFusion
What's confusing is that the syntax highlighting works fine for cfm and cfc files when the package is placed here so I just assumed I installed it properly. (@atomi - you may be able to replicate what people are experiencing by dropping the package in this folder)
As soon as I moved the package to %APPDATA%\Packages\ColdFusion
everything worked just fine.
tl;dr - make sure package is installed here: %APPDATA%\Packages\ColdFusion
edit: Going back through the thread, I see that most have not made the mistake I did. Oh well, hope this helps someone.
@samwscott THANK YOU
This has worked for me on the various ST3 dev builds on my Win 7, 8.x, and Mac laptops. Thanks!
can you have a look at my thread then robred and tell me what I am doing wrong please? :)
I had this problem (Windows 7, Sublime Text 3 demo) when the package was in a folder named %APPDATA%\Sublime Text 3\Packages\User\ColdFusion-development\
. I renamed the folder to just ColdFusion
, restarted, and I was able to type >
again.
As @Lukenickerson said, the folder has to be named ColdFusion or the > key stops working as a side effect of some paths not working anymore. I've tried modifying all the hard coded paths I could find, but even after that there must be some kind of linkage issue with coldfusion-plugin.py because it just doesn't work without keeping the folder as "ColdFusion". I was trying to organize my plugins by cloning them into folders with a prefix that indicates what they are and '>' stopped working :persevere:
This happened to me today and was fixed by re-cloning the Development branch of the git repo.
I had noticed that the console had other warnings going on when I tried to run the close_tag
command in the console. *I mention it as a side note since I'm not entirely sure if that was the culprit, but after a re-install of the development branch and removal of the folder from my project that had the offending files, have since gone away. The warnings were related to the contentbox api docs. I'll restore those files and see if sublime freaks out about them again. I also wonder if some other package or some other internal sublime text issue like I just mentioned might have been preventing the Coldfusion plugin from functioning properly.
I ran into this issue today after downloading ST3 beta and then installing the ColdFusion plugin from github.com. I used the .zip download, unzipped it and placed the inner directory Coldfusion (renamed from Coldfusion-master) into the Packages directory. I launch ST3 and at first it only exhibited this issue with not being able to type the greater-than symbol. But then it started auto-deleting the plugin directory from the Packages directory after launch of ST3. I would paste it back in there from my Downloads directory where I had unzipped the .zip file and renamed it. But repeatedly I would launch ST3 and watch it vanish.
I finally resolved the issue when another developer here said he used the git method of installing and has had no issues. So I installed git (the command line version) and then used the git method to install the plugin. Now it not only doesn't delete itself but I can type the greater-than character! :) Just thought you all should know my experience with this issue. So bizarre.
Did you get a zip of the development branch?
I don't know... I just grabbed whatever is in the right side bar to Download .zip.
The read.me says to grab the development branch otherwise in my experience a lot of things, such as this, don't work as expected.
-tim
On Apr 2, 2015, at 1:17 AM, "Bruce H." notifications@github.com wrote:
I don't know... I just grabbed whatever is in the right side bar to Download .zip.
— Reply to this email directly or view it on GitHub.
And indeed, in this very ticket, I gave a direct link to the development branch zip, in June 2014. Here it is again:
https://github.com/SublimeText/ColdFusion/archive/development.zip
Think I know what's going on with this. It appears there are currently 2 default key maps in the Default.sublime-keymap. I removed the "move" keymap and it's now working again.
{ "keys": [">"], "command": "move", "args": {"by": "characters", "forward": true}, "context":
[
{ "key": "setting.auto_match_enabled", "operator": "equal", "operand": true },
{ "key": "selection_empty", "operator": "equal", "operand": true, "match_all": true },
{ "key": "selector", "operator": "equal", "operand": "meta.tag"},
{ "key": "following_text", "operator": "regex_contains", "operand": "^>", "match_all": true }
]
},
// Auto-close ColdFusion block tags
{ "keys": [">"], "command": "close_cftag", "context":
[
// selectors aren't working as I expect, we'll just use general scopes here
{ "key": "selector", "operator": "equal", "operand": "text.html.cfm, source.cfscript.cfc"},
{ "key": "following_text", "operator": "not_regex_contains", "operand": "^>", "match_all": true }
]
},
Actually, it looks like this is the main part of the issue in the first key map.
{ "key": "selector", "operator": "equal", "operand": "meta.tag"},
{ "key": "following_text", "operator": "regex_contains", "operand": "^>", "match_all": true }
I am also having this issue, but with ST2 (not 3). Got it installe don several machines with same problem on all of them. Doesn't even work in a blank file. Have tried re-installing, to no avail.
If I use the "CFML (do not use)" syntax, then it works.
nathanstandford2 hit it on the head. I tried all the other methods above with st3 and nothing seemed to work. I commented out that second key mapping block and the > key is working great.
If you download the .zip file of the development branch (instead of cloning with git) make sure you rename the package from 'ColdFusion-development' to 'ColdFusion' when you install it.
This fixed the issue for me. Another symptom that will tell you a rename is needed is if you browse to the plugin default settings through the Preferences menu and the file is blank and prompts you to save it when you close it.
Using Sublime 3 portable version.
Installed development branch, however I am still unable to type the ">"...please help!!
still have that issue on version 2
On Wed, Aug 26, 2015 at 4:59 PM, zadams125 notifications@github.com wrote:
Using Sublime 3 portable version.
Installed development branch, however I am still unable to type the ">"...please help!!
— Reply to this email directly or view it on GitHub https://github.com/SublimeText/ColdFusion/issues/106#issuecomment-135079106 .
Russ Michaels Blog: www.michaels.me.uk skype: russmichaels
My other sites/projects www.bluethunder.co : SME hosting solutions www.cfmldeveloper.com : ColdFusion/Railo developer hosting www.cfsearch.com : ColdFusion search engine www.cflive.net : Live CFML console/testing tool
Just wanted to say I resolved by issue by going to preferences > browse packages and deleting everything in the ColdFusion folder and dumping the contents of the development package (https://github.com/SublimeText/ColdFusion/archive/development.zip) in it. I restarted Sublime Text 3 for good measure.
Until then I was just copying and pasting the > to get around it. However, I am glad to have the issue resolved.
I resolved this problem by restarting Sublime Text.
Funnily enough in the CFML (do not use) syntax it works. Just in the ColdFusion Markup and Coldfusion Component Syntax it does not work.
HELP!
Gert