; * lisp/dirtrack.el: Improve commentary.

This commit is contained in:
Stefan Kangas 2022-07-12 18:42:52 +02:00
parent c518b06ae6
commit 5f0ef3c9d8

View file

@ -30,9 +30,8 @@
;; that you can customize your shell's prompt to contain the
;; current working directory. Most shells do support this, including
;; almost every type of Bourne and C shell on Unix, the native shells on
;; Windows95 (COMMAND.COM) and Windows NT (CMD.EXE), and most 3rd party
;; Windows shells. If you cannot do this, or do not wish to, this package
;; will be useless to you.
;; Windows, and most 3rd party Windows shells. If you cannot do this, or
;; do not wish to, this package will be useless to you.
;;
;; Installation:
;;
@ -92,7 +91,7 @@
;; A final note:
;;
;; I run LOTS of shell buffers through Emacs, sometimes as different users
;; (eg, when logged in as myself, I'll run a root shell in the same Emacs).
;; (e.g., when logged in as myself, I'll run a root shell in the same Emacs).
;; If you do this, and the shell prompt contains a ~, Emacs will interpret
;; this relative to the user which owns the Emacs process, not the user
;; who owns the shell buffer. This may cause dirtrack to behave strangely
@ -100,9 +99,9 @@
;; with a ~ in it).
;;
;; The same behavior can occur if you use dirtrack with remote filesystems
;; (using telnet, rlogin, etc) as Emacs will be checking the local
;; filesystem, not the remote one. This problem is not specific to dirtrack,
;; but also affects file completion, etc.
;; (using telnet, etc.) as Emacs will be checking the local filesystem, not
;; the remote one. This problem is not specific to dirtrack, but also
;; affects file completion, etc.
;;; Code: