My previous RebelLabs post showed us that there still is a nice amount of interest among the developers in neat command line tools. This is great news as it means there are still lots of geeks reaching for their maximum l33t potential! This post will, as the title suggests, jump into 5 more tools that will hopefully tickle your fancy.

Whilst it is hard to find a set of tools relevant for every different command line professional or enthusiast, I can still wholly recommend glancing over these tools briefly. You never know when you’ll get stuck in a terminal only environment or will need to impress a friend with your exceptional command line skills. So without further ado, here are 5 more command line tools you should consider using!

z

1. Install it once
2. Forget it’s even there
3. Profit from its productivity: z.

OK, but what’s it all about? Well, z allows you to quickly jump from folder to folder, without having to bother writing the full absolute or relative paths. To achieve this, it simply records all the folders you visit, and then ranks them based on a combination of the frequency and time of last use. Now all you need to do is type z part/of/path and hit enter. With this, z will automagically guide you to the highest ranking match.

To install z, download z.sh and source it in ~/.zshrc or ~/.bashrc, if you still haven’t made the inevitable jump to ZSH. Now go about your regular flow, cd-ing all over the place, and you are done!

Alternatively, if you use the oh-my-zsh framework, simply add it in the plugins listing of ~/.zshrc.

 $ vim ~/.zshrc  plugins=(brew git mercurial mvn osx sbt scala vi-mode z) 

By default, z stores its data in ~/.z, below are my contents after I cleared them and moved around a bit. After printing the data, you can see I moved to 2 different folders by specifying only a small part of the path, irrespective of the current folder. Take note that the directory name was matched mid-word in a case insensitive way — very handy!

All in all I highly recommend this great tool to anyone that spends any amount of time at the command line, whatever your background, interest or use case may be.

youtube-dl

The second tool of this post is the excellent youtube-dl. A cross-platform tool allowing you to, unsuprisingly, download Youtube videos. The easiest way to install is either via Homebrew orpip as shown below. Other download options can be found via the link above.

 $ brew install youtube-dl  $ sudo pip install --upgrade youtube_dl 

At times, for whatever reason, you may want to download a presentation for archiving’s purposes. Or better yet, imagine you spend the weekend in the Estonian countryside, devoid of internet, yet you really wanted to see the latest Virtual JUG sessions. A simple youtube-dl https://youtu.be/PQPvZkA-6bg suffices at this point.

Other nice things to take note of:

• You are not limited to downloading from Youtube only, Vimeo for example is also supported.
• Simply point to a Youtube playlist and youtube-dl will be smart enough to automatically download the full list.
• As shown in the example image, youtube-dl will happily follow shortened URLs for you.
• By default the highest quality video will be downloaded, however a simple youtube-dl -f $FORMAT $LINK will override this. You find available formats with the -F flag.
• A veritable host of additional options are nicely documented and easily accessible via man youtube-dl.

shellcheck

I will assume that anyone spending significant some time at the command line will want to automate tasks using shell scripts. Bash itself is renowned for its many pitfalls, and even advanced scripters will from time to time bump into something unexpected. Unfortunately for us, a shell script has no undo button, and “unexpected” results may well be synonymous with “catastrophic” results.

Long intro short: we have a valuable tool on our side to guard ourselves against exactly this,shellcheck! In essence, it is a static analyser that will tell you where your script goes wrong.

Install shellcheck via your package manager of choice: Homebrew, Pacman, APT; build it from source, or run it inside your browser.

 $ brew install shellcheck  # pacman -S shellcheck  # apt-get install shellcheck 

This list may be of particular interest to you as it describes code samples that shellcheck can protect you against. To run, simply execute shellcheck my-script, it will read the shebang (#!) directive to decide whether to analyse as sh, bash or ksh.

As shown in the example output above, there is one syntax error, it’s marked in red: spaces surrounding the assignment. However, shellcheck goes beyond that. In yellow markings is a warning of a potentially catastrophic event: what if toDelete is ever empty? Granted, the example is somewhat contrived, without –no-preserve-root there will be no damage should the statement resolve to /, but my point still stands! Finally, in green you will find general warnings on potential future mishaps that are best not to be ignored.

As a closing remark on shellcheck: use the neat Syntastic Vim plugin to integrate the tool inside Vim itself, configuring when it should run, how it should behave, etc. The same script that generated the ouput above now looks like the following, from our favorite text editor.

multitail

For the sys-admins and dev-opses amongst us: stop using tail -f, and start using, multitail, tail on steroids! This ultimate log-viewer allows you to do a couple of really cool things that make it worth mentioning. Alternatively you could always either use tmux or screen to get in-shell multiplexing, or just use a modern terminal emulator allowing you to do the splitting like that, such as iTerm2 or Terminator, however in these cases you may miss some of the features below.

• Show multiple windows at the same time, in the same shell using ncurses.
• Merge multiple logs in the same window, for example the stdout and the stderr log of the same application.
• Perform filtering dynamically via in-menu editable regexes.
• Use the predefined color highlighters to make the logs more legible, or define your own, again with regular expressions.

You know the drill how to install:

 $ brew install multitail  # pacman -S multitail  # apt-get install multitail 

For an actual example, here is a screenshot of a window where I’m developing JRebel by attaching it to Tomcat, running the infamous petclinic project. At that time I needed both Tomcat’s own output and the JRebel one. Take note of the -CS flag, signifying “use this color scheme for all subsequent files”, followed by the name of the scheme.
As both logs color nicely with the Apache rules, they are set, finally followed by the actual paths of the logfiles.

 $ multitail -CS apache "$TOMCAT_HOME/logs/catalina.out" "$HOME/.jrebel/jrebel.log" 

tree

Our final tool in this post is the essential tree utility. Tree prints a nice, structured, tree-view of your directories, allowing you to instantly get an idea about the structure of your data, without having to ls, cd or z all over the place. If it is not yet pre-installed in your favourite *NIX, then grab it via your favourite package manager.

 $ brew install tree  # pacman -S tree  # apt-get install tree 

In its most basic form, you simply type $ tree to print the current folder’s structure.

Personally, I prefer to spice it up just a little bit, adding some flags to print human readable filesizes, hidden files, and a nice total sizecount: $ tree -ah --du.

And that is about all I have to tell you about tree. It’s really convenient to grep its output, it gives you an awesome representation of the filesystem, and I’m sure you’ll love it from the first moment.

That concludes my list of command line tools that you won’t think will change you live, but sure enough after some time you won’t imagine yourself not using them. In fact, you’ll likely curse every time you use a command-line-muggle’s computer without these great tools installed. What are the hidden gems of your command-line-fu? Share your favorite command line utilities in the comments below, I really would like to learn new tricks.

Working on the command line will make you more productive, even on Windows!

There’s an age-old discussion between the usability and friendliness of GUI programs, versus the simplicity and productivity of CLI ones. But this is not a holy war I intend to trigger or fuel. In the past, RebelLabs has discussed built-in JDK tools and received amazing feedback, so I feel an urge to share more non-JDK command line tools which I simply couldn’t live without.

I do firmly believe every developer who’s worth their salt should have at least some notion of how to work with the command line, if only because some tools only exist in CLI variants. Plus, because geek++!

All other nuances that people pour words over, like the choice of operating system (OSX of course, they have beautiful aluminum cases), your favorite shell (really it should be ZSH), or the preference of Vim over Emacs (unless you have more fingers than usual) are much less relevant. OK, that was a little flamewar-like, but I promise that will be the last of it!

So my advice would be that you should learn how to use tools at the command line, as it will have a positive impact on your happiness and productivity at least for half a century!

Anyway, in this post I want to share with you four-five lesser-known yet pretty awesome command line gems. As an added bonus I will also advise the proper way to use shell under Windows, which is a pretty valuable bit of knowledge in itself.

The reason I wanted to write this post in the first place is because I really enjoy using these tools myself, and want to learn about other command line tools that I don’t yet know about. So please, awesome reader, leave me a comment with your favourite CLI tools — that’d be grand! Now, assuming we all have a nice, workable shell, let’s go over some neat command line tools that are worth hearing about.

0. HTTPie

The first on my list is a tool called HTTPie. Fear not, this tool has nothing to do with Internet Explorer, fortunately. In essence HTTPie is a cURL wrapper, the utility that performs HTTP requests from the command line. HTTPie adds nice features like auto-formatting and intelligent colour highlighting to the output making it much more readable and useful to the user. Additionally, it takes a very human-centric approach to its execution, not asking you to remember obscure flags and options. To perform an HTTP GET, you simply run http, to post you http POST, what can be easier or more beautiful?

Almost all command line tools are conveniently packaged for installation. HTTPie is no exception, to install it, run the following command.

• On OSX use homebrew, the best package manager to be found on OSX: brew install httpie
• All other platforms, using Python’s pip: pip install --upgrade httpie

I personally use HTTPie a lot when developing a REST API, as it allows me to very simply query the API, returning nicely structured, legible data. Without doubt this tool saves me serious work and frustration. Luckily the usage does not stop at just REST APIs. Generally speaking, all interactions over HTTP, whether it’s inputting or outputting data, can be done in a very human-readable format.

I’d encourage you to take a look at the website, spend the 10 seconds it takes to install and give it a go yourself. Try to get the source of any website and be amazed by the output.

Protip: Combine the HTTPie greatness with jq for command line JSON manipulation or pup for HTML parsing and you’ll be unstoppable!

1. Icdiff

At ZeroTurnaround I am blessed to work with Mercurial, a very nice and easy to use VCS. On OSX the excellent GUI program SourceTree makes working with Mercurial an absolute breeze, even with the more complex stuff. Unfortunately I like to keep the number of programs/tabs/windows I have open to an absolute minimum. Since I always have a terminal window opened it makes sense to use the CLI.

All was fine and well apart from one single pitfall in my setup. This was a feature I could barely go without: side-by-side diffs. Introducing icdiff. Of all the tools I use each day, this is the one I most appreciate. Let’s take a look at a screenshot:

By itself, icdiff is an intelligent Python script, smart at detecting which of the differences are modifications, additions or deletions. The excellent colour highlighting in the tool makes it easy to distinguish between the three types of differences mentioned.

To get going with icdiff, do the following:

• Via homebrew once again: brew install icdiff
• Manually grab the Python script from the site above and put it in your PATH

When you couple icdiff with a VCS such as Mercurial, you’ll see it really shine. To fully integrate it, you’ll need to complete two more configuration steps, already documented here. The gist of the instructions is to first add a wrapping script that allows the one-by-one file diff of icdiff to operate on entire directories. Secondly you need to config your VCS to actually use icdiff. The link above shows the details of configuring it for Mercurial, but porting this to Git shouldn’t be so hard.

2. Pandoc

In the spirit of “practice what you preach” I set out to write this entire blogpost via a CLI. Most of the work was done using MacVim, in iTerm2 on OSX. All of the text was written and formatted using standard MarkDown syntax. The only issue to arise here is that it’s pretty difficult sometimes to accurately guess how your eventual text will come out.

This is where the next tool comes in: Pandoc. A program so powerful and versatile it’s a wonder it was GPL’d in the first place. Let’s take a look at how we might use it.

pandoc -f markdown -t html blogpost.md > blogpost.html 

Think of a markup format, any markup format. The chances are, Pandoc can convert it from one format to any other. For example, I’m writing this blogpost in Vim and use Pandoc to convert it from MarkDown into HTML, to actually see the final result. It’s a nice thing, needing only my terminal and a browser, rather than being tied to a particular online platform, fully standalone and offline.

Don’t let yourself be limited by simple formats like MarkDown though, give it some docx files, or perhaps some LaTeX. Export into PDF, epub, let it handle and format your citations. The possibilities are endless.

Once again brew install pandoc does the trick. Did I mention I really like Homebrew? Maybe that should have made my tool list! Anyway, you get the gist of what that does!

3. Moreutils

The next tool in this post is actually a collection of nifty tools that didn’t make it into coreutils:Moreutils. It should be obtainable under moreutils in about any distro you can think of. OSX users can get all this goodness by brewing it like I did throughout this post:

brew install moreutils 

Here are a list of the included programs with short descriptions:

• chronic: runs a command quietly unless it fails
• combine: combine the lines in two files using boolean operations
• ifdata: get network interface info without parsing ifconfig output
• ifne: run a program if the standard input is not empty
• isutf8: check if a file or standard input is utf-8
• lckdo: execute a program with a lock held
• mispipe: pipe two commands, returning the exit status of the first
• parallel: run multiple jobs at once
• pee: tee standard input to pipes
• sponge: soak up standard input and write to a file
• ts: timestamp standard input
• vidir: edit a directory in your text editor
• vipe: insert a text editor into a pipe
• zrun: automatically uncompress arguments to command

As the maintainer hints himself sponge is perhaps the most useful tool, in that you can easily sponge up standard input into a file. However, it is not difficult to see the advantages of some of the other commands such as chronic, parallel and pee.

My personal favourite though, and the ultimate reason to include this collection, is without doubtvipe.

You can literally intercept your data as it moves from command to command through the pipe. Even though this is not a useful tool in your scripts, it can be extremely helpful when running commands interactively. Instead of giving you a useful example I will leave you with a modified fortune!

4. Babun

These days the Windows OS comes packaged with two different shells: its classic command line, and PowerShell. Let’s completely ignore those and have a look at the proper way or running command line tools under Windows: Babun! The reason this project is amazingly awesome is because it actually brings all the goodness of the \*NIX command line into Windows in a completely pre-configured no-nonsense manner.

Moreover, its default shell is my beloved ZSH, though it can very easily be changed to use Bash, if that’s your cup of tea. With ZSH it also packages the highly popular oh-my-zsh framework, which combines all the benefits of ZSH with no config whatsoever thanks to some very sane defaults and an impressive plugin system.

By default Babun is loaded with more applications than any sane developer may ever need, and is thus a rather solid 728 MBs(!) when expanded. In return you get essentials like Vim pre-installed and ready to go!

Under the hood Babun is basically a fancy wrapper around Cygwin. If you already have a Cygwin install you can seamlessly re-use that one. Otherwise it will default to its own packaged Cygwin binaries, and supply you with access to those.

Some more points of interest are that Babun provides its own package manager, which again wraps around Cygwin’s, and an update mechanism both for itself and for oh-my-zsh. The best thing is that no actual installation is required, nor is the usual requirement of admin rights necessary, so for those people on a locked down PC this may be just the thing they need!

I hope this small selection of tools gave you at least one new cool toy to play with. As for me, it seems it is time to look at command line browsers before writing a following blogpost, to fully ditch the world of the GUI!

By all means fire up any comments or suggestions that you have, and let’s get some tool-sharing going on. If you just want to chat just ping RebelLabs on Twitter: @ZeroTurnaround, they are pretty chatty, but great smart people.

一：下载及安装
站长百科下载站最新版下载地址：http://down.zzbaike.com/download/KeePass–1257.html，下载安装包解压后双击安装文件根据安装向导就可以安装。

选择I accept意思也就是我同意，然后next（下一步），根据提示继续next就可以安装成功。
软件是英文的，安装好之后我们看到界面仍旧都是英文的，我们可以去http://keepass.info/translations.html，中下载简体中文插件复制放到安装目录下，运行软件“KeePass”，点击“View”菜单中“Change Language”命令，选择“简体中文”重新启动程序即可。

二：使用软件
经过上面的步骤，我们返回到桌面双击keepass的快捷键，就可以看到软件的语言已经变成中文的了

这样就可以方便我们的使用了。
如果是第一次使用，我们首先的是要创建数据库，也就是存放密码的数据库，KeePass将会把你的所有密码存储在这个数据库中。
单击菜单上的“文件—新建”，选择数据库存放的路径

选择一个路径来保存我们的数据库，然后点击保存，

这里需要填入数据库管理密码，并要确认密码，我们同时要勾选上密匙文件，并选择密钥的保存位置（可以选择不用密钥）。这样将来在开启数据库时就要“主密码”和“密钥文件”同时具备才行。输入完毕后点击“确定”然后点击创建

鼠标在黑色区域划过生成的密码位数在下方可以很清楚的看到，然后点击确定

在这里描述或者不描述都可以，点击确定后就进入主窗口并可以看到一条示例记录，点击示例记录在下方可以看到网址和密码并且也创建时间。

主窗口的左边是密码群组，各个群组又可建立子群组。右边是你的密码记录。密码记录收纳于不同的密码群组中。你可以使用Keepass默认的密码群组，或删除它们，创建自己的密码组。

在主窗口右边单击右键，选择“添加记录…”，就可以编辑你的记录了：记录标题，用户名，网址，密码，备注等。可以空着不填。确认后就完成了一条记录了，在主窗口右边的子窗口中看到刚才新增的密码条目。

当你再次使用这个文件时，选中该条记录，在记录上右击鼠标就可以真正使用它了。你可以将用户名拷贝后，就可以在其它的任何软件中粘贴了，还可以将用户名拖放到其它窗口中。最后，一定要记住保存密码，点击“文件->保存”，或工具栏上的保存按钮。

提示：随着数据库里的记录数目的逐步增多，通过“编辑”菜单中的“在数据库中查找”或“在此群组内查找”命令可以迅速的找到要查的信息。另外，我们可以把数据库导出为TXT、HTML、XML、CSV等格式，导入CSV、TXT、KeePass数据库等格式的文件。

三：数据库的配置

点击“文件->数据库设置…”，在弹出的窗口的选择“安全”按钮创建一个加密算法，并设置密钥的加密次数（如果选择生成密钥的话）。通常加密次数的数量级达到10万，也就足够了。

四：Keepass数据的备份
首先要备份KeePass.exe所在目录中的KeePass.ini文件。其次，备份你所保存的密码数据库文件（*.kdb）。如果你生在了密钥，还要保存密钥文件。以上文件打包后，可以放入多动存储装置中，或放入网络空间。
提示：如果用户的密码记录经常变动，那么相应的KeePass数据也要经常备份。保存好你的数据。尽管你有数不清的密码，但只需看好一个KeePass数据备份就可以了。
五：密码生成器
在添加记录时，我们可以利用密码生成器来生成复杂的密码，点击“密码”右侧的“生成”按钮，调出“密码生成器”属性框，然后，点击“确定”按钮即可自动生成随机密码。通过点击“***”按钮将密码明文显示，清楚的看到由生成器所产生的字符串。

六：Keepass常用设置

打开【工具】->【选项…】，就可以对Keepass作设置了。

在“安全”选项卡中勾上：设定锁定主窗口时间：300（自己设置适合的时间）
自动清空剪贴板时间，设置时间为3秒
“高级”选项卡中根据需要勾上适合的选项。

我们现在生活中各个方面都需要用到密码，网站，邮箱，论坛，银行卡等等，使用keepass可以方便的为我们服务记录各种不同的密码，使我们的操作更加省时高效，管理更方便安全。

       最容易被一些人搞错地方，就是时间设置问题，所以碰到这种情况，请首先检查你的电脑时间设置是否正确，如果不正确将导致助理从你的电脑上取到的时候，已经不在服务器发送给助理的有效时间范围内，请你核对你的时间设置是否正确。将“自动与internet时间服务器同步”取消后问题消失。如果还是不行，请看下面。

========================================================================

一、XP系统下IE7.0 访问https站点故障排除：

         默认情况，XP系统下通过XP版本的IE 7 浏览器，访问https加密的站点都会出现这个提示，这个是IE7阅览器的提示，必须再次点“继续浏览此网站（不推荐）”才能查看页面信息。每次访问Https站点都需要重复点击，在操作上带来很大的麻烦。下面我们就通过安装证书步骤来解决此问题。

        第一步：当我们用IE7浏览Https站点后会在地址栏右边出现一个红色的“证书错误”的提示，我们点该红色按钮，然后选择“查看证书”。

第二步：在打开的“查看证书”窗口中的“常规”标签中点右下角的“安装证书”按钮。

第三步：出现“证书导入向导”后点“下一步”按钮继续。

第四步：选择证书存储的系统区域，通过“浏览”按钮设置将证书保存为“受信任的根证书颁发机构”。

第五步：之后在安全警告窗口中选择“是”按钮来安装该证书。

第六步：设置完毕后我们再次访问该https站点就不会出现任何问题，也不会再出现这个错误提示了。

========================================================================

　 二、Vista系统下IE7.0 访问https站点故障排除：

1、打开注册表，找到
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shell 主键(项)（如果没有新建一个），
2、单击shell这个主键，在下再新建一个名为 notepad 的主键，在右面的窗口中，把默认项的值改成：用记事本打开 或者其他你喜欢的字样。
3、再在notepad主键下新建一个 command 主键。在右面的窗口中，把默认项的值改成：
notepad %1 （注意notepad和%符号之间要空一格）关闭注册表。
现在在任意一个文件上单击鼠标右键就有“用记事本打开”这一功能了。经体验是一个很好的方法。当然用其它软件也可添加这一功能。（收集学习）

另可以：打开注册表编辑器，找到下面的键值：HKEY_CLASSES_ROOT\*，接着新建一个名为 shell的子项，接着再它的下方新建名为“Notepad”，然后在右侧窗口中将其默认值改为“使用记事本打开”，最后在“Notepad”项下新建名为“command”的子项，在右侧窗口中将其值改为：notepad.exe %1就可以了。

保存一下内容为*.reg运行即可!

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shell]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shell\playboyjin]
@="用记事本打开"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shell\playboyjin\command]
@="notepad.exe \"%1\""

如何添加鼠标右键DOS命令
A:(1)打开注册表编辑器。 (2)打开HKEY_LOCAL_MACHINE\Software\classes\directory\shell主键并选中它。在右侧窗口中新建一个项，命名为CommandPrompt，然后把它的数值数据改为command。 (3)在CommandPrompt下新建一个项，命名为command，改其数值数据为cmd /k cd %1，退出OK了。 (4)鼠标右键单击任何文件夹，在弹出的菜单中，你就可以选择command命令了。

B:保存下边的代码到一个记事本文件，并把扩展名改为“.bat”，执行一次这个文件（以后就没用了），找一个文件夹，打开鼠标右键看看吧！

reg add "HKCR\*\shell\ms-dos" /ve /d ms-dos /f
reg add "HKCR\*\shell\ms-dos\command" /ve /d "cmd.exe /k cd %%1" /f
reg add "HKCR\Folder\shell\ms-dos" /ve /d ms-dos /f
reg add "HKCR\Folder\shell\ms-dos\command" /ve /d "cmd.exe /k cd %%1" /f

本文来自CSDN博客，转载请标明出处：http://blog.csdn.net/bhsky/archive/2009/02/02/3858883.aspx

@echo off
echo proj 本地测试环境
echo.
c:
cd \
if not exist proj-test\con md proj-test
if exist proj-test\hosts.bak goto backup_exists
echo 正在创建备份……
cd \windows\system32\drivers\etc
copy /y hosts \proj-test\hosts.bak > null
echo 完成！
echo.
goto backup_start
:backup_exists
echo 备份文件已经存在，无需备份。
echo.
:backup_start
echo 正在写入测试数据……
echo 127.0.0.1       localhost > hosts
echo 192.168.3.170   proj.com >> hosts
echo 192.168.3.170   www.proj.com >> hosts
echo 192.168.3.170   pics.proj.com >> hosts
echo 192.168.3.170   files.proj.com >> hosts
echo 完成！
echo.
echo 建立 proj 本地测试环境完成。按任意键退出……
pause > null

@echo off
echo proj 本地测试环境
echo.
c:
cd \
if not exist proj-test\hosts.bak goto backup_not_exists
echo 正在还原备份……
copy /y \proj-test\hosts.bak \windows\system32\drivers\etc > null
cd \windows\system32\drivers\etc
if exist hosts del /q hosts
ren hosts.bak hosts
echo 完成！
echo.
echo 正在移除备份……
cd \
rmdir /s/q \proj-test\
echo 完成！
echo.
goto backup_done
:backup_not_exists
echo 备份文件不存在，无法恢复。
echo.
:backup_done
echo 退出 proj 本地测试环境完成。按任意键退出……
pause > null

卸载服务：sc delete serviceName

or check HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices

以上修改要重起机器才能生效

另：
启动服务：net start serviceName 或sc start serviceName
停止服务：net stop serviceName 或sc stop serviceName

[SC命令 的参数可以配置指定的服务，检索当前服务的状态，也可以停止和启动服务（功能上类似NET STOP/START命令，但SC速度更快且能停止更多的服务）。]