unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Arthur Miller <arthur.miller@live.com>
Cc: 43961@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
	Richard Stallman <rms@gnu.org>
Subject: bug#43961: read carefully: dired-file-name-at-point vs dired-filename-at-point
Date: Tue, 13 Oct 2020 07:27:46 -0400	[thread overview]
Message-ID: <20201013112746.o5rc3rloylt33tbe@E15-2016.optimum.net> (raw)
In-Reply-To: <VI1PR06MB4526D1E530C2B707E34131C496040@VI1PR06MB4526.eurprd06.prod.outlook.com>

On 2020-10-13 12:58, Arthur Miller wrote:
> ...
> + file-name-directory and directory-file-name,

Another excellent example that I always find confusing, even after much
dired programming.

> dired-filename-at-point is supposed to return a filename closest to the
> point, according to docs. For me it didn't work at all.

I seems to not have been as well-maintained as its sister function,
possibly because they've been in separate files and the maintainer
forgot about one. One of its bugs is that it truncates file names at the
first embedded space.

> But I mostly disliked the name. Why are there two almost identical name
> for different functionality?

So annoying, and not limited to dired. I recently posted another in bug
report 43294 [1]. It's been languishing for ~6 weeks without a decision
for action, so your vote might be helpful there.

> I have seen also discussion about string-replace and replace-string, can
> we plase not? For the reason above. And for the new APIs added, please
> don't use naming patterns like word1-word2 and word2-word1 or similar
> where same words are used just with some slight variation.

+1

Also, match-string and string-match. IMO, match-string should be aliased
and to something like 'match-result' and deprecate the original name
with a long-horizon EOL to account for its ubiquity. @Lars: Should I
open a bug report separately for this?

[1] https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-09/msg00872.html

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





  reply	other threads:[~2020-10-13 11:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 14:26 bug#43961: read carefully: dired-file-name-at-point vs dired-filename-at-point Boruch Baum
2020-10-13  3:49 ` Richard Stallman
2020-10-13  4:08   ` Boruch Baum
2020-10-13  4:54     ` Lars Ingebrigtsen
2020-10-13 10:25       ` Boruch Baum
2020-10-13 10:58         ` Arthur Miller
2020-10-13 11:27           ` Boruch Baum [this message]
2020-10-14  3:45         ` Lars Ingebrigtsen
2020-10-14  4:19           ` Boruch Baum
2020-10-14  4:43     ` Richard Stallman
2020-10-14  4:58       ` Lars Ingebrigtsen
2020-10-15  3:57         ` Richard Stallman

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=20201013112746.o5rc3rloylt33tbe@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=43961@debbugs.gnu.org \
    --cc=arthur.miller@live.com \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.org \
    /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).