unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Walker Lynch via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 47048@debbugs.gnu.org
Subject: bug#47048: dirtrack debug mode log
Date: Wed, 10 Mar 2021 16:04:18 +0100	[thread overview]
Message-ID: <CAGxFmCMt0GwWy9cbs6z2tghBGvQKHO+q-59Sx7nrGW02Eb8tkw@mail.gmail.com> (raw)
In-Reply-To: <CAGxFmCPdDCBYoSd2YjOnjeYo1cbGO67JRaiHi19xcL0V3fe4Fg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1360 bytes --]

This code ran for years before it stopped working recently, and it doesn't
look like the dirtrack.el code has changed either, but I could be wrong
about that, the comment says the variable has not changed since 24.1.
Unfortunately,  Fedora 33 will not allow me to use dnf to go to an older
release for emacs.  It  says that the one used now is the only package for
emacs for F33.

I see in the dirtrack.el comments that a third prompt of t should be added
for a multi line prompt.  I have added that.  It made no difference.  There
are some good examples in the comments.  The prompt used for this bug
report is much like their solaris example.

The dirtrack.el mentions regular expression groups as the second argument.
It is set to 1.  I do not know what that is referring to.  In any case, it
does not look like the dirtrack-list is the problem.

Rather it looks like the problem is that the input to (defun dirtrack
(input)) is being limited to 48 chars.  It is not difficult to find paths
on this system that exceed 44 chars in length (plus the prompt sugar).
 Where is this limitation imposed?  Is there a variable for it somewhere?
It is disappointing that the regular expression match has a maximum length
to trip on at all.




On Wed, Mar 10, 2021 at 3:17 PM Thomas Walker Lynch <
thomas.lynch@reasoningtechnology.com> wrote:

> [image: image.png]
>

[-- Attachment #1.2: Type: text/html, Size: 1989 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 80978 bytes --]

  reply	other threads:[~2021-03-10 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 13:48 bug#47048: dirtrack no longer parses long paths from prompt Thomas Walker Lynch via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-10 14:17 ` bug#47048: dirtrack debug mode log Thomas Walker Lynch via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-10 15:04   ` Thomas Walker Lynch via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-10 15:27     ` Thomas Walker Lynch via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGxFmCMt0GwWy9cbs6z2tghBGvQKHO+q-59Sx7nrGW02Eb8tkw@mail.gmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47048@debbugs.gnu.org \
    --cc=thomas.lynch@reasoningtechnology.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).