this is probably something really stupid but I can't work it out.
I upgraded my version of cucumber to v 0.10.0 and now the test's (running on Win 7) are not showing coloured output with the "pretty" formatter.
When tests are run it prints this error: *** WARNING: You must use ANSICON 1.31 or higher (http://adoxa.110mb.com/ansicon) to get coloured output on Windows
I have been to http://adoxa.110mb.com/ansicon but it's not obvious to me how I should be upgrading it. Anyone know how to upgrade my version of anscion?
One of the dev's at my work figured it out.
You need to
Download Ansicon from https://github.com/adoxa/ansicon/downloads and unzip it into a directory
with no spaces
Open a command prompt and cd to the folder where you unzipped it
Now, cd into either x86 or x64 (depending on your machine’s processor) and install it globally on
your machine (For example, D:\Cucumber\ansi160\x64)
Type ansicon.exe –i OR ansicon -i and press Enter
Any program that prints ANSI colors will now display properly on your machine.
Update as of today, http://adoxa.110mb.com/ansicon is no longer accessible.
Files have been uploaded to https://github.com/adoxa/ansicon/downloads.
I tried downloading from adoxa.3eeweb.com, but Chrome warned me that the file was "not commonly downloaded and could be dangerous."
So I opted with the file from github.
Besides that, I just followed the steps mentioned above and my output is now coloured.
Related
I just downloaded https://www.cygwin.com/setup-x86_64.exe
and used a few mirrors like cygwin.mirror.constant.com
w/o success
I read that file /etc/postinstall/0p_update-info-dir.dash
it hangs when running md5sum: ls -n /usr/share/info/*info* | md5sum >/usr/share/info/.stamp.tmp
because neither the file .stamp.tmp nor .stamp.tmp are being created
at the log here there is this:
Cygwin WARNING:
Couldn't compute FAST_CWD pointer. This typically occurs if you're using
an older Cygwin version on a newer Windows. Please update to the latest
available Cygwin version from https://cygwin.com/. If the problem persists,
please see https://cygwin.com/problems.html
but if I try to run md5sum directly it shows the same above warning.
it happens on windowsxp and windows 7
I tried a huge lot of tips and tricks from removing log files to deleting the whole install path to start again but it did not help
If you are being able to install cygwin on 2022, tell me how you did it?
PS.: that warning comes from bin/cygwin1.dll
Ansicon does not seem to want to work with Windows 8.
1 - I install it correctly : ansicon -i under the x64 directory (since I have Win 8 on a 64-bit machine/install),
2 - I launch a new command window, run rspec to run unit tests in ruby
Result - the ANSI characters are still displaying the raw unconverted data.
Any help would be appreciated; thanks.
Sounds like ansicon might not have installed correctly. I've got ansicon working well on Windows 8 64-bit with Ruby 1.9.3p392.
http://imgur.com/n28vomG
Try running ansicon -i from an elevated Command Prompt and see if that makes any difference. If you don't have administrator permissions, run ansicon -p to hook into the parent process for the current session and then see if rspec returns colored output then.
If you still can't get it to work, maybe try reinstalling the latest version of ansicon. I installed the 64-bit files (ANSI32.dll, ANSI64.dll, ansicon.exe, ANSI-LLW.exe) in my Ruby's bin directory so I know it's in my PATH.
I did a cheap trick and just made a shorcut directly on my desktop in order to use it.
adding it to the path crashed ruby.
I have a file abc.ps on my desktop. I have installed Ghostscript 9.05 on my machine and I want to view my abc.ps file using the command line.
GS>?????
What command should I write here. I am working on Windows 7.
Location of exe file: C:\Program Files\gs\gs9.05\bin
From the Ghostscript documentation:
GS> (c:/gs3.53/example.ps)
Just looks like you use forward slashes instead of back slashes. For example, if your Windows username is Ankit, you'd enter:
GS> (c:/Users/Ankit/Desktop/abc.ps)
You can avoid the interactive GS> commandprompt by running the command like this:
gswin32c.exe -sDEVICE=display c:/Users/Ankit/Desktop/abc.ps
Download and install Ghostview after installing Ghostscript, it is a GUI interface for Ghostscript:
http://pages.cs.wisc.edu/~ghost/gsview/get50.htm
Note: Be sure you download the same architecture. I.e. if you downloaded and installed 64 bit ghostscript, make sure you also download and install 64 bit Ghostview.
I have installed vim in windows and would like to configure it so i can send code to R. I want to also use Sweave with it. However, i have Googled and failed to find clear step-by-step instructions on how to set this up.
my attempts so far:
installed Vim using executable from ftp://ftp.vim.org/pub/vim/pc/gvim73_46.exe
downloaded R-plugin from https://github.com/jcfaria/Vim-R-plugin/zipball/master and extracted it to a folder on my pc. following instructions in the r-plugin.txt file, i installed python-3.2.msi and pywin32-216.1.win32-py3.2exe. I extracted the plugin zip-file to C:\Program Files (x86)\Vim\vimfiles\ merging like-named folders together. then i opened Vim and typed :helptags C:\Program Files (x86)\Vim\vimfiles\doc. I closed Vim then I started R and reopened Vim. I typed :new anewfile.R and got the error message
"Python interface must be enabled to run Vim-R-Plugin. Please do ':h r-plugin-installation details
and when i type this i get
error149, no help for r-plugin-installation
I also did not see the buttons that send code to R.
I failed to understand the instruction that , "You may have to
adjust the value of |vimrplugin_sleeptime|."
What should i do?
-I already have Miktex 2.9 on my PC. will Vim see it? How do I set up Vim to see Latex?
Will appreciate any help.
Note: I have used rstudio with Sweave and also eclipse but there are some issues i need to resolve and hence need to try vim and see how it will work out.
I suppose that this solution will not satisfying you completely but Rstudio IDE features a basic VIm editing mode: Global Option > Code Editing > Enable vim editing mode.
I think the windows binaries of Vim 7.3 need Python 2.7 or 3.1. You can check the information that you get via :version; the linked Python version is somewhere in it.
So my solution would be installing Python 2.7 (+pywin32 for python 2.7). Also, check if Python is working in Vim before trying to use the R plugin.
This is a pretty straight-forward question: I have an older INTEL Mac (32-bit) and I need to build a 32-bit version of ImageMagick.
I've seen some people playing around with options during the binary install, but I can't seem to find any reliable information about how to do this!
NOTE: ImageMagick gives out a 64-bit version of the binaries for Mac OS X on their webpage, but I'm not sure if this can be hacked into a 32-bit version during compiling?
THANK YOU - I'm really stuck on this!
The problem was ImageMagick's un-intuitive webpage that made it a little hard to figure out how to proceed - I finally found the binaries on their page and installed following these directions:
Intro:
If you have an older INTEL MacBook - it might have a 32-bit processor. This is how to compile ImageMagick (Mac OS X version) as a 32-bit program using the ImageMagick binary files - NOT USING MACPORTS!.
To find out what processor you have, i.e. 32-bit or 64-bit, look here:
http://support.apple.com/kb/ht3696
To install via MACPORTS look here:
http://xentek.net/articles/442/installing-imagemagick-and-imagick-via-macports/
My Computer:
This worked on my first-generation INTEL Macbook (you know - the white one with a Due Core processor).
OS:
I'm running OS X 10.6.4 (Snow Leopard)
INSTALL STEPS:
1. The trick is to ignore ImageMagick's pre-packed MAC OS X install package because it's compiled in a 64-bit version - we want a 32-bit version instead!
So, we need to get the UNIX binaries here: http://www.imagemagick.org/script/install-source.php#unix
Following the page's instructions, we download a file called ImageMagick.tar.gz. The ImageMagick group seemingly updates this link to point to the latest version.
The file is a compressed TAR file with the extension tar.gz. If you're using MAMP (like I am) then you might want to create a new file called "ImageMagick" (without the quotation marks "") in this folder: /Applications/MAMP/bin/. Normally we would install ImageMagick into this folder - however, because we're working from the binaries, a standard ./configure / make / make install pattern will simply default install ImageMagick into whatever path you have set up on your computer. In my case, my default path is the USR/LOCAL folder.
NOTE: if somebody wants to write here how to instead direct the ./configure options so that ImageMagick will install into a MAMP folder (or other folder) instead of the default path, that would be really helpful!
Well, back to the MAMP 32-bit install:
Place your recently-downloaded binary copy of ImageMagick in a new folder. I use a folder called SRC to keep all these intermediate copies of files in a place that I can later delete/clean when they are not necessary.
Next, expand the compressed file by opening your TERMINAL (look for the program in the "Utilities" folder).
With TERMINAL open, type the following:
cd path/to/the/ImageMagick/file #navigate to the folder where the file is saved
tar xvfz ImageMagick.tar.gz #expand the tar ball file
You should now see in the ImageMagick folder a new folder that you just expanded, called (for example) "ImageMagick-6.6.3" (NOTE: later versions of ImageMagick might have a different version number written at the end of this). Right now the folder would be called ImageMagick-6.6.3-2 ...
Move one level up into that folder.
To do so, type the following into TERMINAL:
cd ImageMagick-6.6.3-2 #replace the version number
Now you're going to run a standard .configure / make / make install pattern - your compiler/system should automatically configure the build to your 32-bit environment!
In terminal, you should be in the ImageMagick-6.6.3 file folder. Once there, run these commands:
sudo ./configure #I use SUDO here just in case your file permissions are messed up...
make #go get a cup of coffee
make install #go get another cup ...
HINT: text after the "#" is just my comments - just ignore the # and also the text on that line following the hash...
Make sure the "./configure" "MAKE" and "MAKE INSTALL" commands finish without errors - they should run just fine!
Then, you can run the standard ImageMagick test using your TERMINAL program:
Type this out to run the tests:
convert logo: logo.gif
identify logo.gif
display logo.gif
Wholla! You should see the ImageMagick logo pop up - meaning that ImageMagick is now installed on your 32-bit MAC OS X computer!
thx for this! to point configure to a different installation directory the syntax is:
./configure --prefix=NEW_PREFIX
where NEW_PREFIX should be set to the path of your mamp installation directory.