From: Eli Zaretskii <eliz@gnu.org>
To: Colton Goates <coltongoates@gmail.com>
Cc: 74524@debbugs.gnu.org
Subject: bug#74524: 29.4; dirtrack-mode
Date: Mon, 25 Nov 2024 20:55:03 +0200 [thread overview]
Message-ID: <867c8ri1o8.fsf@gnu.org> (raw)
In-Reply-To: <CAJkz86vppc+XYrcB_3wzX1LNXQkd6OweQWmE7aQ+GL+0DodYPA@mail.gmail.com> (message from Colton Goates on Mon, 25 Nov 2024 10:27:00 -0700)
> From: Colton Goates <coltongoates@gmail.com>
> Date: Mon, 25 Nov 2024 10:27:00 -0700
> Cc: 74524@debbugs.gnu.org
>
> Coltons-MacBook-Pro:/Users/coltongoates/software-dev/$ isn't intended to be a directory name, it's a string
> that's intended to look exactly like my prompt. (I know it's pretty contrived.)
>
> So, if someone prints something that resembles their prompt, dirtrack will change the directory, because
> dirtrack thinks it just saw the shell prompt appear, but it really just saw a string that resembles the prompt.
> Does that make more sense now?
What do you expect dirtrack to do when you deliberately try to deceive
it? AFAIU, dirtrack is a piece of heuristic ad-hocery (as explained
in its commentary), so it cannot be expected to survive such
deception. What kind of changes would you suggest to consider to
handle the cases such as this one?
next prev parent reply other threads:[~2024-11-25 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 3:55 bug#74524: 29.4; dirtrack-mode Colton Goates
2024-11-25 12:38 ` Eli Zaretskii
2024-11-25 17:27 ` Colton Goates
2024-11-25 18:55 ` Eli Zaretskii [this message]
2024-11-25 19:08 ` Ship Mints
2024-11-26 2:32 ` Colton Goates
2024-11-26 2:11 ` Colton Goates
2024-11-26 14:00 ` Ship Mints
2024-11-26 18:11 ` Colton Goates
2024-11-26 14:32 ` Eli Zaretskii
2024-11-26 14:46 ` Ship Mints
2024-11-26 18:05 ` Colton Goates
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=867c8ri1o8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74524@debbugs.gnu.org \
--cc=coltongoates@gmail.com \
/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.