all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Allred <allred.sean@gmail.com>
Cc: 65120@debbugs.gnu.org
Subject: bug#65120: 29.1; directory-abbrev-alist breaks various things when inside an abbreviated directory
Date: Mon, 07 Aug 2023 18:45:55 +0300	[thread overview]
Message-ID: <83leemonyk.fsf@gnu.org> (raw)
In-Reply-To: <m08rann3kv.fsf@epic96565.epic.com> (message from Sean Allred on Sun, 06 Aug 2023 18:35:22 -0500)

> From: Sean Allred <allred.sean@gmail.com>
> Date: Sun, 06 Aug 2023 18:35:22 -0500
> 
> Emacs behaves oddly inside abbreviated directories when
> `directory-abbrev-alist' is set.
> 
>     $ emacs -Q
>     lisp> (setq directory-abbrev-alist `(("~/tmp" . "tmp")))
>     keys> C-x d ~/tmp RET
>     keys> C-x C-f
> 
> I see "tmp/" in the minibuffer and no completions are available.
> 
> I've also seen (dired "~/tmp") fail on Windows in this scenario --
> complaining that the directory is inaccessible. On both systems, ~/tmp
> does exist (and has content) and behaves as expected if
> `directory-abbrev-alist' is nil.

This is not how directory-abbrev-alist should be used, according to
documentation.  The cdr of each alist element ("tmp" in your case) is
supposed to be an absolute file name, and "tmp" isn't.  Also, the car
of each element is supposed to be an anchored regexp.

What did you want to accomplish with directory-abbrev-alist such as
the above, and why did you want that?





  reply	other threads:[~2023-08-07 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 23:35 bug#65120: 29.1; directory-abbrev-alist breaks various things when inside an abbreviated directory Sean Allred
2023-08-07 15:45 ` Eli Zaretskii [this message]
2023-08-09 11:28   ` Sean Allred
2023-08-09 13:21     ` Eli Zaretskii
2023-08-09 23:31       ` Sean Allred
2023-08-10  6:22         ` Eli Zaretskii

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=83leemonyk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65120@debbugs.gnu.org \
    --cc=allred.sean@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.