[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43961: read carefully: dired-file-name-at-point vs dired-filename-at
From: |
Boruch Baum |
Subject: |
bug#43961: read carefully: dired-file-name-at-point vs dired-filename-at-point |
Date: |
Tue, 13 Oct 2020 06:25:12 -0400 |
User-agent: |
NeoMutt/20180716 |
On 2020-10-13 06:54, Lars Ingebrigtsen wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
>
> > They return different values. One returns an expanded (canonical)
> > path-name, and the other an abbreviated one.
>
> Why not just have one call the other, and wrap the results in
> abbreviate-file-name?
You could, but you wouldn't be saving anything since the inner function
would still need to perform the expansion, so for the abbreviated
function you end up in effect with an inefficient (abbrev (expand file))
instead of a choice between (abbrev file) or (expand file).
Also, much of the change ends up being defaliases, docstrings and
deprecation notices, so its more clearly presented without nesting
functions.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0