From: Ryan Barrett <emacs@ryanb.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 9647@debbugs.gnu.org, lekktu@gmail.com
Subject: bug#9647: dirtrack.el patch to support prefixed paths, e.g. tramp remote shells
Date: Sun, 16 Oct 2011 09:47:12 -0700 [thread overview]
Message-ID: <CA+caGh9TkBS60Dow8P_6j2_x22kkgVYryi9Tnn_ag460itBAYw@mail.gmail.com> (raw)
In-Reply-To: <87k485l47r.fsf@gmx.de>
On Sun, Oct 16, 2011 at 1:40 AM, Michael Albinus <michael.albinus@gmx.de> wrote:
> However, I still don't know whether this shall be fixed in
> dirtrack.el. Maybe it would be better if Tramp could support.
yeah, i understand that instinct. i think dirtrack may be the more
appropriate place, though.
notably, if you look at the patch, it doesn't actually depend on tramp
at all. it uses shell-prefixed-directory-name and
comint-file-name-prefix, which are generic mechanisms in shell and
comint, which dirtrack already depends on.
> (set-variable 'dirtrack-list "[REGEX]")
...
> What do you use as "[REGEX]"? Shouldn't this be a list?
>
> Remote shells as implemented by Tramp do not provide any directory
> information in the prompt. By default, the prompt looks like this:
tramp does use the user's shell and dotfiles on the remote machine,
but still, good points, the instructions needed more details. i use
tcsh with this dirtrack-list:
(set-variable 'dirtrack-list '(":\\([^ :>]*\\)> *$" 1 nil))
try that, and then run tcsh on the remote machine and run this:
set prompt="%m:%~%# "
that gives you a prompt that looks like this:
purgatory:~/foo/bar>
next prev parent reply other threads:[~2011-10-16 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 21:09 bug#9647: dirtrack.el patch to support prefixed paths, e.g. tramp remote shells Ryan Barrett
2011-10-09 9:52 ` Michael Albinus
2011-10-10 2:17 ` Ryan Barrett
2011-10-16 8:40 ` Michael Albinus
2011-10-16 16:47 ` Ryan Barrett [this message]
2011-10-17 19:52 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+caGh9TkBS60Dow8P_6j2_x22kkgVYryi9Tnn_ag460itBAYw@mail.gmail.com \
--to=emacs@ryanb.org \
--cc=9647@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.