Show Hidden Files on your Mac


How to Show Hidden Files on your mac? If you find yourself needing to access hidden files on your Mac (say an .htaccess file you downloaded), run the below command from the terminal.
For those who don’t know, files that are hidden in Mac OS are determined so by preceding the filename with a single period symbol (.), you can actually make any file hidden by doing this.

Show Hidden Files on your Mac

Launch the Terminal and enter these commands exactly as shown. The first command activates the ability to see the hidden files:
defaults write com.apple.Finder AppleShowAllFiles TRUE
Now you must relaunch the Finder by killing it, this is how the changes take effect:
killall Finder
If you want to hide hidden files again (those preceded with a .) and go back to the default Mac settings, you can just type the following:
defaults write com.apple.Finder AppleShowAllFiles FALSE
Again you will need to kill the Finder so that it can relaunch for changes to take effect:
killall Finder
That’s all there is to it!

Show Hidden Files in a Mac Save Dialogue

You can quickly show all hidden files in any Mac OS X save dialogue box by hitting Command+Shift+Period

Show Hidden Files on your Mac through the Terminal

Another way to quickly see hidden files is by using the ls command within the Terminal, at the command line type the following:
ls -a
The -a flag tells the ls (list) command to show all contents, including hidden files. You then just have to specify a directory if you want to see the hidden files in it:
ls -a ~/Sites/betasite
This method does not effect the Finder or the visibility of hidden files outside of using the -a flag.

Source : http://osxdaily.com/2009/02/25/show-hidden-files-in-os-x/
 

How to Login More Than One Skype Account





How to login more than one skype account? yeeah sometimes people have more than one account on skype, so the problem is how to login with that account at the same time? To use more than one Skype account on the same computer at the same time you need to start a new instance of Skype. so this is a simple way.







How To Login More Than One Skype Account For Windows User :

  1. Login as usual for first account
  2. From the Windows taskbar, click Start > Run (or press the Windows and R keys on your keyboard at the same time)
  3. In the Run window, enter the following command (include the quotes) and press OK:
    "C:\Program Files\Skype\Phone\Skype.exe" /secondary

  1. Login as usual for first account
  2. Open Terminal,goto spotlight (cmd+space) and type terminal then enter.
  3. In the Terminal window, enter the following command  and press OK:
    sudo /Applications/Skype.app/Contents/MacOS/Skype /secondary

If you get an error message, copy and paste the exact command from this page and try again.
Be aware that if you have changed the installation path for Skype then you will need to enter the correct path for the Skype file.



 

How to, capture animated screen into gif file

how to capture animated screen into gif file? its easy using software called LICEcapLICEcap can capture an area of your desktop and save it directly to .GIF (for viewing in web browsers, etc) or .LCF (see below). 

LICEcap is an intuitive but flexible application (for Windows and now OSX), that is designed to be lightweight and function with high performance. 

In addition to .GIF, LICEcap supports its own native lossless .LCF file format, which allows for higher compression ratios than .GIF, higher quality (more than 256 colors per frame), and more accurate timestamping. If you record to .LCF, you can later convert to .GIF (using the included command line utility), or play back the .LCF files directly within REAPER

this software to capture animated screen into gif file available for Windows and OSX. LICEcap is GPL free software, each download package includes the source. 

Features and options:
  • Record directly to .GIF or .LCF.
  • Move the screen capture frame while recording.
  • Pause and restart recording, with optional inserted text messages.
  • Global hotkey (shift+space) to toggle pausing while recording
  • Adjustable maximum recording framerate, to allow throttling CPU usage.
  • Basic title frame, with or without text.
  • Record mouse button presses.
  • Display elapsed time in the recording.
Requirements:
  • For Windows: Windows XP/Vista/7 (might work with reduced functionality on other versions)
  • For OSX: OS 10.4+ (10.6+ for full feature support), PPC or Intel (note: OS X support is still preliminary, some features are not supported)
  • A reasonably fast CPU
  • A healthy amount of RAM (1GB+, especially when encoding to LCF)
go directly to official LICEcap website : http://www.cockos.com/licecap/
 

Configuring VirtualHosts in XAMPP on Mac


A few weeks back I rejoined the “Cult of Mac” when I replaced my old Asus notebook with a MacBook Pro, and since then I’ve been busy settling into my new OSX workflow. I do all my development locally, so one of the first applications I installed was XAMPP, a cross platform Apache/MySQL/PHP stack. While I know that MAMP is very popular on Mac, I have been using XAMPP for many years so I thought I’d stick with what I know.
Installing XAMPP was a snap, but when I came to create my own Apache VirtualHoststhings started getting fiddly. Here are the steps I followed to get everything running smoothly.

What are VirtualHosts?

First, some quick background on what we’re trying to achieve.
VirtualHosts allow Apache to map a hostname to a directory on the filesystem. You can set up as many VirtualHosts as you need, so that each website operates under its own hostname. For example, you might want to map mysite.local to/Users/yourusername/mysite. To test your development site all you would need to do is plug “http://mysite.local” into your browser’s address bar.

Enable VirtualHosts

The first thing you’ll need to do is open the file/Applications/XAMPP/xamppfile/etc/httpd.conf in your favourite text editor. Look for the following lines:
1
2
# Virtual hosts
#Include /Applications/XAMPP/etc/extra/httpd-vhosts.conf
Uncomment the second line by removing the hash (#), so that Apache loads your custom VirtualHosts configuration file:
1
2
# Virtual hosts
Include /Applications/XAMPP/etc/extra/httpd-vhosts.conf

Create your VirtualHosts

Open the file /Applications/XAMPP/xamppfile/etc/extra/httpd-vhosts.conf. Towards the bottom of the file you will see some example VirtualHosts, which you should comment out or delete.
At the bottom of the file, add ‘localhost’ as the default named VirtualHost:
1
2
3
4
5
6
7
8
9
10
11
# localhost
<VirtualHost *:80>
    ServerName localhost
    DocumentRoot "/Applications/XAMPP/htdocs"
    <Directory "/Applications/XAMPP/htdocs">
        Options Indexes FollowSymLinks Includes execCGI
        AllowOverride All
        Order Allow,Deny
        Allow From All
    </Directory>
</VirtualHost>
This step is necessary to ensure that http://localhost still points at XAMPP’s htdocsdirectory once we’ve created our custom VirtualHosts. Personally I don’t use the htdocsdirectory a lot, but occasionally it’s useful to have somewhere to perform quick tests.
Now you are ready to create your own VirtualHosts. After the default localhost that you just created, add:
1
2
3
4
5
6
7
8
9
10
11
12
# My custom host
<VirtualHost *:80>
    ServerName mysite.local
    DocumentRoot "/Users/yourusername/path/to/your/site"
    <Directory "/Users/yourusername/path/to/your/site">
        Options Indexes FollowSymLinks Includes ExecCGI
        AllowOverride All
        Order Allow,Deny
        Allow From All
    </Directory>
    ErrorLog "logs/mysite.local-error_log"
</VirtualHost>
In the above example you should replace “mysite.local” with your own hostname. This can be anything you wish, but make sure you choose a hostname that won’t conflict with a real domain name. Using a .local extension makes it obvious that the site is hosted locally rather than on a public web server.
The path to your website can point at any folder in your OSX user directory. I store most of my sites inside of Dropbox so that I can access them on both my home and work machines. If your path includes spaces, make sure you enclose it in quotes, like in my example.

Edit your hosts file

Once you’ve saved your httpd.conf and httpd-vhosts.conf files, the next step is to edit your OSX hosts file so it knows how to handle your new ServerName. The hosts file is used by OSX to map hostnames to IP addresses. In this case we want to map your newServerName to the IP address 127.0.0.1, which is your localhost.
Fire up a Terminal instance, and at the prompt type the following command:
1
sudo nano /etc/hosts
Enter your OSX password when prompted, and the hosts file will be opened in the nano text editor. You’ll see that the hosts file already contains some default hostname mappings (e.g. “127.0.0.1 localhost”). Use your keyboard’s arrow keys to navigate to the bottom of the file and add your own mapping:
1
2
# XAMPP VirtualHost mappings
127.0.0.1 mysite.local
Save the host file using the key combo control+o, and pressing return when prompted to choose the filename. Close the file using control+x.

Restart Apache

So that your changes take effect, restart Apache. This can be done using XAMPP Control, which is found at /Applications/XAMPP/XAMPP Control.app.
Point your browser at http://mysite.local (or whatever ServerName you chose) and you should see your website. However, there’s a chance that instead you’ll be faced with a…

403 error

Because Apache runs as the ‘nobody’ user by default, it may not have adequate permission to browse your OSX user directory or some of its subdirectories, in which case you’ll see a 403 ‘access forbidden’ error when you try and view your development site. Similarly, you may find that although you can view your dev site, PHP throws errors when you attempt to write files or make directories on the filesystem.
To fix this you can configure Apache to run as your OSX user. Open/Applications/XAMPP/xamppfiles/etc/httpd.conf and look for the following lines:
1
2
3
4
5
6
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User nobody
Group nogroup
Change User to your OSX username, and save the file:
1
User yourusername
Restart Apache and you should now be able to navigate your site without any issues, including manipulating files and folders using PHP.
Making the change I’ve described above carries certain security risks, and if you choose to run Apache as your OSX user then you’ll need to be quite certain that XAMPP is not accessible from outside your local network. From what I understand, XAMPP’s built in security features ensure that this is the case out-of-the-box, and it is straightforward to beef up security for additional piece of mind.
If you’re not convinced that it’s safe to let Apache run as your OSX user, another option is to change the permissions of your dev directories so that the ‘nobody’ or ‘_www’ user can read/write to them.I suspect that I would quickly tire of setting folder permissions, which is why I have opted to take the path of least resistance!

Conclusion

Hopefully this post helps someone else to get XAMPP up and running on OSX. I imagine that MAMP Pro streamlines this process somewhat (I know it has a wizard for creating VirtualHosts), but as long as you don’t mind getting your hands dirty XAMPP is a fantastic way to learn how Apache actually works.

Source : http://f6design.com/journal/2012/03/11/configuring-virtualhosts-in-xampp-on-mac/
 
 
Copyright © 2011. GixBox Log - All Rights Reserved
Proudly powered by Blogger