[Emacs-diffs] Changes to emacs/man/tramp.texi

[Kai Großjohann]

Index: emacs/man/tramp.texi
diff -c emacs/man/tramp.texi:1.4 emacs/man/tramp.texi:1.5
*** emacs/man/tramp.texi:1.4    Tue Jun 25 16:11:34 2002
--- emacs/man/tramp.texi        Sat Jul 13 06:52:22 2002
***************
*** 8,19 ****
  @c This is *so* much nicer :)
  @footnotestyle end
  
- @c Version values, for easy modification
- @c NOTE: The 'UPDATED' value is updated by the 'time-stamp' function.
- @c       If you change it by hand, the modifications will not stay.
- @set VERSION $Revision: 1.4 $
- @set UPDATED Monday, 17 June, 2002
- 
  
  @c Entries for @command{install-info} to use
  @direntry
--- 8,13 ----
***************
*** 61,67 ****
  
  @titlepage
  @title @tramp{} User Manual
- @subtitle Last updated @value{UPDATED}
  
  @author by Daniel Pittman
  @author based on documentation by Kai address@hidden
--- 55,60 ----
***************
*** 102,110 ****
  @command{rsh} and @command{rcp} or other work-alike programs, such as
  @command{ssh}/@command{scp}.
  
- This is version @value{VERSION} of the @tramp{} manual, last updated on
- @value{UPDATED}.
- 
  You can find the latest version of this document on the web at
  @uref{http://www.freesoftware.fsf.org/tramp/}.
  
--- 95,100 ----
***************
*** 726,731 ****
--- 716,728 ----
  logging in.  This procedure avoids these questions, and just gives
  @tramp{} a more-or-less `standard' login shell to work with.
  
+ Note that this procedure does not eliminate questions asked by
+ @command{ssh} itself.  For example, @command{ssh} might ask ``Are you
+ sure you want to continue connecting?'' if the host key of the remote
+ host is not known.  Tramp does not know how to deal with such a
+ question (yet), therefore you will need to make sure that you can log
+ in without such questions.
+ 
  This is also useful for Windows users where @command{ssh}, when
  invoked from an Emacs buffer, tells them that it is not allocating a
  pseudo tty.  When this happens, the login shell is wont to not print
***************
*** 1091,1096 ****
--- 1088,1100 ----
  recognize the shell prompt, the variable @code{shell-prompt-pattern} has
  to be set correctly to recognize the shell prompt on the remote host.
  
+ Note that Tramp requires the match for @code{shell-prompt-pattern} to
+ be at the end of the buffer.  Many people have something like the
+ following as the value for the variable: @code{"^[^>$][>$] *"}.  Now
+ suppose your shell prompt is @code{a <b> c $ }.  In this case, Tramp
+ recognizes the @code{>} character as the end of the prompt, but it is
+ not at the end of the buffer.
+ 
  @item @code{tset} and other questions
  
  Some people invoke the @code{tset} program from their shell startup
***************
*** 1640,1650 ****
  @c   shells.
  @c * Explain how tramp.el works in principle: open a shell on a remote
  @c   host and then send commands to it.
  
- @c Local Variables:
- @c eval: (add-hook 'write-file-functions 'time-stamp)
- @c time-stamp-start: "@set UPDATED "
- @c time-stamp-format: "%:a, %:d %:b, %:y"
- @c time-stamp-end: "$"
- @c time-stamp-line-limit: 50
- @c End:
--- 1644,1650 ----
  @c   shells.
  @c * Explain how tramp.el works in principle: open a shell on a remote
  @c   host and then send commands to it.
+ @c * Mention that bookmarks are a cool feature to go along with Tramp.
+ @c * Make terminology "inline" vs "out-of-band" consistent.
+ @c   It seems that "external" is also used instead of "out-of-band".