unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Randy Taylor <dev@rjt.dev>
Cc: dgutov@yandex.ru, 59756@debbugs.gnu.org
Subject: bug#59756: [PATCH] Use file-name-nondirectory to determine project-name
Date: Fri, 02 Dec 2022 10:08:42 +0200	[thread overview]
Message-ID: <831qpigrcl.fsf@gnu.org> (raw)
In-Reply-To: <pTVX1m2AnkdhFahEsZnqS86UsE7L7iEb9TrBemq9rS948hvfctpXaM4f3LsZH9YQYWjpqu2bR3Wc7JoGCuhn7nWPFYkvI-UWsr5xU_rvu60=@rjt.dev> (message from Randy Taylor on Fri, 02 Dec 2022 03:34:30 +0000)

> Cc: dgutov@yandex.ru
> Date: Fri, 02 Dec 2022 03:34:30 +0000
> From: Randy Taylor <dev@rjt.dev>
> 
> If a project is named something like ".emacs.d", file-name-base will return ".emacs" instead of ".emacs.d" as
> expected (or at least as I expect it).
> 
> Therefore, we use file-name-nondirectory instead.

Why do we want to support such project names?

I could also name my project /foo/bar/baz, and defeat file-name-nondirectory
as well.  Where does it end?

My suggestion is to require that project names don't include slashes,
backslashes, periods and maybe also colon characters.





  reply	other threads:[~2022-12-02  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  3:34 bug#59756: [PATCH] Use file-name-nondirectory to determine project-name Randy Taylor
2022-12-02  8:08 ` Eli Zaretskii [this message]
2022-12-02 12:47   ` Stefan Kangas
2022-12-02 14:37   ` Dmitry Gutov
2022-12-02 15:24 ` Dmitry Gutov

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=831qpigrcl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59756@debbugs.gnu.org \
    --cc=dev@rjt.dev \
    --cc=dgutov@yandex.ru \
    /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).