From: Drew Adams <drew.adams@oracle.com>
To: Philippe Vaucher <philippe.vaucher@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Kangas <stefan@marxist.se>,
Emacs developers <emacs-devel@gnu.org>
Subject: RE: Namespaces - summary, conclusion
Date: Mon, 4 May 2020 11:25:20 -0700 (PDT) [thread overview]
Message-ID: <3db6a9c6-b6d3-4ffa-ad11-03edec323f38@default> (raw)
In-Reply-To: <CAGK7Mr4pPf7gnLFe91x0fZ-sdPjLszw4hJ+GoNS_fgTsDSaxkg@mail.gmail.com>
> > This one should be under the `file-name-` prefix.
> > Almost all other file-name manipulation functions are already there.
>
> That works for me.
Actually, it's most, but not almost all.
There are quite a few functions dealing
with file names that have `filename',
not `file-name', in their name. I'm
guessing that includes some that might
be called "file-name manipulation"
functions. (I see none, however that
use `filename-' as a _prefix_.)
(And no, such inconsistency is not very
important, IMO.)
next prev parent reply other threads:[~2020-05-04 18:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 9:27 Namespaces - summary, conclusion Philippe Vaucher
2020-05-04 10:11 ` Philippe Vaucher
2020-05-04 11:38 ` Stefan Kangas
2020-05-04 12:42 ` Philippe Vaucher
2020-05-04 13:13 ` Alfred M. Szmidt
2020-05-04 13:24 ` Stefan Kangas
2020-05-04 13:35 ` Joost Kremers
2020-05-04 14:18 ` Alfred M. Szmidt
2020-05-04 15:35 ` tomas
2020-05-04 16:32 ` Philippe Vaucher
2020-05-04 14:59 ` 조성빈
2020-05-04 16:28 ` Philippe Vaucher
2020-05-05 10:22 ` 조성빈
2020-05-04 15:00 ` Eli Zaretskii
2020-05-04 16:36 ` Philippe Vaucher
2020-05-04 16:52 ` Alfred M. Szmidt
2020-05-04 16:52 ` Alfred M. Szmidt
2020-05-05 16:12 ` Alfred M. Szmidt
2020-05-04 17:08 ` Eli Zaretskii
2020-05-04 18:47 ` Stefan Monnier
2020-05-04 17:36 ` Stefan Monnier
2020-05-04 18:05 ` Philippe Vaucher
2020-05-04 18:25 ` Drew Adams [this message]
2020-05-04 14:43 ` Eli Zaretskii
2020-05-04 16:25 ` Philippe Vaucher
2020-05-04 23:40 ` chad
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=3db6a9c6-b6d3-4ffa-ad11-03edec323f38@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philippe.vaucher@gmail.com \
--cc=stefan@marxist.se \
/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.