I've been using Liclipse for a while, after having supported it in the IndieGogo funding drive a few years ago. However, there are a number of issues that I'm always hopping will get fixed in the next update, yet I haven't found any way to cleanly apply said updates.
The Help -> Check for Updates menu doesn't ever show updates to LiClipse, which means the only way I've been able to do it is to download a new copy and overwrite my old one. Unfortunately, this breaks all my existing plugins, so I have to re-install said plugins, which is a petty annoying pain.
I'm using OSX El Capitan, which I think is why plugins get blown aaway upon update? They're all stored in the .app, which gets replaced entirely.
There's a section named "Updating Native Install" in http://www.liclipse.com/download.html which has instructions on how to update the native install (as a note, there really was a bug in the updating of LiClipse through Check for Updates which was fixed in the 4.x version).
Related
Yeah due to Christmas I went over to my mother but still wanted to improve my skills in rust. For one day everything just worked fine, but now vscode doesn't underline the errors.
https://imgur.com/a/LxAe8f6
here a pic how it looks, I have rust-analyzer installed. It should underline something because the method doesn't return. anything.
Do you have any idea how to get rid of the Issue I already reinstalled twice.
Are you in main.rs?
If you are in a module file or lib.rs you need to import the files with use.
Other than that, I don't know, you could try enabling
"rust-analyzer.trace.extension": true,
In your settings.json file and checking your log output.
I had some issues after installing the latest version so you may want to head to the rust-analyzer extension page, click the drop-down arrow next to Uninstall and selecting Install older version, I just used a version that was 11 days old and it seemed to fix things.
EDIT: There is an issue showing VSCode downloads the wrong/old version.
I am working on an ASP.NET application in VS2010; the repository is still VSS-2005. I am going to abandon the changes made to one of the pages and revert back to the version that existed two checkins ago (which is the current production code). My problem is that I haven't worked with VSS much and I've never done this particular thing before. I can't find any "How to" literature on VSS that tells how to do it, and when I try to do it using the intuitive thing (do a "Get" on the version I want to revert to), it does nothing.
I can View that older version using Notepad, and so I could check out the page and replace the code with the Viewed Notepad version, but this doesn't seem proper somehow.
I've been wondering about the Rollback button, but when I click it, it gives me an ominous message that I am not sure I like: "Rollback cannot be undone; some versions will be lost irretrievably! Continue anyway?"
Well, apparently there are no SourceSafe gurus out there, so I'll answer my own question. I bought a book! And it told me how to do it.
Overview:
Check out the current version manually
"Get" the version we want to revert to
Check in the older version as a newer version
Details:
Check out the current version, then use the View History command to show the History dialog and select the version that is desired to be reverted to.
After selecting/highlighting this version, click on the Get button. The Get dialog shows where the specific file version will be placed along with several options. By default the path in the To text box points to the file in our workspace, which is what we want. Don't select the "Make writable" option since the file in question is already under source control. Leave everything as defaulted, and click OK. In the next dialog, choose "Replace". SourceSafe gets the older verison and overwrites the one in the workspace.
Now that you have the older base version, all you have to do is check in the version and obtain a new version that is identical to the old one.
I got this information from the book "Visual Source Safe 2005 - Software Configuration Management in Practice" by Alexandru Serban, published by Packt Publishing Ltd. I bought the book used, but found you can still get it new from the publisher for a lot less than the list price -- $20 less! I don't know who might need a book about an obsolete source control system, but don't pay full price, get it from the publisher direct! Amazon charges the full list price on new copies (astonishing).
Actually quite a simple issue. I have been using a slow laptop to develop on VS2012, and I setup a screamer to develop on now. No change in versions, etc., just doing it all on a different machine.
To be honest, I haven't even copied the Projects folder yet, as I'm not sure if there wold be project-specific options that would be reset/broken.
To be clear, the new 2012 is Ultimate, and I haven't even tried to migrate. There have been a LOT of options/features added to my existing projects & solutions, so it may not be as simple as copy/paste the Projects folder.
What are your thoughts?
#Peter and #JohnnyHK,
You both were right. I was putting this off on a new machine for fear that I'd need to remember a ton of things I hadn't documented in the Solution (and projects under it-about 20).
So I was already using subversion on the old machine, so I added VisualSVN/Tortoise and checked out a copy of the solution to the new Projects folder. There were like 350 errors & more warnings! Yikes!
But I went through them very quickly and it is clean now. One thing that I noticed in the process was that VS2012 is a little 'broken' when it comes to project (on-web) references. NuGet was actually amazing in that as soon as I fired up the Package Console, it went along, finding & installing all the packages & dependencies! :)
I enabled Show All Files, then opened the References tree node, and noted the ones with little yellow "X"s next to them. In the good side, ones that were not needed (I added them, but created just clutter) were good to see & delete. BUT, there were mostly errors from references that had references to DLLs that were actually in the right place, and when I left clicked on the reference with the error icon, the error would simply go away. Weird, but preferable...
The strangest ones were reference to DLLs that were where they were supposed to be (I'd make a .\lib directory in the project, a la *NIX style, and throw all DLLs for that project in there), BUT I had to delete the reference in error (even though the project was pointing to the right file/location) and then re-browse for it, adding it again, and all errors went away.
All in all, I was pretty impressed with the ease-even with the weirdness-it went. Once I saw how the references were broken, I just went into each project & treated each one. Let me be clear for anyone doing a mass WPF migration: If I had started with the first project and worked to the end one, and ONLY fixed the References issues, I would have been done in 5 minutes-includes time for NuGet to auto-load.
I will not lie; This was the first big migration of a solution to a new machine, and when I saw like 700 warnings/errors, I thought "There goes another weekend!", but I will warn those in this situation to NOT go into source code and try to fix each red underline. You will break things!
Today I tried to made "Code Cleanup" of single file in ReSharper 6.0 (VS 2010). The Code Cleanup dialog did not show up so I tried again.
I then discovered, that the feature is grayed out and when I press hotkey for Code Cleanup, the notification area shows that the "command is not available at the moment".
Even the Code Cleanup settings are hidden. The panel where settings should be shown says that the settings are solution-specific and thus a solution needs to be opened (although it is, however).
All other solution-specific settings and features work, except for Code Cleanup.
I want to avoid re-installing ReSharper or resetting its settings, because otherwise I would need to set it up again (long and annoying work of setting all the options as before re-install).
I am afraid that backing up settings and restoring it again restores the problem as well.
Any suggestions?
Suggestions:
Ensure that the file that you're trying to cleanup is included in your solution.
Try to reopen solution (close and then open again).
Upgrade to 6.1.1, maybe its fixed there.
File a bug report at http://youtrack.jetbrains.com
Both ReSharper 7 and 8 seems to work OK.
I know this is an old answer, but I found a little more insight on this. According to Jerrie Pelser in this blog post from last year, this may have to do with the file being part of a NuGet package. In my case, this was definitely it!
In case of link rot, basically the post mentions that ReSharper will avoid refactoring/code cleaning for files it detects were added as part of NuGet packages. This is similar to how it will not allow code cleanup for generated code.
The title of the question sums it up pretty well. I've downloaded the source for firefox 3.6 and built it (no errors), but when I try to run it, I get a warning that says:
(firefox-bin:2857): GLib-WARNING **: g_set_prgname() called multiple times
I'm not sure what to try now. Any suggestions? Or even a better place to ask this question?
*EDIT - It's not that I only get a warning, that wouldn't bother me. The problem is that the warning is the only thing that ever happens (no firefox windows show up or anything). When I run it from the terminal, that warning shows up twice and then nothing else happens (it just hangs and I have to Ctrl-C it).
Bug in Glib introduced while trying to fix https://bugzilla.gnome.org/show_bug.cgi?id=563627 and, as discussed in that bug, later backed out because of the issue you're seeing. The warning will go away once you get a newer version of Glib.
Quick comments:
It's a warning, not an error. This is not a problem but looks like the library wanted to be used differently. So why worry?
Why did you build it from source? If you want newer packages, I usuaully start with Debian sources and turn those into local packages -- as this incorporates whatever the package maintainers deemed worthy and will be closer to the package you will get at the next Ubuntu upgrade.