Menu
▾
▴
tramp-checkins
|
From: Kai Gro?j. <ka...@us...> - 2002-04-22 18:54:57
|
Update of /cvsroot/tramp/tramp/texi
In directory usw-pr-cvs1:/tmp/cvs-serv28525/tramp/texi
Modified Files:
ChangeLog tramp.texi
Log Message:
2002-04-22 Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
* tramp.texi (Top, Connection types, Dired, Back-end Versions,
Path deconstruction): It's "its", not "it's". Thanks to Ted
Stern for catching this.
2002-04-19 Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
From Harry Putnam <re...@ne...>. Awaiting copyright
assignment.
* tramp.texi (Installation): Give more details on byte-compiling
the Lisp files and creating and installing the info file.
Index: ChangeLog
===================================================================
RCS file: /cvsroot/tramp/tramp/texi/ChangeLog,v
retrieving revision 2.15
retrieving revision 2.16
diff -C2 -d -r2.15 -r2.16
*** ChangeLog 14 Apr 2002 15:52:39 -0000 2.15
--- ChangeLog 22 Apr 2002 18:54:54 -0000 2.16
***************
*** 1,2 ****
--- 1,15 ----
+ 2002-04-22 Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
+
+ * tramp.texi (Top, Connection types, Dired, Back-end Versions,
+ Path deconstruction): It's "its", not "it's". Thanks to Ted
+ Stern for catching this.
+
+ 2002-04-19 Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
+ From Harry Putnam <re...@ne...>. Awaiting copyright
+ assignment.
+
+ * tramp.texi (Installation): Give more details on byte-compiling
+ the Lisp files and creating and installing the info file.
+
2002-04-14 Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
Index: tramp.texi
===================================================================
RCS file: /cvsroot/tramp/tramp/texi/tramp.texi,v
retrieving revision 2.13
retrieving revision 2.14
diff -C2 -d -r2.13 -r2.14
*** tramp.texi 14 Apr 2002 15:52:39 -0000 2.13
--- tramp.texi 22 Apr 2002 18:54:54 -0000 2.14
***************
*** 13,17 ****
@c If you change it by hand, the modifications will not stay.
@set VERSION $Revision$
! @set UPDATED Sunday, 14 April, 2002
--- 13,17 ----
@c If you change it by hand, the modifications will not stay.
@set VERSION $Revision$
! @set UPDATED Monday, 22 April, 2002
***************
*** 188,192 ****
How file names, directories and paths are mangled and managed.
! * Path deconstruction:: Breaking a path into it's components.
@end detailmenu
--- 188,192 ----
How file names, directories and paths are mangled and managed.
! * Path deconstruction:: Breaking a path into its components.
@end detailmenu
***************
*** 440,444 ****
Optionally byte-compile all files in the Lisp directory,
@file{~/emacs/tramp/lisp/}, by issuing a command like the following from
! that directory:
@example
make EMACS=emacs all # for Emacs users
--- 440,444 ----
Optionally byte-compile all files in the Lisp directory,
@file{~/emacs/tramp/lisp/}, by issuing a command like the following from
! the top level directory @file{~/emacs/tramp/}:
@example
make EMACS=emacs all # for Emacs users
***************
*** 447,452 ****
@item
! Tell Emacs about the new Lisp directory and the @tramp{} package, with
! the following lines in @file{~/.emacs}:
@lisp
(add-to-list 'load-path "~/emacs/tramp/lisp/")
--- 447,468 ----
@item
! NOTE:
! @example
! If you run into problems running the example @command{make}
! commands, don't dispare. You can still byte compile the
! @file{*.el} files by opening emacs in @command{dired}
! (@command{C-x d}) mode, at @file{~/tramp/lisp}. Mark the lisp
! files with @command{m}, then press @command{B} to byte compile
! your selections.
!
! Something similar can be done to create the info manual.
! Just cd to @file{~/emacs/tramp/texi} and load the @file{tramp.texi}
! file in emacs. Then press @command{M-x makeinfo-buffer <RET>}
! to generate @file{tramp.info}.
! @end example
!
! @item
! Tell Emacs about the new Lisp directory and the @tramp{} package
! with the following lines in @file{~/.emacs}:
@lisp
(add-to-list 'load-path "~/emacs/tramp/lisp/")
***************
*** 457,466 ****
To be able to read the Info documentation, create a file
@file{~/emacs/tramp/texi/dir} using for example the
! @command{install-info} command, and add the directory to the search path
! for Info.
! CCC Todo: explain how to use the @command{install-info} command. This
! works differently in Debian than on other systems. How does one create
! a @file{dir} file using @command{install-info} on Debian?
If the environment variable @env{INFOPATH} is set, add the directory
--- 473,506 ----
To be able to read the Info documentation, create a file
@file{~/emacs/tramp/texi/dir} using for example the
! @command{install-info} command, and add the directory to the search
! path for Info.
! @item
! NOTE:
! @example
! On systems using `gnu' @command{install-info}, the
! @command{install-info} syntax is very direct and simple. One can
! cd to @file{~/emacs/tramp/texi} and type:
! @command{install-info tramp.info dir}
! and a @file{dir} file will be created with the @tramp{}
! entry. The info reader will know how to interpret it, but must
! be told where to find it (see below). If you want anything fancier
! you'll need to look through @command{man install-info}.
!
! Debian gnu/linux doesn't default to `gnu' @command{install-info} and
! uses its own version. This version does not create a @file{dir} file
! for you from scratch. You must provide a skeleton dir file it
! recognizes. One can be found in a default install at
! @file{/usr/info/dir}. Copy the top of this file down to the first
! occurrence of `* Menu' including that line plus one more blank line,
! to your working directory @file{texi/dir}, or use the sample provided
! in the @file{texi} directroy of this distribution. See
! @file{texi/dir_sample}
!
! Once a @file{dir} file is in place, this command will make the entry.
! install-info --infodir=. tramp.info
! If you want it in a specific category
! (see @command{man install-info} for further details)
! @end example
If the environment variable @env{INFOPATH} is set, add the directory
***************
*** 484,489 ****
@end ifhtml
-
-
@node Configuration, Usage, Installation, Top
@chapter Configuring @tramp{} for use
--- 524,527 ----
***************
*** 518,522 ****
@section Types of connections made to remote machines.
! There are two basic types of transfer methods, each with it's own
advantages and limitations. Both types of connection make use of a
remote shell access program such as @command{rsh}, @command{ssh} or
--- 556,560 ----
@section Types of connections made to remote machines.
! There are two basic types of transfer methods, each with its own
advantages and limitations. Both types of connection make use of a
remote shell access program such as @command{rsh}, @command{ssh} or
***************
*** 1177,1181 ****
If you need to browse a directory tree, Dired is a better choice, at
! present, than filename completion. Dired has it's own cache mechanism
and will only fetch the directory listing once.
--- 1215,1219 ----
If you need to browse a directory tree, Dired is a better choice, at
! present, than filename completion. Dired has its own cache mechanism
and will only fetch the directory listing once.
***************
*** 1471,1475 ****
The default implementation of VC determines this value the first time it
is needed and then stores the value globally to avoid the overhead of
! executing a process and parsing it's output each time the information is
needed.
--- 1509,1513 ----
The default implementation of VC determines this value the first time it
is needed and then stores the value globally to avoid the overhead of
! executing a process and parsing its output each time the information is
needed.
***************
*** 1497,1506 ****
@menu
! * Path deconstruction:: Breaking a path into it's components.
@end menu
@node Path deconstruction, , Files directories and paths, Files directories and paths
! @section Breaking a path into it's components.
@tramp{} filenames are somewhat different, obviously, to ordinary path
--- 1535,1544 ----
@menu
! * Path deconstruction:: Breaking a path into its components.
@end menu
@node Path deconstruction, , Files directories and paths, Files directories and paths
! @section Breaking a path into its components.
@tramp{} filenames are somewhat different, obviously, to ordinary path
|
Thanks for helping keep SourceForge clean.
X