Other people who have asked this question had answers about downloading Vim from Vim.org, but that website doesn't respond.
Are there other ways to use Vi on Windows?
It's pretty simple to set up vim on windows, although I just tested and the download seems to be surprisingly slow, as if vim.org is experiencing a lot of traffic right now.
If you are having trouble getting the download from https://www.vim.org/download.php to work, there is a list of mirrors that you can try.
Once you get the windows installer, use the 'full' installation type option for best results.
You can download from here, it's working
Related
Do you know ATOM? It's developed by the GitHub's community:
A hackable text editor for the 21st Century.
So, I have used it recently. It's so very nice, dude! But... I've got stuff to solve on it: how do I use FTP/SFTP connection in active mode? Yes, I have found no package able to do it. I have already tested these ones:
remote-ftp (https://atom.io/packages/remote-ftp)
sftp-deployment (https://atom.io/packages/sftp-deployment)
remote-edit (https://atom.io/packages/remote-edit)
remote-sync (https://atom.io/packages/remote-sync)
Ideas? Tips? How-tos? Advices? Argues?
I would like to start programming in GO. As I am a Windows user, I understand that it possible to do so using the GO plugin for NetBeans.
Until now, I have written GO programs in text files and run them using the command prompt, but I prefer to use another platform/environment so I would be able to debug the programs.
The code examples in this forum are syntax highlighting and seem to be taken from an environment like Visual Studio. Does anyone know about the environment?
I would appreciate a simple solution. Thank you! :)
IDEs built specifically for Go and still actively maintained:
LiteIDE: http://code.google.com/p/golangide/
Portable and fast with build in debugger
GoWorks: http://tunnelvisionlabs.com/products/demo/goworks
Based on NetBeans 7.3, standalone application or NetBeans plugin
Googling you can find several IDE, for instance:
http://go-ide.com/ or
https://code.google.com/p/goclipse/
You may find this question gets closed as it's quite subjective, and a FAQ. However, the simple answer: from your description, it seems likely that you would be comfortable with goclipse.
More complete answer: there is no "one true environment" for Go development. The code examples you see here are coloured using Stack Overflow's syntax highlighter, and were submitted in plain text. You'll probably find highlighting and utilities available for most major editors. For example, I use Vim which has a plugin to run gofmt on the current buffer.
I believe some Windows users are fond of Sublime Text 2's GoSublime plugin. A more complete list of development tools can be found here.
You don't really need an IDE to develop using Go. I'd encourage you to spend more time working with a good editor and the command line. Getting to know the tools already distributed with the language is essential IMHO (go, godoc, gofmt). See also Debugging Go Code with GDB.
What is the simplest (to install and use) git client for Windows nowadays?
msysgit and TortoiseGit / GitCheetah
Apart from others have already said, there is also SmartGit.
msysgit is, like everyone else said, wonderful.
You should also look into Git Extensions for visual studio integration, which I find I can't live without.
I just use the one in Cygwin, although many people are looking forward to msysgit once its out of the preview stage. If they make it a no-brainer to install (like in Cygwin), it would be nice.
I had serious issues with negotiating SSL connections with msygit+putty. It's so much easier on cygwin. I even wrote up a guide on it. See Windows Git Tutorial: Cygwin, SSH and Projectlocker.
I intend to use GitHub with Git Extensions and possibly integrate with FogBugz (optional).
Looking at the download page and reading some rather technical half related questions I wanted to see what you thought would be better to install on Windows 7, given I want to integrate with Visual Studio 2008 (thinking this would be through GitExtensions).
A straight answer (msysGit or Cygwin?) between the two would be great but any more no brainer advice on starting out on GitHub would be welcome, or if indeed I've missed the mark entirely (does it matter which?). Will be importing from Subversion.
Cygwin's was the officially recommended one last time I checked, but I think msysgit might have caught up now. I'm using TortoiseGit with msysgit, and it seems to work fine. Recommended.
In my experience, Cygwin is much better: Windows Git Tutorial: Cygwin, SSH and Projectlocker.
If you used TortoiseSVN with Subversion you might want to take a look at TortoiseGit, TortoiseSVN's Git version.
Git Extensions requires msysGit. The "Complete" installation has msysGit and KDiff3 packed with it.
As for the versus, the only major difference I know of is that msysGit doesn't support git-daemon, yet. Since you're using GitHub, this shouldn't affect you much.
Never found the previous options that great for Windows and had used mercurial for quite some time instead.
Now GitHub have done github:windows and after just a little use it is very impressive. It's a well thought out product and think will greatly extend GitHub usage on windows.
I'm unclear on the difference between the functioning of a plugin vs
an extension.
For years, I've written a plain old NPAPI plugin. It lived in /Library/
Plug-ins on mac and somewhere similar on a PC. With Firefox 3.6, it
stopped working. Looking around, I see this:
http://blog.mozilla.com/security/2009/11/16/component-directory-lockd...
which I figure might be the problem, so I try to turn my plugin into
an XPI, but this turns it into an extension.
I install it, and it STILL doesn't work, but now I don't know if it
doesn't work because extensions are a different beast than plugins,
and so what I did makes no sense at all, or whether it's because of
whatever the underlaying problem was before is still around, and so
what I did was a waste of time, and didn't actually address the
problem...
Can anyone give me some guidance here?
thanks.
The answer is "it's because of whatever the underlaying problem was before is still around". The lockdown post clearly states that you'll have problems only if you put your files inside Firefox.app/.../components (if you mentioned this link in your original post, you wouldn't have to try and make it into XPI).
The relationship between extensions and plugins is: an extension may include plugin(s), among other things. You can install plugins (without making them into an extension) in Firefox.
As for your original problem, unfortunately I have no idea why it doesn't work. I'm not well-versed with debugging NPAPI plugins and the only bit of information you shared is that it doesn't work in Firefox 3.6 :)
As a first step, does it appear in about:plugins or in Tools -> Addons?
You can install a plugin as part of an extension (optionally using an XPI) if you want.
The reason that your plugin stopped working in Firefox 3.6 is almost definitely that Firefox 3.6 stopped supporting the XPCOM method of providing a scripting interface. Most likely, your plugin loads but you can't talk to it in javascript.
For more information, look here: http://colonelpanic.net/2010/01/firefox-3-6-has-removed-support-for-xpcom-plugins/
Also, if you need to update it, you might consider using FireBreath, which extracts a lot of that complexity away from you.