As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm looking for a command line program (Windows) or a PHP library that can handle UTF-8 characters.
I've searched SO and I have read these questions:
https://stackoverflow.com/questions/12625/best-diff-tool
Highlight the difference between two strings in PHP
but with no luck.
Thanks for help!
I've end up with prettydiff.com. It is not either PHP lib or a program but it works for what I need.
As luck would have it...
Our Smart Differencer tools handle a huge variety of input encodings. You can define the input encoding as an environment variable, so if you do a lot of compares you might want to write a little script. (We're moving towards allowing this as a command line switch).
These tools are designed to compare computer langauges, and are langauge specific.
There's a version specifically to compare PHP programs.
If all you want is a plain vanilla text diff, this won't be your tool.
[This makes me consider the "trivial computer language" consisting of text lines,
which this tool would do really well. I'll have go build one of these
(really easy with our machinery) just to see what it is like. Stay tuned
to this Bat channel.]
WinMerge can handle UTF-8 (you need to start the Unicode version WinMergeU.exe)
ECMerge internal representation of text is UTF8 (NB: I work for ECMerge). It comes we a command line tool ecmerge-cli (on Windows, ecmerge --cli on Unixes). Calling it from PHP should as simple as any other command line tools. It can be scripted and output whatever you need. Of course it can generate HTML/XML diff reports and patches off the shelf.
It is succesfully implemented as the base for several diff services behind web servers.
Did you try my favorite -- beyond compare?
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I really need to understand how to use git on Windows, but all the guides are too complex. For example, I understand we need to use a command line for git. But when I open a command prompt in Windows using "cmd.exe", where do I go? Do I navigate to the folder where git is installed? What is "git bash"?
Why do all the examples on the Internet have this $ sign in front? How do I add an existing folder to git version control? What does "checkout" mean? I keep hearing about a tool called "powershell". What does it do and how is it different from a DOS prompt?
To use the "git" command I'll probably have to add it to my environment variables so the computer can find it and I get "'git' is not recognized as an internal or external command,
operable program or batch file."
I've never used a version control system for my programming before - I've just saved folders with numbers in front of them so far and I need to use git to publish a project folder I have on Amazon AWS Beanstalk.
I basically just want to add a folder to git and save changes regularly so I have a back up of all the stuff I've done before.
Edit: Is git a single program, or are there many "gits". The first result for "git" in google takes me here: http://git-scm.com/ and yet lots of people talk about something called "msysgit". Is this a different git application?
Edit: I'm looking more at a command line for Windows tutorial. It's here that I'm having the most trouble.
If you want to understand some of the concepts of Git (and only then you can use it effectively), you should read the Pro Git book (available online and for download, or even to buy on paper). This is a really good book, teaching you the very basics you need with good examples, and having sections on more advanced stuff if you want to know more.
The book assumes that you use a Unix-/Linux-like shell (like Bash). Msysgit (a.k.a. "Git for Windows") brings Bash with it, pre-configured for easy use of Git. (And no, there are not many gits, Msysgit is just a bundle that brings some other dependencies of Git which are not usually installed on Windows.)
A shell (also named console or terminal) is in this case a command-line interpreter, just like cmd.exe is on Windows; on the *nix-like systems, there are many more alternatives than on Windows (where one alternative is Powershell), but that's just some side info here.
The $ sign in the examples you see is a typical prompt delimiter on *nix-like shells; on Windows (cmd.exe), you usually have ">" as the delimiter. It has no special meaning and just serves as a delimiter.
What "checkout" means and how you add files and folders to version control, is explained very well in the mentioned book. You also do not need to know anything about version control in general, the book is really written for absolute beginners (in fact, to start using Git it might be an advantage not to know other VCSs).
If you need any help with the stuff that's in the book (or in other tutorials mentioned there, here, or on Google), feel free to drop by the #git IRC channel (more info on the git-scm.com community page, where people can help you immediately and with small questions.
There are a bunch of tutorials that worked for me:
http://www.youtube.com/results?search_query=git+windows&oq=git+windows&gs_l=youtube.3...250.879.0.972.7.6.0.0.0.0.0.0..0.0...0.0...1ac.1.
They show you how to install the various components and then how to use Git with Windows.
Github* has GUI application for Windows (as well as for Mac) which is pretty friendly to novices. You won't get a lot of insight, but this might help you to get up and running.
*git-repository hosting, e.g. place where you can store your repos and sync with them from time to time. It's free and awesome.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have learned the standard c and c++ language. However I don't know how to using system calls and writing programs with processes and so on.So I want to learn programming in the unix/linux environment . What's the step? should I do. Should I learn the shell first.
If you want to program in a UNIX environment, you'll have to first learn your way around it before messing with system calls and stuff. I'd recommend The UNIX programming environment for a healthy introduction to UNIX in general. It's a little dated but still a gem of a book and a must read for any programmer.
If you have Unix/Linux system, you should at least know a bit of shell scripting and its tools, just for the sake of knowing what your startup scripts does or quickly moving around your system (eg using ls, mv, cp etc). other than that, for real programming stuff, you can use a programming language (Python, Ruby comes to mind). A lot of modern programming langauge, like Python, already provides system level APIs. Python comes with a shell itself, so if you are a hard core, you can also use it for your every day tasks. This little example shows you can do directory listing in Python shell
>>> import os
>>> os.chdir("/tmp")
>>> os.listdir(".")
Its the same as typing ls on the command line. how about moving/copying files? Instead of using shell mv and cp,
>>> import shutil
>>> shutil.copy("file","/destiation")
>>> shutil.move("file1","/destination")
IMHO, if you plan to program system/low level stuff, then C/C++ may be what you need, but for normal system administrative or every day operations, a programming language like Python/Ruby (or Perl) would mostly suit you.
I'm in Systems Programming right now, and the professor is giving us a survey of Unix, including system calls and writing simpler versions of existing core utilities.
One source I found very helpful was reading the full source code of the utilities and a system call quick reference. The textbook is Understanding UNIX/Linux Programming and I definitely recommend you pick it up.
We haven't gotten into shell scripting at all, other than using input redirects, grep, and pipes, so I don't know how useful that would be for you at this point.
No, you don't need to learn shell.
Just look for a book or web page describing unix system calls for C.
If you are going to be programming in a "traditional" unix environment (i.e. using a text editor and doing everything from the command line), you will want to be pretty competent with the shell, and very competent with The Editor Of Your Choice (and you have freedom of choice, but if it's not emacs you're going to the bad place...).
But it isn't really necessary to "study" the shell first. Just be aware that the shell provides powerful tools. Then, every time you find you self thinking "There has got to be a better way!", go learn what the better way is.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
When it comes to scripting the Mac, are there alternatives to Applescript? Its API seems awesome, but the language itself, from what I've read so far, seems aimed more at non-programmers.
Insights into this would be greatly helpful.
(At the moment, I'm thinking of writing a tiling window manager for the Mac.
Yes, I know some exist, but this will be open source.
Yes, I know of Xmonad, but it only does X11 windows.)
Thanks!
When it comes to scripting the Mac, are there alternatives to Applescript?
Depends what you want to do. If you want to send Apple events to other applications, yes; for running scripts from OSA-aware applications (Mail rules, folder actions, etc.), not really.
The best technical alternative is appscript (my baby), which is available for Python, Ruby and Objective-C on 10.4+. (There's also a MacRuby version, but I've yet to do a public release of that.) Feature-wise appscript's slightly better than AppleScript and its application compatibility is very nearly as good. Third-party project, so you'll need to install it yourself (but that's easy enough as long as you've got Xcode) and MIT licensed so you can redistribute it as needed (e.g. included in your application bundle). Fairly decent tool and documentation support, including an online book by Matt Neuburg, with mailing list support for the Python and Ruby versions and direct email support for the others.
The 'official' alternative is Apple's Scripting Bridge. The API looks very Cocoa-like, but that's really just a lot of smoke and mirrors which ultimately makes it less capable than AppleScript and significantly more prone to application compatibility problems (and tricky to troubleshoot when it does go wrong). Tool, documentation and community support is not so great either (appscript's is better; AppleScript's is better still). SB's main advantage is that it's included in 10.5+ so requires no additional installation to use. I wouldn't recommend it for heavy-duty automation work due to its technical shortcomings, but for modest automation tasks involving obliging apps it may suffice.
Other bridges do exist (e.g. Perl's Mac::Glue, RubyOSA), but they are not as capable, popular and/or actively supported.
All that said, if you want to do any serious application scripting, you will still have to learn AppleScript as that's where you'll find the vast bulk of literature, sample scripts and community expertise. All of which you will need, since the great majority of scriptable applications are notoriously under-documented.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Can any one recommend a good all-in-one web development tool for Windows.
Something on par with Coda, which is only available for Mac OS X?
I have not used Coda by myself, but believe that whatever it has, you can find in Sublime Text 2 as well, check it out. For remote files access, you can use an utility like ExpanDrive that mounts remote drive as local disk.
I love Komodo Edit. I recommend that you try it.
I Tried NotePad++
And it is in fact very cool, However,
it crashes from time to time and it can delete your work! :O,
sadly i haven't found anything like CODA for the PC
so i'm staying with the mac
i think you can use notepad++ with ftp_synchronize plug-in so you can remotely edit files on server ;)
As far as I can tell, nothing gets close to Coda on mac. It's pretty sad.
I love Coda and use it professionally every day. However, I'm going to check out Aptana Studio and Komodo IDE on the PC---they both look like they could be very good.
Note that Coda is not free (download, $99), so the answer presumably shouldn't be limited to free PC software in order to compare apples to apples (pun intended).
Cheers!
I used PHPed myself, the best for me
I've looked and NetBeans 7.x is about as close as I've found. Coda is much more than an editor...it does Subversion, has an excellent built-in CSS editor, and allows really elegant local development and publish-to-host workflow. Even NetBeans is only local or remote, but can't deal with both in one project. However, NetBeans' MySQL integration is very handy.
Isn't Coda just a text editor? For Windows there is notepad++.
I use KomodoEdit and it does not even compare to Coda. Coding on a Mac is a lot different as you can have a built in terminal. A windows equivalent would have to have a plugin for putty or something similar.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I've been using vim, but after reading this question was wondering what is being used in the linux world.
There's also Netbeans: http://ruby.netbeans.org/
If you'd rather be using a light text editor instead of a heavy IDE, then I'd highly recommend going with GEdit with some additional plugins.
Here's an excellent guide on how to turn your GEdit into a "Linux Textmate":
Pimp My GEdit
If you want more of a IDE, then Netbeans is the current benchmark for Ruby IDEs.
I have used and really like Ruby Mine from JetBrains. It's been around since around 2008, here's the link for that: http://www.jetbrains.com/ruby/index.html
I use Diakonos. Written in Ruby, you can script it with Ruby, and manipulate text with Ruby. No dependencies (except Ruby itself).
I use Eclipse with Aptana RadRails: http://aptana.com/rails
but if you need only Ruby you can use RDT instead: http://rubyeclipse.sourceforge.net/
I'm surprised no one has mentioned jEdit - it has a whole slew of plugins for Ruby, and unlike many other editors with Ruby support, it is very stable. There are edit modes + syntax coloration for erb, rb, javascript, haml, etc. etc. I have it set up basically to mimic TextMate, with some Eclipse-isms. It doesn't do code completion to the nines, but it does at least try to complete from the current buffer. It also has very extensible key stroke configurations and the ability to record/playback macros.
I'm assuming you be using Ruby for the web? Aptana IDE with the RADRails plugin would have to be the best choice.
I really like using Geany for ruby and rails work.
I wouldn't affirm an IDE is better than other. Everyone has its pros an cons.
When I'm lazy I'd use Netbeans because it's comprehensive. An overkill in computer resources, but usefull if you are learning.
I've had bad comments about Aptana... maybe some of you that recommend this may have to convince me otherwise.
GEdit + Rails plugin may be a good alternative. And VIM is awfully powerfull but the learning curve is steeper (but once you get the taste of it, productivity will increase for sure).
It all depends on what you want.
I personally use vim as an editor as the default ruby tools as the rest of my IDE.
If you are looking for a more "heavyweight" IDE look at Eclipse (http://rubyeclipse.sourceforge.net/) or netbeans (Google for link).
There are a number of in-the-middle options which behave differently and have different features. Google is your best best when it comes to these.
Also - please see Ruby and linux, preferred setup?
and https://stackoverflow.com/questions/59968/best-editor-for-ruby
If I could close this question for being a dupe - I would.
komodo Edit is the best choice.