manual - Kenyth Zeng on Diigo

29 Sep 09

gt *i_CTRL-<PageDown>* *i_<C-PageDown>*
Go to the next tab page. Wraps around from the last to the
first one.
{count}gt Go to tab page {count}. The first tab page has number one.
2 more annotations...
- gT Go to the previous tab page. Wraps around from the first one
  to the last one.
- :tabs List the tab pages and the windows they contain.
  Shows a ">" for the current window.
  Shows a "+" for modified buffers.

28 Sep 09

RubyGems Manuals

docs.rubygems.org/shelf - Preview

manual gem ruby

25 Sep 09

Tor: 匿名在线

tor.zuo.la/index.html.zh-cn - Preview

tor Chinese manual GFW workaround

22 Sep 09

Bash Reference Manual

www.gnu.org/...bashref.html - Preview

linux shell reference manual scripting bash athand unix programming starred

The preamble is prefixed to each string contained within the braces, and
the postscript is then appended to each resulting string, expanding left
to right.

02 Sep 09

gitignore(5)

www.kernel.org/...gitignore.html - Preview

git manual

An optional prefix ! which negates the pattern
foo/ will match a
directory foo and paths underneath it, but will not match a
regular file or a symbolic link foo
2 more annotations...
- git treats the pattern as a shell glob suitable
  for consumption by fnmatch(3)
- wildcards in the pattern will not match a / in the pathname.

01 Jun 09

Git User's Manual (for version 1.5.3 or newer)

www.kernel.org/...user-manual.html - Preview

git scm manual toread athand shell scripting programming reference

A freshly cloned repository contains a single branch head, by default
named "master"
The commit
representing a merge can therefore have more than one parent, with
each parent representing the most recent commit on one of the lines
of development leading to that point.
48 more annotations...
- git branch <branch> <start-point>
- accept an arbitrary commit
- HEAD is "detached".
- The "master" branch that was created at the time you cloned is a copy
  of the HEAD in the repository that you cloned from.
- slash-separated path name
  starting with "refs"
- It will not touch any of your own branches—not even the
  "master" branch that was created for you on clone.
- The command "git fetch", with no arguments, will update all of the
  remote-tracking branches to the latest version found in her
  repository.
- git remote add
- search through the project's
  history to find the particular commit that caused the problem.
- $ git show HEAD~4 # the great-great-grandparent
- include a
  comment with the tag, and possibly sign it cryptographically, then you
  should create a tag object
- Telling git about your changes.
- At the beginning, the content of the index will be identical to
  that of the HEAD. The command "git diff —cached", which shows
  the difference between the HEAD and the index, should therefore
  produce no output at that point.
- $ git commit -a
  will update the index with any files that you've modified or removed
  and create a commit, all in one step.
- it's a good idea to begin the commit message
  with a single short (less than 50 character) line summarizing the
  change, followed by a blank line and then a more thorough
  description.
- tell git to ignore certain files by creating a file called .gitignore
  in the top level of your working directory
- if the same file is
  modified in two different ways in the remote branch and the local
  branch—then you are warned
- Files with conflicts are marked specially in the index, so until you
  resolve the problem and update the index, git-commit(1) will
  fail:
- While you are in the middle of working on something complicated, you
  find an unrelated but obvious and trivial bug. You would like to fix it
  before continuing. You can use git-stash(1) to save the current
  state of your work, and after fixing the bug (or, optionally after doing
  so on a different branch and then coming back), unstash the
  work-in-progress changes.
- by default "git pull"
  merges from the HEAD branch of the origin repository.
- a branch that is created from a remote branch will pull
  by default from that branch.
- $ git pull . branch
  
  $ git merge branch
- the simplest way to submit them may
  just be to send them as patches in email
- commands that accept repository URLs as arguments will also accept a
  local directory name
- you push
  your personal repo ------------------> your public repo
  ^ |
  | |
  | you pull | they pull
  | |
  | |
  | they push V
  their public repo <------------------- their repo
- The resulting directory proj.git contains a "bare" git repository—it is
  just the contents of the ".git" directory, without any files checked out
  around it.
- scp, rsync
- git-daemon(1); it will
  listen on port 9418.
- an inetd service
- force git push
- $ git push ssh://yourserver.com/~you/proj.git +master
- while there is nothing wrong with git's support for shared
  repositories, this mode of operation is not generally recommended
- Git's ability to quickly import and merge patches allows a
  single maintainer to process incoming changes even at very
  high rates.
- The gitweb cgi script provides users an easy way to browse your
  project's files and history without having to install git
- ("topic branches"), each
  containing a logical grouping of patches.
- merge changes in from
  Linus by default.
- This is where you
  see the value of keeping each patch (or patch series) in its own branch. It
  means that the patches can be moved into the "release" tree in any order.
- Some time later when enough time has passed and testing done, you can pull the
  same branch into the "release" tree ready to go upstream.
- So the ideal is usually to produce a series of patches such that:
  
  Each patch can be applied in order.
  
  Each patch includes a single logical change, together with a
  message explaining the change.
  
  No patch introduces a regression: after applying any initial
  part of the series, the resulting project still compiles and
  works, and has no bugs that it didn't have before.
  
  The complete series produces the same end result as your own
  (probably much messier!) development process did.
- keep the history in mywork a simple series of
  commits without any merges
- This will remove each of your commits from mywork, temporarily saving
  them as patches (in a directory named ".git/rebase-apply"), update mywork to
  point at the latest version of origin, then apply each of the saved
  patches to the new mywork. The result will look like:
  o--o--O--o--o--o <-- origin
  \
  a'--b'--c' <-- mywork
- $ git commit --amend
- The index contains all the information necessary to generate a single
  (uniquely determined) tree object.
- The index enables fast comparisons between the tree object it defines
  and the working tree.
- The index is thus a sort of temporary staging area, which is filled with
  a tree which you are in the process of working on.
- changeset
  
  BitKeeper/cvsps speak for "commit". Since git does not
  store changes, but states, it really does not make sense to use the term
  "changesets" with git.
- rebase
  
  To reapply a series of changes from a branch to a
  different base, and reset the head of that branch
  to the result.
- refspec
  
  A "refspec" is used by fetch and
  push to describe the mapping between remote
  ref and local ref. They are combined with a colon in
  the format <src>:<dst>, preceded by an optional plus sign, +.
  For example: git fetch $URL refs/heads/master:refs/heads/origin means "grab the master
  branch head from the $URL and store
  it as my origin branch head". And git push $URL refs/heads/master:refs/heads/to-upstream means "publish my
  master branch head as to-upstream branch at $URL". See also
  git-push(1).

07 May 09

Screen - Copy and Paste

web.mit.edu/...screen_11.html - Preview

screen linux shell commands starred system-administration manual doc

(C-a [, C-a C-[, C-a ESC)
The copy range is specified by setting two marks. The text between these
marks will be highlighted. Press space to set the first or second
mark respectively.

05 May 09

CVS Howto - Eclipsepedia

wiki.eclipse.org/...CVS_Howto - Preview

cvs howto eclipse opensource manual

01 May 09

The Kernel Virtual Machine - Community Ubuntu Documentation

help.ubuntu.com/KVM - Preview

ubuntu virtualization linux kvm manual

Ubuntu uses kvm as the backend virtualisation technology and libvirt as its toolkit/API. Libvirt frontends for managing VMs include virt-manager (GUI) or virsh (CLI).
it has been designed to be run on Ubuntu Server Edition to host server operating systems.

28 Apr 09

Apache Felix - Apache Felix Usage Documentation

felix.apache.org/...felix-usage-documentation.html - Preview

Felix OSGi getting-started doc manual

install file:bundle/simple.jar
If a bundle is updated or uninstalled and it was exporting packages, these packages are not removed until the framework is refreshed using the PackageAdmin service. The Felix shell offers a convenient refresh command for this purpose.
3 more annotations...
- install bundles from a remote URL
- those starting with "org.osgi" are standard OSGi properties
- It is possible to use system properties to specify the values of properties in the conf/config.properties file.

23 Apr 09

UpgradeNotes - Community Ubuntu Documentation

help.ubuntu.com/...UpgradeNotes - Preview

ubuntu upgrade doc starred athand cheatsheet manual

To find your Ubuntu version:
```
lsb_release -a
```

10 Feb 09

Bugzilla Installation

www.bugzilla.org/...installation.html - Preview

scm install manual doc opensource

the others are easier to
configure, and therefore many people replace Sendmail with Postfix or
Exim.

09 Jan 09

FreeMarker Manual - FAQ

freemarker.sourceforge.net/...app_faq.html - Preview

FreeMarker manual doc reference view java mvc

FreeMarker is not tied to Servlets, networking or the Web
No servlet specific scopes and other highly technical things in templates. It was made for MVC from the beginning, it focuses only on the presentation.
4 more annotations...
- Locale sensitive number and date formatting by default.
- Macros and functions are just variables (compare it to how JSP custom tags work), so they can be easily passed around as parameter values, put into the data-model, ...etc, just like any other value.
- Virtually unnoticeable delay when visiting a page for the first time (or after it was changed), because no expensive compilation happens.
- JSP tag libraries work without modification in FreeMarker templates, if they are not using .tag files

FreeMarker Manual - The template at a glance

freemarker.org/...dgui_quickstart_template.html - Preview

FreeMarker manual doc reference view java mvc

FreeMarker
Template Language tags
start with #.
(User-defined FTL tags use @ instead of
#, but they are an advanced topic.)
5 more annotations...
- <#-- and -->.
- With FTL tags you refer to so-called directives. This is the same kind of relationship as between HTML tags
  (e.g.: <table> and
  </table>) and HTML elements (e.g.,
  the table element) to which you refer to with the HTML tags.
- <#list sequence as
  loopVariable>repeatThis</#list>
- <#include "/copyright_footer.html">
- (When
  user isn't missing, this template behaves exactly
  like if !"Anonymous" were not there):

FreeMarker Manual - The data-model at a glance

freemarker.org/...dgui_quickstart_datamodel.html - Preview

FreeMarker manual doc reference view java mvc

act as directories
Hashes store other variables (the so
called subvariables)
1 more annotations...
- they
  don't store names for the variables they contain. Instead, they store
  the subvariables sequentially, and you can access them with a
  numerical index.

FreeMarker Manual - Template + data-model = output

freemarker.org/...dgui_quickstart_basics.html - Preview

FreeMarker manual doc reference view java mvc

<html>
<head>
  <title>Welcome!</title>
</head>
<body>
  <h1>Welcome ${user}!</h1>
  <p>Our latest product:
  <a href="${latestProduct.url}">${latestProduct.name}</a>!
</body>
</html>

In the
template you only deal with presentation issues, that is, visual
design issues, formatting issues.

09 Dec 08

CVS Minimal Help

www.cs.wustl.edu/CVS.html - Preview

cvs manual doc reference athand

Adding one or more text files requires two steps:
    % cvs add file . . .
    % cvs commit file . . .

To create a branch, you must first create a tag to identify the
branch.
2 more annotations...
- The first, preferred approach is to use
  the cvs export command to stage a version of the
  controlled files to a non-controlled directory. This version will
  not have any of the CVS files in it.
- THe second approach is to
  create a release from a user's CVS-controlled workspace.

CVS—Concurrent Versions System v1.11.21: A. Guide to CVS commands

ximbiot.com/...cvs_16.html - Preview

cvs manual doc reference

The modules are either
symbolic names for some
collection of source directories and files, or paths to
directories or files in the repository. The symbolic
names are defined in the `modules' file.
The top-level directory created is always
added to the directory where checkout is
invoked, and usually has the same name as the specified
module.
2 more annotations...
- checkout takes a module name whereas
  update takes a directory name.
- -d dir
  
  Create a directory called dir for the working
  files, instead of using the module name. In general,
  using this flag is equivalent to using `mkdir dir; cd dir' followed by the checkout
  command without the `-d' flag.

08 Dec 08

CVS manual

ximbiot.com/...cvs_toc.html - Preview

cvs manual doc reference athand

22 Oct 08

Keyboard shortcuts

support.mozilla.com/...Keyboard+shortcuts - Preview

doc manual firefox tips keyboard

CtrlCmd+[
CtrlCmd+]
2 more annotations...
- Find As You Type Link'
- FindCtrlCmd+F
  Find AgainF3
  CtrlCmd+G
  Find As You Type Link'
  Find As You Type Text/

Kenyth Zeng's Library tagged manual → View Popular

Vim documentation: tabpage

RubyGems Manuals

Tor: 匿名在线

Bash Reference Manual

gitignore(5)

Git User's Manual (for version 1.5.3 or newer)

Screen - Copy and Paste

CVS Howto - Eclipsepedia

The Kernel Virtual Machine - Community Ubuntu Documentation

Apache Felix - Apache Felix Usage Documentation

UpgradeNotes - Community Ubuntu Documentation

Bugzilla Installation

FreeMarker Manual - FAQ

FreeMarker Manual - The template at a glance

FreeMarker Manual - The data-model at a glance

FreeMarker Manual - Template + data-model = output

CVS Minimal Help

CVS—Concurrent Versions System v1.11.21: A. Guide to CVS commands

CVS manual

Keyboard shortcuts

Selected Tags

Related Tags

Sponsored Links

Top Contributors

Groups interested in manual

Health Impact Assessment

MYOB courses

TEM_Cristianos y Graneros

Manuales y tutoriales