另：Xfce更新到4.10 后会发现Panel居左了。解决办法（来自这里：https://makandracards.com/makandra/4489-right-align-or-center-panel-items-in-xfce）：

Right-align or center panel items in XFCE
Add a separator between left-aligned and right-aligned items.
In the separator properties, set the style to “Transparent” and check “Expand”.
The separator will now grab all available space and hence push the right-hand items into the corner.

You can also use this trick to center panel items by using two separators (one on the left, one on the right side).

Install Dropbox via command line

The Dropbox daemon works fine on all 32-bit and 64-bit Linux servers. To install, run the following command in your Linux terminal.

Next, run the Dropbox daemon from the newly created .dropbox-dist folder.

命令行助手：
Dropbox Linux CLI
下载：
http://dl.getdropbox.com/u/43645/dbcli.py

上传文件到dropgox :
web 方式：
PHP Dropbox Uploader

http://dropboxwiki.com/PHP_Dropbox_Uploader

https://github.com/jakajancar/DropboxUploader/

Python:

https://github.com/jncraton/PythonDropboxUploader

http://dropboxwiki.com/Dropbox_Addons#PHP

How To Access Dropbox Behind a Firewall or Pr_o_x_y ,使用P.r.o.x.yChains

恶意登录：

我能说脏话吗？

话说ip基本上有可能是变动的，变动不大的而且可以掌握的就是我个人的ip.因此，后来又把上面的代码替换为了下面的：

再在类的构造函数中加上：

Over at illuminea, we’ve been migrating WordPress sites for years. So we thought we’d seen it all when it came to WordPress migration. And yet, recently we encountered an issue that we had never dealt with before, that puts a snag in the ease with which you can move WordPress sites: data serialization.

One of the reasons we love WordPress is because it’s so future-proof. What I mean by that is that once you have created a WordPress site, you aren’t stuck where you are for the following reasons:

• Content is separate from form so at any point you can completely redesign your site while retaining content and link structure. This is important to ensure you don’t lose traffic from search engines and inbound links.
• As long as the WordPress software continues to be developed, it will continue to support modern web technologies so users are not left with an archaic system that, for example, adores IE7 but doesn’t know what HTML5 is.
• Your site is portable. You need to move a site to another server, or even another domain name? No problem. A few steps related to find-and-replace, exporting and importing the database, and setting up global 301 redirects (if you’ve changed domains) and you’re there.

All the above is true, except the data portability point. It’s not quite as true as I thought it was.

Data serialization and its impact on data portability

(I am a big newbie when it comes to data serialization, so the following is based on what I’ve managed to learn over the while and could very well be inaccurate/wrong.)

It seems that developers use data serialization in order to improve performance or efficiency in a database. Instead of creating a new table for data, or storing data in a table which could end up having wasteful empty fields, you can keep all the data in an array in one field. This leads to saved space and simplified SQL statements. Serialized data is stored and recovered using PHP’s serialize() and unserialize() functions. Terri Swallow explains how using serialized data for her multi-user plugin helped save her from creating hundreds of new options for every new user created.

Here’s an example of serialized data from Andrew Nacin:

But there are serious drawbacks to using serialized data. One problem is that you can’t run a MySQL query on serialized data. The data would have to be pulled out of the table via PHP, unserialized, and then searched using PHP instead of MySQL (thanks to Catch My Fame for explaining this). So let’s say you are storing user data in serialized format, but you want to find out how many of your users are from Australia, you can’t get that info easily.

A serious problem, in my opinion, is the impact serialization has on data portability. It makes it near-impossible to port a WordPress site from one domain to another without losing data. Another or to port data from WordPress into another programming language – admittedly a rare occurrence, but a possible one that needs to be considered.

There are developers out there who are very frustrated by the use of serialized data:

An anonymous comment left on the PHP manual entry for serialize():

Please! please! please! DO NOT serialize data and place it into your database. Serialize can be used that way, but that’s missing the point of a relational database and the datatypes inherent in your database engine. Doing this makes data in your database non-portable, difficult to read, and can complicate queries. If you want your application to be portable to other languages, like let’s say you find that you want to use Java for some portion of your app that it makes sense to use Java in, serialization will become a pain in the buttocks. You should always be able to query and modify data in the database without using a third party intermediary tool to manipulate data to be inserted…That’s not to say serialize() is useless. It’s not…Just don’t abuse serialize because the next guy who comes along will have a maintenance or migration nightmare.

Alexander Scammon: “WordPress does a silly thing. It has serialized data inside its database.”

Serialized data usage that can have a serious impact on WordPress portability:

Some widget data (though for some reason we’ve never had issues retaining widgets via a database dump)
Some theme settings
Plugin data

It was related to serialized plugin data that we had our first encounter with data serialization. We had installed a plugin to help a client manage a technical issue on their site without having to get too technical. They entered hundreds of entries in the plugin, but upon moving the site from development to production, the data disappeared. By that point, there was no way to recover it unfortunately, but we had definitely learned a painful, important lesson.

So what do we do?

Some suggestions:

Theme and plugin developers: please seriously consider whether the benefits of serializing your data outweigh the potential future problems it could cause.
Theme and plugin developers: if you must use serialized data, please try to make sure there’s some way to export and import the data. Even a simple .csv export is better than nothing.
WordPress users: try to ascertain before using a theme or plugin whether the data is stored in a serialized format.

But let’s say you find yourself with a database that includes serialized data. Here are some tools created by generous souls that might be able to help you port your data without losing it:

Peach – an online utility that aims to deal with the fact that WordPress stores URLs in serialized format, which makes it hard to move a site from one domain to another, or from staging to production. To use this tool (which works best in Chrome) ou drag-and-drop an .sql file into the square in the middle of the page, and set a new domain.

WordPress Search and Replace Tool – this script can also handle multiply nested serializations and multi-byte Unicode changes, which is important now that internationalized domain names are allowed. The code will work for any platform that stores PHP serialized arrays in a MySQL database (Drupal, Joomla, etc.). You must delete the script from your server once you’re finished with it.

fix_serialization.php – Not much description provided with this tool

本文转自：Data portability and data serialization in WordPress | WP Garage

Posted via UltraBlog.vim.

以前我就是用的这种方式。

使用官方提供的GetLatestScript插件

下面这段介绍引用自 滇狐博客 ：

安装完毕后，创建文件 ~/.vim/GetLatest/GetLatestVimScripts.>dat，按照这样的格式编写你的自动下载配置文件：

每行写一个插件的下载信息。插件 id 就是在 Vim 主页下载插件时 URL 中的 script_id= 后面的那个数字。第二个参数是前一次成功下载到的插件文件编号，第一次使用的时候该参数写 0，成功使用一次后会自动被修改为该插件最新版本的文件编号。第三个参数是该插件下载成功后是否自动安装，如果要自动安装的话就写上 :AutoInstall:。滇狐不建议使用自动安装，因此第三个参数建议省略不要写。第四个参数是插件的名称，一般和下载到的插件的文件名相同，当然即使不同也不会造成太大影响，这个参数主要用于防止某些插件自动将自己加入到这张列表，并非用于指定插件的下载文件名，更详细情况请参看该插件的文档。

Pathogen

与前面的相比，利用Pathogen 和git submodule来管理插件就方便多了。
这里有一篇很好的介绍：《Synchronizing plugins with git submodules and pathogen》 ，附带视频：

vundle

vundle是目前我在使用的插件管理方式
利用vundle的好处是，更新和安装新插件都非常方便。
安装插件只要写一条:
Bundle ‘xxxx’
然后再在vim中执行：
BundleInsall
要卸载的话，只要注释掉或删除这一句就可以。
更新插件与安装的命令相同，不过后面要加一个感叹号。

不好的地方是，由于一般我们喜欢让.vim目录处于git版本控制之下，而
bundle目录下面通过git clone过来的插件目录下面也有.git目录，在父目录提交时
，有.git的目录中的文件不会提交到远程repo.

另外还有neobundle

这是一个改进版的vundle,支持更多的repo格式(vundle只支持github上的repo)。基本功能同vundle。

muzuiget的方法

muzuiget的方法也不错。
vimfiles/scripts at master · muzuiget/vimfiles · GitHub
我的vimfiles方案 | 七星庐

vim-flavor

vim-flavor其实其实现还是蛮好的，不过
作者不太喜欢考虑插件版本的兼容性问题，这个问题我提交过issue,作者表示不愿意修改（见issue#14 ).
vim-flavor可以：
管理插件的安装/更新/卸载
管理插件的版本号与依赖关系（这一点上面所有插件都没有做到）
vim-flavor不可以：
安装版本号中带特殊字符的插件（如1.1@1 or v1.2,这一点非常蛋疼)
因为最后一条，我弃用vim-flavor并开始使用vundle了。

Posted via UltraBlog.vim.

下面还有一种方法，不过使用的命令比上面的复杂：

This is the best way:

http://github.com/guides/completely-remove-a-file-from-all-revisions

Just be sure to backup the copies of the files first.

EDIT

The edit by Neon got unfortunately rejected during review.
See Neons post below, it might contain useful information!

E.g. to remove all *.gz files accidentally committed into git repository:

That still didn’t work for me? (I am currently at git version 1.7.6.1)

Not sure why, since I only had ONE master branch. Anyways, I finally got my git repo truely cleaned up by pushing into a new empty and bare git repository, e.g.

(yes!)

Then I clone that to a new directory and moved over it’s .git folder into this one. e.g.

(yeah! finally cleaned up!)

After verifying that all is well, then you can delete the ../largedotgit and ../tmpdir directories (maybe in a couple weeks or month from now, just in case…)

Posted via UltraBlog.vim.

如果已经安装了ruby,就不用安装rvm 了。
Archlinux用户建议用pacman 安装ruby,方便省事。

Archlinux安装RVM教程：
https://wiki.archlinux.org/index.php/RVM

添加当前用户到rvm 组

查看下添加成功了没：

再注销，登录。

* To start using RVM you need to run `source /etc/profile.d/rvm.sh`
in all your open shell windows, in rare cases you need to reopen all shell windows.

安装依赖

注意路径后面不能带/，不然它还是会报错。。。。。

答案：http://stackoverflow.com/questions/7918804/how-do-i-keep-all-gems-in-gemfile-compatible-after-an-update
rake aborted解决办法：

再装：

Deploying to Github Pages

http://octopress.org/docs/deploying/github/

首次deploy 之前的准备活动
创建 username.github.com 仓库
执行rake setup_github_pages来设置。

This will:

Ask you for your Github Pages repository url.
Rename the remote pointing to imathis/octopress from ‘origin’ to ‘octopress’
Add your Github Pages repository as the default origin remote.
Switch the active branch from master to source.
Configure your blog’s url according to your repository.
Setup a master branch in the _deploy directory for deployment.

生成静态页面：

接下来把博客源码push上去：

Configuring Octopress

配置
略，见 http://octopress.org/docs/configuring/

写日志

详见 http://octopress.org/docs/blogging/
写完了之后

如果想本地预览一下效果，可以用

要注意的是，如果修改源码和配置，是在source 分支修改和提交。
而发布日志，也是在source分支，rake deploy会自动将生成的静态页面push到master分支。因此，master分支的内容不用你管。

rake watch 检测文件变化，实时生成新内容
rake preview 监听本机4000端口，可查看生成页面效果。

我的github博客页面：http://github.ihacklog.com//

个性化
文档： http://octopress.org/docs/theme/template/
修改定制文件/source/_includes/custom/head.html 把google的自定义字体去掉或自行定义，如我的（自己下载了google font)：

我把下载的google font放在 source/assets/font 目录下面。

图片发布
我把图片放在source/static 目录。
在文章中引用（注意URL前面的/)：

个性域名
先去给域名建立一个CNAME记录，指向 username.github.com ,如 ihacklog.github.com
在source目录下建一个名为CNAME的文件，然后将自己的域名输入进去
如：

文档： http://help.github.com/pages/

其它，如sidebar的修改等，可参考文档。http://octopress.org/docs/theme/template/
我这就不写了。

其它可参考的文章： http://blog.devtang.com/blog/2012/02/10/setup-blog-based-on-github/

(ps:本文内容全部通过UltraBlog.vim发送)

安装依赖库

在Archlinux下安装：

修正：
经测试发现，pytho-markdown不能正常处理pre标记（代码中若有空行会被p标记包裹),后来xbot(UltraBlog.vim的作者)说他一直在用python-markdown2,速度比python-markdown
要快，且没有发现此问题，于是我也把python-markdown
卸载了，安装python-markdown2 .

安装插件

从git clone :
这是我的一个fork版，做了一点点修改：

ps:此插件支持vundle.

配置

配置sample:

把上面的内容用户名/密码/博客地址修改成你自己的。保存下。

ps:这个python2-markdown库解析貌似有点问题，
在pre中包含的东西如有空行，会加入p标记。

然后在.vimrc中加上：

截图：

基本命令

在博客中输入代码的话，建议使用pre标记，以便在WP中用插件高亮代码。

演示

这里录了一小部分演示，时间有限，就没有把全部命令演示了。。。

– EOF –
markdown语法：Daring Fireball: Markdown Syntax Documentation

Posted via UltraBlog.vim.