From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Randy Taylor <dev@rjt.dev>
Cc: 59756@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#59756: [PATCH] Use file-name-nondirectory to determine project-name
Date: Fri, 2 Dec 2022 04:47:35 -0800 [thread overview]
Message-ID: <CADwFkmmjtWPmpLVGVLpzd8kXP+h4LBj=sSLiywnHBCZJmiP3Wg@mail.gmail.com> (raw)
In-Reply-To: <831qpigrcl.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> 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?
Because people put their configuration files under version control, and
they want to use project commands there. For example "~/.emacs.d",
which is what I use.
> 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.
It's fine to disallow slashes, backslashes, and colons, but banning
periods would break some of my most important use-cases. So I hope we
won't do that.
next prev parent reply other threads:[~2022-12-02 12:47 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
2022-12-02 12:47 ` Stefan Kangas [this message]
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='CADwFkmmjtWPmpLVGVLpzd8kXP+h4LBj=sSLiywnHBCZJmiP3Wg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=59756@debbugs.gnu.org \
--cc=dev@rjt.dev \
--cc=dgutov@yandex.ru \
--cc=eliz@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).