Mercurial > hgbook

changeset 357:ef197f25f11e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
more hgext.tex
author Yoshiki Yazawa <yaz@honeyplanet.jp>
date Tue, 02 Sep 2008 17:27:11 +0900
parents b96d7f6504e5
children 1348ce7d2d77
files ja/hgext.tex ja/todo.txt
diffstat 2 files changed, 135 insertions(+), 64 deletions(-) [+]
line wrap: on
line diff
--- a/ja/hgext.tex	Mon Sep 01 18:20:56 2008 +0900
+++ b/ja/hgext.tex	Tue Sep 02 17:27:11 2008 +0900
@@ -186,103 +186,174 @@
 $B%H%o!<%/%U%!%$%k%7%9%F%`$O9MN8$5$l$F$$$J$$!%(B
 \end{itemize}
 
-The \hgext{inotify} extension is not yet shipped with Mercurial as of
-May~2007, so it's a little more involved to set up than other
-extensions.  But the performance improvement is worth it!
+%The \hgext{inotify} extension is not yet shipped with Mercurial as of
+%May~2007, so it's a little more involved to set up than other
+%extensions.  But the performance improvement is worth it!
+
+2007$BG/(B5$B7n$^$G$O(B\hgext{inotify}$B3HD%$O(BMercurial$B$KF1:-$5$l$F$$$J$+$C$?!%$=$N(B
+$B$?$a!$%;%C%H%"%C%W$OB>$N3HD%$KHf$Y$F$d$dJ#;($@$,!$F@$i$l$k@-G=8~>e$O$K$O(B
+$B$=$l$@$1$N2ACM$,$"$k!%(B
 
-The extension currently comes in two parts: a set of patches to the
-Mercurial source code, and a library of Python bindings to the
-\texttt{inotify} subsystem.
+%The extension currently comes in two parts: a set of patches to the
+%Mercurial source code, and a library of Python bindings to the
+%\texttt{inotify} subsystem.
+
+$B8=:_!$3HD%$O(B2$B$D$N%Q!<%H$KJ,$+$l$F$$$k!%(BMercurial$B%=!<%9%3!<%I$X$N%Q%C%A$H(B
+\texttt{inotify}$B%5%V%7%9%F%`$X$N(BPython$B%P%$%s%G%#%s%0%i%$%V%i%j$G$"$k!%(B
+
 \begin{note}
-  There are \emph{two} Python \texttt{inotify} binding libraries.  One
-  of them is called \texttt{pyinotify}, and is packaged by some Linux
-  distributions as \texttt{python-inotify}.  This is \emph{not} the
-  one you'll need, as it is too buggy and inefficient to be practical.
+%  There are \emph{two} Python \texttt{inotify} binding libraries.  One
+%  of them is called \texttt{pyinotify}, and is packaged by some Linux
+%  distributions as \texttt{python-inotify}.  This is \emph{not} the
+%  one you'll need, as it is too buggy and inefficient to be practical.
+
+Python$B$N(B\texttt{inotify}$B%P%$%s%G%#%s%0%i%$%V%i%j$O(B\emph{2$B$D(B}$B$"$k!%(B1$B$D$O(B
+\texttt{pyinotify}$B$G$"$j!$$$$/$D$+$N(BLinux$B%G%#%9%H%j%S%e!<%7%g%s$G$O(B
+\texttt{python-inotify}$B$H$7$F%Q%C%1!<%82=$5$l$F$$$k!%$3$l$O%P%0$,Hs>o$KB?(B
+$B$/!$<BMQ$9$k$K$OHs8zN(E*$G$"$j!$;H$&$Y$-$G(B\emph{$B$J$$(B}$B!%(B
 \end{note}
-To get going, it's best to already have a functioning copy of
-Mercurial installed.
+%To get going, it's best to already have a functioning copy of
+%Mercurial installed.
+$B@h$X?J$`$KEv$C$F!$@5$7$/5!G=$9$k(BMercurial$B$,%$%s%9%H!<%k$5$l$F$$$k$3$H$,(B
+$BK>$^$7$$!%(B
+
 \begin{note}
-  If you follow the instructions below, you'll be \emph{replacing} and
-  overwriting any existing installation of Mercurial that you might
-  already have, using the latest ``bleeding edge'' Mercurial code.
-  Don't say you weren't warned!
+%  If you follow the instructions below, you'll be \emph{replacing} and
+%  overwriting any existing installation of Mercurial that you might
+%  already have, using the latest ``bleeding edge'' Mercurial code.
+%  Don't say you weren't warned!
+$B0J2<$N;X<($K=>$C$F%$%s%9%H!<%k$7$?(BMercurial$B$r!$:G?7$N(BMercurial$B%3!<%I$G(B
+\emph{$BCV$-49$($k(B}$B$3$H$,$G$-$k!%!J7Y9p$5$l$J$+$C$?$H$O8@$o$J$$$3$H!K(B
+
 \end{note}
 \begin{enumerate}
-\item Clone the Python \texttt{inotify} binding repository.  Build and
-  install it.
+%\item Clone the Python \texttt{inotify} binding repository.  Build and
+%  install it.
+\item Python \texttt{inotify}$B%P%$%s%G%#%s%0$N%j%]%8%H%j$r%/%m!<%s$7!$%S(B
+      $B%k%I$H%$%s%9%H!<%k$r9T$&!%(B
   \begin{codesample4}
     hg clone http://hg.kublai.com/python/inotify
     cd inotify
     python setup.py build --force
     sudo python setup.py install --skip-build
   \end{codesample4}
-\item Clone the \dirname{crew} Mercurial repository.  Clone the
-  \hgext{inotify} patch repository so that Mercurial Queues will be
-  able to apply patches to your cope of the \dirname{crew} repository.
+%\item Clone the \dirname{crew} Mercurial repository.  Clone the
+%  \hgext{inotify} patch repository so that Mercurial Queues will be
+%  able to apply patches to your cope of the \dirname{crew} repository.
+ \item Merecurial$B$N(B\dirname{crew}$B%j%]%8%H%j$r%/%m!<%s$9(B
+      $B$k!%(B\hgext{inotify}$B%Q%C%A%j%]%8%H%j$r%/%m!<%s$7!$(BMercurial Queues
+      $B$,(B\dirname{crew}$B%j%]%8%H%j$K%Q%C%A$rEv$F$i$l$k$h$&$K$9$k!%(B
   \begin{codesample4}
     hg clone http://hg.intevation.org/mercurial/crew
     hg clone crew inotify
     hg clone http://hg.kublai.com/mercurial/patches/inotify inotify/.hg/patches
   \end{codesample4}
-\item Make sure that you have the Mercurial Queues extension,
-  \hgext{mq}, enabled.  If you've never used MQ, read
-  section~\ref{sec:mq:start} to get started quickly.
-\item Go into the \dirname{inotify} repo, and apply all of the
-  \hgext{inotify} patches using the \hgxopt{mq}{qpush}{-a} option to
-  the \hgxcmd{mq}{qpush} command.
+%\item Make sure that you have the Mercurial Queues extension,
+%  \hgext{mq}, enabled.  If you've never used MQ, read
+%  section~\ref{sec:mq:start} to get started quickly.
+
+\item Mercurial Queues$B3HD%!J(B\hgext{mq}$B!K$,M-8z$K$J$C$F$$$k$3$H$r3NG'$9(B
+      $B$k!%(BMQ$B$r;H$C$?$3$H$,$J$1$l$P!$(B\ref{sec:mq:start}$B$r0lFI$9$k$3$H$r$*(B
+      $B$9$9$a$9$k!%(B
+
+%\item Go into the \dirname{inotify} repo, and apply all of the
+%  \hgext{inotify} patches using the \hgxopt{mq}{qpush}{-a} option to
+%  the \hgxcmd{mq}{qpush} command.
+\item \dirname{inotify}$B%j%]%8%H%j$X9T$-!$(B\hgxcmd{mq}{qpush}$B%3%^%s%I$K(B
+      \hgxopt{mq}{qpush}{-a}$B%*%W%7%g%s$r;H$C$F(B\hgext{inotify}$B$N%Q%C%A$r$9(B
+      $B$Y$FE,MQ$9$k!%(B
+
   \begin{codesample4}
     cd inotify
     hg qpush -a
   \end{codesample4}
-  If you get an error message from \hgxcmd{mq}{qpush}, you should not
-  continue.  Instead, ask for help.
-\item Build and install the patched version of Mercurial.
+%  If you get an error message from \hgxcmd{mq}{qpush}, you should not
+%  continue.  Instead, ask for help.
+
+\hgxcmd{mq}{qpush}$B$G%(%i!<$,5/$-$?>l9g!$@h$X?J$^$:$K=u8@$r5a$a$FM_$7$$!%(B
+
+%\item Build and install the patched version of Mercurial.
+\item $B%Q%C%A$rEv$F$?(BMercurial$B$r%S%k%I$7$F%$%s%9%H!<%k$9$k!%(B
   \begin{codesample4}
     python setup.py build --force
     sudo python setup.py install --skip-build
   \end{codesample4}
 \end{enumerate}
-Once you've build a suitably patched version of Mercurial, all you
-need to do to enable the \hgext{inotify} extension is add an entry to
-your \hgrc.
+%Once you've build a suitably patched version of Mercurial, all you
+%need to do to enable the \hgext{inotify} extension is add an entry to
+%your \hgrc.
+
+$BE,@Z$J%Q%C%A$NEv$C$?(BMercurial$B$r%S%k%I$9$l$P!$8e$O(B\hgext{inotify}$B3HD%$rMx(B
+$BMQ$9$k$h$&$K(B\hgrc $B$r@_Dj$9$k$@$1$G$"$k!%(B
+
 \begin{codesample2}
   [extensions]
   inotify =
 \end{codesample2}
-When the \hgext{inotify} extension is enabled, Mercurial will
-automatically and transparently start the status daemon the first time
-you run a command that needs status in a repository.  It runs one
-status daemon per repository.
+%When the \hgext{inotify} extension is enabled, Mercurial will
+%automatically and transparently start the status daemon the first time
+%you run a command that needs status in a repository.  It runs one
+%status daemon per repository.
+
+\hgext{inotify}$B$,M-8z$K$J$C$F$$$k$H!$(BMercurial$B$O%j%]%8%H%jFb$G%3%^%s%I$,(B
+$B:G=i$K<B9T$5$l$?;~$K<+F0E*$+$DF)2aE*$K%9%F!<%?%9%G!<%b%s$r5/F0$9$k!%%j%](B
+$B%8%H%j(B1$B$D$4$H$K(B1$B$D$N%9%F!<%?%9%G!<%b%s$,5/F0$5$l$k!%(B
 
-The status daemon is started silently, and runs in the background.  If
-you look at a list of running processes after you've enabled the
-\hgext{inotify} extension and run a few commands in different
-repositories, you'll thus see a few \texttt{hg} processes sitting
-around, waiting for updates from the kernel and queries from
-Mercurial.
+%The status daemon is started silently, and runs in the background.  If
+%you look at a list of running processes after you've enabled the
+%\hgext{inotify} extension and run a few commands in different
+%repositories, you'll thus see a few \texttt{hg} processes sitting
+%around, waiting for updates from the kernel and queries from
+%Mercurial.
+
+$B%9%F!<%?%9%G!<%b%s$O2?$b=PNO$r9T$o$:!$%P%C%/%0%i%&%s%I$GF0:n$9(B
+$B$k!%(B\hgext{inotify}$B3HD%$rM-8z$K$7$?8e$GJL$N%j%]%8%H%jFb$G$$$/$D$+%3%^%s%I(B
+$B$r<B9T$7!$<B9TCf$N%W%m%;%9$N%j%9%H$r8+$k$H!$$$$/$D$+$N(B\texttt{hg}$B%W%m%;%9(B
+$B$,%+!<%M%k$+$i$N%"%C%W%G!<%H$H(BMercurial$B$+$i$NLd$$9g$o$;$rBT$C$F$$$k$N$,(B
+$B8+$i$l$k$@$m$&!%(B
 
-The first time you run a Mercurial command in a repository when you
-have the \hgext{inotify} extension enabled, it will run with about the
-same performance as a normal Mercurial command.  This is because the
-status daemon needs to perform a normal status scan so that it has a
-baseline against which to apply later updates from the kernel.
-However, \emph{every} subsequent command that does any kind of status
-check should be noticeably faster on repositories of even fairly
-modest size.  Better yet, the bigger your repository is, the greater a
-performance advantage you'll see.  The \hgext{inotify} daemon makes
-status operations almost instantaneous on repositories of all sizes!
+%The first time you run a Mercurial command in a repository when you
+%have the \hgext{inotify} extension enabled, it will run with about the
+%same performance as a normal Mercurial command.  This is because the
+%status daemon needs to perform a normal status scan so that it has a
+%baseline against which to apply later updates from the kernel.
+%However, \emph{every} subsequent command that does any kind of status
+%check should be noticeably faster on repositories of even fairly
+%modest size.  Better yet, the bigger your repository is, the greater a
+%performance advantage you'll see.  The \hgext{inotify} daemon makes
+%status operations almost instantaneous on repositories of all sizes!
+
+\hgext{inotify}$B3HD%$rM-8z$K$7!$%j%]%8%H%jFb$G(BMercurial$B%3%^%s%I$r:G=i$K<B(B
+$B9T$7$?;~$ODL>o$N(BMercurial$B%3%^%s%I$HF1MM$N@-G=$GF0$/!%%9%F!<%?%9%G!<%b%s$O(B
+$BDL>o$N%9%F!<%?%9%9%-%c%s$r9T$$!$%+!<%M%k$+$i99?7$NDLCN$r<u$1$k$?$a$N%Y!<(B
+$B%9%i%$%s$r<hF@$7$F$*$+$J$1$l$P$J$i$J$$$+$i$G$"$k!%0lJ}$G!$8eB3$N%9%F!<%?(B
+$B%9%A%'%C%/$r9T$&(B\emph{$B$9$Y$F$N(B}$B%3%^%s%I$O!$$=$3$=$3$NBg$-$5$N%j%]%8%H%j$K(B
+$BBP$7$F$bL\$K8+$($F9bB.2=$5$l$k!%$5$i$K%j%]%8%H%j$,Bg$-$/$J$k$KO"$l$F@-G=(B
+$B$N8~>e$OBg$-$/$J$k!%(B\hgext{inotify}$B%G!<%b%s$O!$%j%]%8%H%j$N%5%$%:$K4X$o$i(B
+$B$:!$%9%F!<%?%9<hF@$r$[$\=V;~$K9T$&$3$H$,$G$-$k!%(B
 
-If you like, you can manually start a status daemon using the
-\hgxcmd{inotify}{inserve} command.  This gives you slightly finer
-control over how the daemon ought to run.  This command will of course
-only be available when the \hgext{inotify} extension is enabled.
+%If you like, you can manually start a status daemon using the
+%\hgxcmd{inotify}{inserve} command.  This gives you slightly finer
+%control over how the daemon ought to run.  This command will of course
+%only be available when the \hgext{inotify} extension is enabled.
+
+\hgxcmd{inotify}{inserve}$B%3%^%s%I$r;H$C$F%9%F!<%?%9%G!<%b%s$r<jF0$G<B9T$9(B
+$B$k$3$H$b2DG=$G$"$k!%$3$l$K$h$j!$%G!<%b%s$,$I$N$h$&$KF0:n$9$k$N$+$r$d$d:Y(B
+$B$+$/%3%s%H%m!<%k$9$k$3$H$,$G$-$k!%EvA3$J$,$i!$$3$N%3%^%s%I$O(B
+\hgext{inotify}$B$,M-8z$N>l9g$N$_MxMQ2DG=$G$"$k!%(B
+
 
-When you're using the \hgext{inotify} extension, you should notice
-\emph{no difference at all} in Mercurial's behaviour, with the sole
-exception of status-related commands running a whole lot faster than
-they used to.  You should specifically expect that commands will not
-print different output; neither should they give different results.
-If either of these situations occurs, please report a bug.
+%When you're using the \hgext{inotify} extension, you should notice
+%\emph{no difference at all} in Mercurial's behaviour, with the sole
+%exception of status-related commands running a whole lot faster than
+%they used to.  You should specifically expect that commands will not
+%print different output; neither should they give different results.
+%If either of these situations occurs, please report a bug.
+
+\hgext{inotify}$B3HD%$r;H$C$F$$$k;~$O(BMercurial$B$N(B\emph{$BA4$/JQ2=$J$7(B}$B$H$$$&F0(B
+$B:n$K5$IU$/$@$m$&!%%9%F!<%?%9$K4X78$9$k%3%^%s%I$O0JA0$h$j$:$C$H9bB.$K$J$C(B
+$B$F$$$k$H$$$&0l$D$NNc30$r=|$$$F%3%^%s%I$OFCJL$N=PNO$b7k2L$b=PNO$7$J$$$3$H(B
+$B$KN10U$5$l$?$$!%2?$+FCJL$J$3$H$,5/$-$?$i%P%0$H$7$FJs9p$7$FM_$7$$!%(B
 
 %\section{Flexible diff support with the \hgext{extdiff} extension}
 \section{\hgext{extdiff}$B3HD%$K$h$k=@Fp$J(Bdiff$B%5%]!<%H(B}
--- a/ja/todo.txt	Mon Sep 01 18:20:56 2008 +0900
+++ b/ja/todo.txt	Tue Sep 02 17:27:11 2008 +0900
@@ -5,7 +5,7 @@
 daily.tex
 filenames.tex
 hg_id.tex	noneed
-hgext.tex
+hgext.tex	50%
 hook.tex
 intro.tex
 license.tex