chrome magnet link handler

Hey! When I click a link with URL (for example) magnet:?xt=abunchofjibberishandstuffgoeshere , Google Chrome does nothing. It's because when I first clicked on one of them, I accidentally told it not to do anything.

How do I change that setting back so that the links actually work now? I couldn't find it in the Preferences.

-------------------------------

Quite chrome

Edit "C:\Users\xxxx\AppData\Local\Google\Chrome\User Data\Local State"

fing 'manget' -> delete line

「アジャイル・マニフェスト」の概要は、以下の通り。

• アジャイル開発の価値

• プロセスやツールより人と人同士の相互作用を重視する。
• 包括的なドキュメントより動作するソフトウェアを重視する。
• 契約上の交渉よりも顧客との協調を重視する。
• 計画に従うことよりも変化に対応することを重視する。

• アジャイル開発の原則

• http://www.metabolics.co.jp/XP/AgilePrinciples.html (日本語訳) を参照。

アジャイル･アライアンスの原則

我々は以下の原則に従います:

我々は価値のあるソフトウェアを

できるだけ早い段階から継続的に引き渡すことによって

お客様の満足度を高めることをもっとも優先します。

要件の変更は例え開発の後期であっても受け入れます。

アジャイル･プロセスは変化を味方につけることによって

お客様の競争力を引き上げます。

動くソフトウェアを

2~3週間から2~3ヶ月というできるだけ短い時間間隔で

繰り返し引き渡します。

ビジネスをする人と開発者はプロジェクトを通して

日々一緒に働かなければなりません。

意欲に満ちた人々を集めてプロジェクトを構成します。

ですから彼らが必要とする環境と支援を与え

仕事が無事終わるまで彼らを信頼してください。

開発チームに対して、あるいは開発チーム内部で

情報を伝えるもっとも効率的で効果的な方法は

面と向かって話をすることです。

動いているソフトウェアこそが進捗の最も重要な尺度です。

アジャイル･プロセスは持続可能な開発を促進します。

スポンサ、開発者、ユーザは一定のペースで

永続的に保守できるようにしなければなりません。

卓越した技術と優れた設計に対する

不断の注意こそが機敏さを高めます。

単純さ - 作業せずに済む量を

最大限に引き上げる技量 - が本質です。

最良のアーキテクチャ、要件、設計は

自己組織的なチームから生み出されます。

どうしたらチームがもっと効率を高めることができるかを

定期的に振り返り、それに基づいて自分たちのやり方を

最適に調整します。

(from http://agilealliance.org/principles.html)

How to clear subclipse and subversion password

How to clear subclipse and subversion password



Both subversion and subclipse cache usernames and passwords. Sometimes it is necessary to manually change the authentication information, e.g. to clear the password after it has changed, or occasionally, to update the username.



Anyone that uses subclipse (the subversion client for eclipse) that has needed to change the username or password for a stored repository, knows that there is no obvious way to do this. Luckily, I ran across this post. Unfortunately, it left some important details out.



If subclipse is setup to use JavaHL (which it is by default: check in Preferences > Team > SVN > SVN interface), then the passwords are stored in the same location as if the command-line svn tool was used. For unix-based systems (or using the command-line tool under cygwin), this is in ~/.subversion/auth/svn.simple. On windows it is in c:\Documents and Settings\[username]\Application Data\subversion\auth\svn.simple. It looks like there is one file per repository in this directory (the filename is a long hexadecimal number). This file contains your username and password.

On the other hand, if subclipse is configured to use the JavaSVN adapter, the .keyring file mentioned in the post appears to be located in the eclipse directory (not the workspace, the actually directory where the eclipse executable is found) under configuration/org.eclipse.core.runtime/.keyring. This is a binary file and hence must be deleted.



A few complaints: (1) I don�ft like the fact my password is stored plaintext in a location where others frequently have at least read access to (this is especially true in Windows) (2) if the keyring is stored in the Eclipse directory that means all users share the same authentication information. That means someone else on the computer could access my subversion repositories as me!



This seems like a huge security whole.



keywords: clear delete remove subversion subclipse password authentication information

Six Possible solutions for JDBC – SQL Server Connection problem

Six Possible solutions for JDBC – SQL Server Connection problem


Here in this post I am writing about some possible solutions of JDBC – MS SQL server connection problem.
During my work I had faced this problem and tried a little hard to findout the solution.
In our project when we tried to connect to MSSQL Server, through its default port 1433 it thrown an exception as follows.
Hope this will be helpful to you.

com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed.
java.net.ConnectException: Connection refused: connect

If you created the database and you are sure about your connection string then please check the following points.
   1. First Check the port which we are given is free or not. If any other connection is using this then please specify other port.
   2. Check the TCP/IP configuration in “MSSQL surface area configuration”. And if its disabled then make it enable.
   3. Check the Windows Firewall. It may obstruct the port accessing. So please disable it or allow this port accessing through the firewall using windows firewall configuration.
   4. Check if there is any antivirus software is running and it comes in between or not.
   5. Check the Dynamic port allocation of SQL Server is set or not. If it sets to ZERO or any other port then make it ‘Blank’. [making Blank is important] Give the static port number we want to the port number place. These configurations we can do in “SQL Server Configuration manager”. Give IPALL = 1433 also.  This information will set in the following part of the windows registry HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Microsoft SQL Server> MSSQL.1 > MSSQLServer > SuperSocketNetLib > Tcp> IP1/IP2/IPALL. If it’s not changing there we can manually change it.
   6. Then also its not working then please check the Windows Registry where we sets the “SQL Instance’s port number”. If it is different then please set that to our port number. It’s in HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Microsoft SQL Server > [Instance name] > MSSQLServer > SuperSocketNetLib > Tcp and change String value TcpPort = 1433.

Are are you reached here? Thanks for reading my full post :) becouse if u are a person who is facing this problem then I am sure you will not reach here, before itself it should solve :) And then also you are here then please check your connection string properly. I am giving an example here.

jdbc.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc.url=jdbc:sqlserver://servername:1433;DatabaseName=DBName;SelectMethod=cursor

英文标点符号翻译大全

英文标点符号翻译大全

+　 plus　加号；正号 -　 minus　减号；负号 ±　plus or minus　正负号 ×　is multiplied by　乘号 ÷　is divided by　除号 ＝　is equal to　等于号 ≠　is not equal to　不等于号 ≡　is equivalent to　全等于号 ≌　is equal to or approximately equal to　等于或约等于号 ≈　is approximately equal to　约等于号 ＜　is less than　小于号 ＞　is more than　大于号 ≮　is not less than　不小于号 ≯　is not more than　不大于号 ≤　is less than or equal to　小于或等于号 ≥　is more than or equal to　大于或等于号 %　 per cent　百分之… ‰　per mill　千分之… ∞　infinity　无限大号 ∝　varies as　与…成比例 √　(square) root　平方根 ∵　since; because　因为 ∴　hence　所以 ∷　equals, as (proportion)　等于，成比例 ∠　angle　角 ⌒　semicircle　半圆 ⊙　circle　圆 ○　circumference　圆周 π　pi 圆周率 △　triangle　三角形 ⊥　perpendicular to　垂直于 ∪　union of　并，合集 ∩　intersection of 交，通集 ∫　the integral of …的积分 ∑　(sigma) summation of　总和 °　degree　度 ′　minute　分 ″　second　秒 ℃　Celsius system　摄氏度 {　open brace, open curly　左花括号 }　close brace, close curly　右花括号 (　open parenthesis, open paren　左圆括号 )　close parenthesis, close paren　右圆括号 () brakets/ parentheses　括号 [　open bracket 左方括号 ]　close bracket 右方括号 [] square brackets　方括号 .　period, dot　句号，点 |　vertical bar, vertical virgule　竖线 &　ampersand, and, reference, ref　和，引用 *　asterisk, multiply, star, pointer　星号，乘号，星，指针 /　slash, divide, oblique 斜线，斜杠，除号 //　slash-slash, comment 双斜线，注释符 #　pound　井号 \　backslash, sometimes escape　反斜线转义符，有时表示转义符或续行符 ~　tilde　波浪符 .　full stop　句号 ,　comma　逗号 :　colon　冒号 ;　semicolon　分号 ?　question mark　问号 !　exclamation mark (英式英语) exclamation point (美式英语) '　apostrophe　撇号 -　hyphen　连字号 -- dash 破折号 ...　dots/ ellipsis　省略号 "　single quotation marks 单引号 ""　double quotation marks 双引号 ‖ parallel 双线号 &　ampersand = and ～　swung dash 代字号 §　section; division 分节号 →　arrow 箭号；参见号

bash scripting (if statements)

If you use bash for scripting you will undoubtedly have to use conditions a lot, for example for an if ... then construct or a while loop. The syntax of these conditions can seem a bit daunting to learn and use. This tutorial aims to help the reader understanding conditions in bash, and provides a comprehensive list of the possibilities. A small amount of general shell knowledge is assumed.

Difficulty: Basic - Medium

Introduction

Bash features a lot of built-in checks and comparisons, coming in quite handy in many situations. You've probably seen if statements like the following before:

if [ $foo -ge 3 ]; then

The condition in this example is essentially a command. It may sound strange, but surrounding a comparison with square brackets is the same as using the built-in test command, like this:

if test $foo -ge 3; then

If $foo is Greater then or Equal to 3, the block after 'then' will be executed. If you always wondered why bash tends to use -ge or -eq instead of >= or ==, it's because this condition type originates from a command, where -ge and -eq are options.
And that's what if does essentially, checking the exit status of a command. I'll explain that in more detail further in the tutorial.
There also are built-in checks that are more specific to shells. What
about this one?

if [ -f regularfile ]; then

The above condition is true if the file 'regularfile' exists and
is a regular file. A regular file means that it's not a block or
character device, or a directory. This way, you can make sure a usable
file exists before doing something with it. You can even check if a
file is readable!

if [ -r readablefile]; then

The above condition is true if the file 'readablefile' exists and is readable. Easy, isn't it?

The syntax of an if statement (a short explanation)

The basic syntax of an if ... then statement is like this:

if <condition>; then
<commands>
fi

The condition is, depending on its type, surrounded by certain
brackets, eg. [ ]. You can read about the different types further on
in the tutorial. You can add commands to be executed when the condition is false using the else keyword, and use the elif (elseif) keyword to execute commands on another condition if the primary condition is false. The else keyword always comes last. Example:

if [ -r somefile ]; then
content=$(cat somefile)
elif [ -f somefile ]; then
echo "The file 'somefile' exists but is not readable to the script."
else
echo "The file 'somefile' does not exist."
fi

A short explanation of the example: first we check if the file somefile is readable ("if [ -r somefile ]"). If so, we read it into a variable. If not, we check if it actually exists ("elif [ -f somefile ]"). If that's true, we report that it exists but isn't readable (if it was, we would have read the content). If the file doesn't exist, we report so, too. The condition at elif is only executed if the condition at if was false. The commands belonging to else are only executed if both conditions are false.

The basic rules of conditions

When you start writing and using your own conditions, there are some rules you should know to prevent getting errors that are hard to trace. Here follow three important ones:

1. Always keep spaces between the brackets and the actual check/comparison. The following won't work:
   

   if [$foo -ge 3]; then

   Bash will complain about a "missing `]'".
2. Always terminate the line before putting a new keyword like "then". The words if, then, else, elif and fi are shell keywords, meaning that they cannot share the same line. Put a ";" between the previous statement and the keyword or place the keyword on the start of a new line. Bash will throw errors like "syntax error near unexpected token `fi'" if you don't.
3. It is a good habit to quote string variables if you use them in conditions, because otherwise they are likely to give trouble if they contain
   spaces and/or newlines. By quoting I mean:

   if [ "$stringvar" == "tux" ]; then

   There are a few cases in which you should not
   quote, but they are rare. You will see one of them further on in the tutorial.

Also, there are two things that may be useful to know:

1. You can invert a condition by putting an "!" in front of it. Example:
   

   if [ ! -f regularfile ]; then

   Be sure to place the "!" inside the brackets!
2. You can combine conditions by using certain operators. For the single-bracket syntax that we've been using so far, you can use "-a" for and and "-o" for or. Example:
   

   if [ $foo -ge 3 -a $foo -lt 10 ]; then

   The above condition will return true if $foo contains an integer greater than or equal to 3 and Less Than 10. You can read more about these combining expressions at the respective condition syntaxes.

And, one more basic thing: don't forget that conditions can also be used in other statements, like while and until. It is outside the scope of this tutorial to explain those, but you can read about them at the Bash Guide for Beginners.

Anyway, I've only shown you conditions between single brackets so far. There are more syntaxes, however, as you will read in the next section.

Different condition syntaxes

Bash features different syntaxes for conditions. I will list the three of them:

1. Single-bracket syntax

This is the condition syntax you have already seen in the previous paragraphs; it's the oldest supported syntax. It supports three types of conditions:

• File-based conditions
  • Allows different kinds of checks on a file. Example:
    

    if [ -L symboliclink ]; then

    The above condition is true if the file 'symboliclink' exists and is a symbolic link. For more file-based conditions see the table below.
• String-based conditions
  • Allows checks on a string and comparing of strings. Example one:
    

    if [ -z "$emptystring" ]; then

    The above condition is true if $emptystring is an empty string or an uninitialized variable. Example two:

    if [ "$stringvar1" == "cheese" ]; then

    The above condition is true if $stringvar1 contains just the string "cheese". For more string-based conditions see the table below.
• Arithmetic (number-based) conditions
  • Allows comparing integer numbers. Example:
    

    if [ $num -lt 1 ]; then

    The above condition returns true if $num is less than 1. For more arithmetic conditions see the table below.

2. Double-bracket syntax

You may have encountered conditions enclosed in double square brackets already, which look like this:

if [[ "$stringvar" == *string* ]]; then

The double-bracket syntax serves as an enhanced version of the single-bracket syntax; it mainly has the same features, but also some important differences with it. I will list them here:

• The first difference can be seen in the above example; when comparing strings, the double-bracket syntax features shell globbing. This means that an asterisk ("*") will expand to literally anything, just as you probably know from normal command-line usage. Therefore, if $stringvar contains the phrase "string" anywhere, the condition will return true. Other forms of shell globbing are allowed, too. If you'd like to match both "String" and "string", you could use the following syntax:
  

  if [[ "$stringvar" == *[sS]tring* ]]; then

  Note that only general shell globbing is allowed. Bash-specific things like {1..4} or {foo,bar} will not work. Also note that the globbing will not work if you quote the right string. In this case you should leave it unquoted.
• The second difference is that word splitting is prevented. Therefore, you could omit placing quotes around string variables and use a condition like the following without problems:
  

  if [[ $stringvarwithspaces != foo ]]; then

  Nevertheless, the quoting string variables remains a good habit, so I recommend just to keep doing it.
• The third difference consists of not expanding filenames. I will illustrate this difference using two examples, starting with the old single-bracket situation:
  

  if [ -a *.sh ]; then

  The above condition will return true if there is one single file in the working directory that has a .sh extension. If there are none, it will return false. If there are several .sh files, bash will throw an error and stop executing the script. This is because *.sh is expanded to the files in the working directory. Using double brackets prevents this:

  if [[ -a *.sh ]]; then

  The above condition will return true only if there is a file in the working directory called "*.sh", no matter what other .sh files exist. The asterisk is taken literally, because the double-bracket syntax does not expand filenames.
• The fourth difference is the addition of more generally known combining expressions, or, more specific, the operators "&&" and "||". Example:
  

  if [[ $num -eq 3 && "$stringvar" == foo ]]; then

  The above condition returns true if $num is equal to 3 and $stringvar is equal to "foo". The -a and -o known from the single-bracket syntax is supported, too.
  Note that the and operator has precedence over the or operator, meaning that "&&" or "-a" will be evaluated before "||" or "-o".
• The fifth difference is that the double-bracket syntax allows regex pattern matching using the "=~" operator. See the table for more information.

3. Double-parenthesis syntax

There also is another syntax for arithmetic (number-based) conditions, most likely adopted from the Korn shell:

if (( $num <= 5 )); then

The above condition is true if $num is less than or equal to 5. This syntax may seem more familiar to programmers. It features all the 'normal' operators, like "==", "<" and ">=". It supports the "&&" and "||" combining expressions (but not the -a and -o ones!). It is equivalent to the built-in let command.

Table of conditions

The following table list the condition possibilities for both the single- and the double-bracket syntax. Save a single exception, the examples are given in single-bracket syntax, but are always compatible with double brackets.

1. File-based conditions:
Condition	True if	Example/explanation
[ -a existingfile ]	file 'existingfile' exists.	if [ -a tmp.tmp ]; then     rm -f tmp.tmp # Make sure we're not bothered by an old temporary filefi
[ -b blockspecialfile ]	file 'blockspecialfile' exists and is block special.	Block special files are special kernel files found in /dev, mainly used for ATA devices like hard disks, cd-roms and floppy disks. if [ -b /dev/fd0 ]; then     dd if=floppy.img of=/dev/fd0 # Write an image to a floppy fi
[ -c characterspecialfile ]	file 'characterspecialfile' exists and is character special.	Character special files are special kernel files found in /dev, used for all kinds of purposes (audio hardware, tty's, but also /dev/null). if [ -c /dev/dsp ]; then     cat raw.wav > /dev/dsp # This actually works for certain raw wav files fi
[ -d directory ]	file 'directory' exists and is a directory.	In UNIX-style, directories are a special kind of file. if [ -d ~/.kde ]; then     echo "You seem to be a kde user." fi
[ -e existingfile ]	file 'existingfile' exists.	(same as -a, see that entry for an example)
[ -f regularfile ]	file 'regularfile' exists and is a regular file.	A regular file is neither a block or character special file nor a directory. if [ -f ~/.bashrc ]; then     source ~/.bashrc fi
[ -g sgidfile ]	file 'sgidfile' exists and is set-group-ID.	When the SGID-bit is set on a directory, all files created in that directory will inherit the group of the directory. if [ -g . ]; then    echo "Created files are inheriting the group '$(ls -ld . | awk '{ print $4 }')' from the working directory." fi
[ -G fileownedbyeffectivegroup ]	file 'fileownedbyeffectivegroup' exists and is owned by the effective group ID.	The effective group id is the primary group id of the executing user. if [ ! -G file ]; then # An exclamation mark inverts the outcome of the condition following it    chgrp $(id -g) file # Change the group if it's not the effective one fi
[ -h symboliclink ]	file 'symboliclink' exists and is a symbolic link.	if [ -h $pathtofile ]; then     pathtofile=$(readlink -e $pathtofile) #Make sure $pathtofile contains the actual file and not a symlink to it fi
[ -k stickyfile ]	file 'stickyfile' exists and has its sticky bit set.	The sticky bit has got quite a history, but is now used to prevent world-writable directories from having their contents deletable by anyone. if [ ! -k /tmp ]; then # An exclamation mark inverts the outcome of the condition following it     echo "Warning! Anyone can delete and/or rename your files in /tmp!" fi
[ -L symboliclink ]	file 'symboliclink' exists and is a symbolic link.	(same as -h, see that entry for an example)
[ -N modifiedsincelastread ]	file 'modifiedsincelastread' exists and was modified after the last read.	if [ -N /etc/crontab ]; then     killall -HUP crond # SIGHUP makes crond reread all crontabsfi
[ -O fileownedbyeffectiveuser ]	file 'fileownedbyeffectiveuser' exists and is owned by the user executing the script.	if [ -O file ]; then     chmod 600 file # Makes the file private, which is a bad idea if you don't own it fi
[ -p namedpipe ]	file 'namedpipe' exists and is a named pipe.	A named pipe is a file in /dev/fd/ that can be read just once. See my bash tutorialfor a case in which it's used. if [ -p $file ]; then     cp $file tmp.tmp # Make sure we'll be able to read     file="tmp.tmp"    # the file as many times as we like fi
[ -r readablefile ]	file 'readablefile' exists and is readable to the script.	if [-r file ]; then     content=$(cat file) # Set $content to the content of the filefi
[ -s nonemptyfile ]	file 'nonemptyfile' exists and has a size of more than 0 bytes.	if [ -s logfile ]; then     gzip logfile    # Backup the old logfile     touch logfile # before creating a fresh one. fi
[ -S socket ]	file 'socket' exists and is a socket.	A socket file is used for inter-process communication, and features an interface similar to a network connection. if [ -S /var/lib/mysql/mysql.sock ]; then     mysql --socket=/var/lib/mysql/mysql.sock # Seethis MySQL tipfi
[ -t openterminal ]	file descriptor 'openterminal' exists and refers to an open terminal.	Virtually everything is done using files on Linux/UNIX, and the terminal is no exception. if [ -t /dev/pts/3 ]; then     echo -e "\nHello there. Message from terminal $(tty) to you." > /dev/pts/3 #Anyone using that terminal will actually see this message! fi
[ -u suidfile ]	file 'suidfile' exists and is set-user-ID.	Setting the suid-bit on a file causes execution of that file to be done with the credentials of the owner of the file, not of the executing user. if [ -u executable ]; then     echo "Running program executable as user $(ls -l executable | awk '{ print $3 }')." fi
[ -w writeablefile ]	file 'writeablefile' exists and is writeable to the script.	if [ -w /dev/hda ]; then     grub-install /dev/hda fi
[ -x executablefile ]	file 'executablefile' exists and is executable for the script.	Note that the execute permission on a directory means that it's searchable (you can see which files it contains). if [ -x /root ]; then     echo "You can view the contents of the /root directory." fi
[ newerfile -nt olderfile ]	file 'newerfile' was changed more recently than 'olderfile', or if 'newerfile' exists and 'olderfile' doesn't.	if [ story.txt1 -nt story.txt ]; then     echo "story.txt1 is newer than story.txt; I suggest continuing with the former." fi
[ olderfile -ot newerfile ]	file 'olderfile' was changed longer ago than 'newerfile', or if 'newerfile' exists and 'olderfile' doesn't.	if [ /mnt/remote/remotefile -ot localfile ]; then     cp -f localfile /mnt/remote/remotefile #Make sure the remote location has the newest version of the file, too fi
[ same -ef file ]	file 'same' and file 'file' refer to the same device/inode number.	if [ /dev/cdrom -ef /dev/dvd ]; then     echo "Your primary cd drive appears to read dvd's, too." fi
2. String-based conditions:
Condition	True if	Example/explanation
[ STRING1 == STRING2 ]	STRING1 is equal to STRING2.	if [ "$1" == "moo" ]; then     echo $cow # Ever tried executing 'apt-get moo'?fi Note: you can also use a single "=" instead of a double one.
[ STRING1 != STRING2 ]	STRING1 is not equal to STRING2.	if [ "$userinput" != "$password" ]; then     echo "Access denied! Wrong password!"     exit 1 # Stops script execution right here fi
[ STRING1 \> STRING2 ]	STRING1 sorts after STRING2 in the current locale (lexographically).	The backslash before the angle bracket is there because the bracket needs to be escaped to be interpreted correctly. As an example we have a basic bubble sort: (Don't feel ashamed if you don't understand this, it is a more complex example)   array=( linux tutorial blog ) swaps=1 while (( swaps > 0 )); do     swaps=0     for (( i=0; i < (( ${#array[@]} - 1 )) ; i++ )); do         if [ "${array[$i]}" \> "${array[$(( i + 1 ))]}" ]; then # Here is the sorting condition             tempstring=${array[$i]}             array[$i]=${array[$(( i + 1 ))]}             array[$(( i + 1 ))]=$tempstring             (( swaps=swaps + 1 ))         fi     done done echo ${array[@]} # Returns "blog linux tutorial"
[ STRING1 \< STRING2 ]	STRING1 sorts before STRING2 in the current locale (lexographically).
[ -n NONEMPTYSTRING ]	NONEMPTYSTRING has a length of more than zero.	This condition only accepts valid strings, so be sure to quote anything you give to it. if [ -n "$userinput" ]; then     userinput=parse($userinput) # Only parse if the user actually gave some input. fi Note that you can also omit the "-n", as brackets with just a string in it behave the same.
[ -z EMPTYSTRING ]	EMPTYSTRING is an empty string.	This condition also accepts non-string input, like an uninitialized variable: if [ -z $uninitializedvar ]; then     uninitializedvar="initialized" # -z returns true on an uninitialized variable, so we initialize it here. fi
Double-bracket syntax only:[[ STRING1 =~ REGEXPATTERN ]]	STRING1 matches REGEXPATTERN.	If you are familiar with Regular Expressions, you can use this conditions to perform a regex match. if [[ "$email" =~ "\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,4}\b" ]]; then     echo "\$email contains a valid e-mail address." fi
3. Arithmetic (number-based) conditions:
Condition	True if	Example/explanation
[ NUM1 -eq NUM2 ]	NUM1 is EQual to NUM2.	These conditions only accept integer numbers. Strings will be converted to integer numbers, if possible. Some random examples: if [ $? -eq 0 ]; then # $? returns the exit status of the previous command     echo "Previous command ran succesfully." fi if [ $(ps -p $pid -o ni=) -ne $(nice) ]; then     echo "Process $pid is running with a non-default nice value" fi if [ $num -lt 0 ]; then     echo "Negative numbers not allowed; exiting..."     exit 1 fi
[ NUM1 -ne NUM2 ]	NUM1 is Not Equal to NUM2.
[ NUM1 -gt NUM2 ]	NUM1 is Greater Than NUM2.
[ NUM1 -ge NUM2 ]	NUM1 is Greater than orEqual to NUM2.
[ NUM1 -lt NUM2 ]	NUM1 is Less Than NUM2.
[ NUM1 -le NUM2 ]	NUM1 is Less than orEqual to NUM2.
4. Miscellaneous conditions:
Condition	True if	Example/explanation
[ -o shelloption ]	shell option 'shelloption' is enabled.	Shell options modify the behaviour of bash, except a few unmodifiable ones that indicate the shell status. if [ ! -o checkwinsize ] # An exclamation mark inverts the outcome of the condition following it     echo "Shell option checkwinsize is disabled; enabling it so you can resize you terminal window without problems."     shopt -s checkwinsize # This shell option is modifiable fi if [ -o login_shell ]; then     echo "This a a login shell." # This shell option is not modifiable fi

With the double-parenthesis syntax, you can use the following conditions:

5. Double-parenthesis syntax conditions:
Condition	True if	Example/explanation
(( NUM1 == NUM2 ))	NUM1 is equal to NUM2.	These conditions only accept integer numbers. Strings will be converted to integer numbers, if possible. Some random examples: if (( $? == 0 )); then # $? returns the exit status of the previous command     echo "Previous command ran succesfully." fi if (( $(ps -p $pid -o ni=) != $(nice) )); then     echo "Process $pid is running with a non-default nice value" fi if (( $num < 0 )); then     echo "Negative numbers not allowed; exiting..."     exit 1 fi
(( NUM1 != NUM2 ))	NUM1 is not equal to NUM2.
(( NUM1 > NUM2 ))	NUM1 is greater than NUM2.
(( NUM1 >= NUM2 ))	NUM1 is greater than or equal to NUM2.
(( NUM1 < NUM2 ))	NUM1 is less than NUM2.
(( NUM1 <= NUM2 ))	NUM1 is less than or equal to NUM2.

After this dry information load, here's a bit of explanation for those who want to know more...

Diving a little deeper

I said I'd tell more about the fact that if essentially checks the exit status of commands. And so I will. The basic rule of bash when it comes to conditions is 0 equals true, >0 equals false.
That's pretty much the opposite of many programming languages where 0 equals false and 1 (or more) equals true. The reason behind this is that shells like bash deal with programs a lot. By UNIX convention, programs use an exit status for indicating whether execution went alright or an error occured. As a succesful execution doesn't require any explanation, it needs only one exit status. If there was a problem, however, it is useful to know what went wrong. Therefore, 0 is used for a succesful execution, and 1-255 to indicate what kind of error occured. The meaning of the numbers 1-255 differs depending on the program returning them.

Anyway, if executes the block after then when the command returns 0. Yes, conditions are commands. The phrase [ $foo -ge 3 ] returns an exit status, and the other two syntaxes as well! Therefore, there's a neat trick you can use to quickly test a condition:

[ $foo -ge 3 ] && echo true

In this example, "echo true" is only executed if "[ $foo -ge 3 ]" returns 0 (true). Why is that, you might ask. It's because bash only evaluates a condition when needed. When using the and combining expression, both conditions need to be true to make the combining expression return true. If the first condition returns false, it doesn't matter what the second one returns; the result will be false. Therefore, bash doesn't evaluate the second condition, and that's the reason why "echo true" is not executed in the example. This is the same for the or operator ("||"), where the second condition is not evaluated if the first one is true.

Well, so much for the diving. If you want to know even more, I'd like to point you to the Advanced Bash-Scripting Guide and maybe the Bash Reference Manual.

Conclusion

In this tutorial, you've been able to make a start at understanding the many possibilities of conditions in bash scripting. You've been able to read about the basic rules of writing and using conditions, about the three syntaxes and their properties, and maybe you took the opportunity to dive a little deeper. I hope you enjoyed the reading as much as I enjoyed the writing. You can always return here to look up conditions in the table (bookmark that link to see the table directly), or to refresh your knowledge. If you have any suggestions, additions or other feedback, feel free to comment. Thanks for reading and happy scripting!