From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: npostavs@users.sourceforge.net, 16984@debbugs.gnu.org,
jidanni@jidanni.org
Subject: bug#16984: dired-do-rename susceptible to .../~/... hijack
Date: Thu, 08 Dec 2016 19:23:30 +0200 [thread overview]
Message-ID: <837f7aibcd.fsf@gnu.org> (raw)
In-Reply-To: <87k2bawfpu.fsf@gmx.de> (message from Michael Albinus on Thu, 08 Dec 2016 17:25:17 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: npostavs@users.sourceforge.net, 16984@debbugs.gnu.org, jidanni@jidanni.org
> Date: Thu, 08 Dec 2016 17:25:17 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> As said in the other mail, it shall be made available as
> >> `file-name-quote', therefore. Eli?
> >
> > Are you asking me about the function's name? file-name-quote is OK
> > with me.
>
> The question was rather whether this function (and file-name-unquote,
> file-name-quoted-p) shall be exposed in files.el. I understand your
> answer that you agree :-)
Yes, thanks.
prev parent reply other threads:[~2016-12-08 17:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 18:10 bug#16984: dired-do-rename susceptible to .../~/... hijack 積丹尼 Dan Jacobson
2016-10-23 2:21 ` npostavs
2016-10-23 6:50 ` Eli Zaretskii
2016-10-29 2:27 ` npostavs
2016-10-29 7:01 ` Eli Zaretskii
2016-10-29 13:23 ` Michael Albinus
2016-10-29 15:54 ` npostavs
2016-10-29 16:22 ` Michael Albinus
2016-11-01 0:42 ` npostavs
2016-12-04 19:06 ` Michael Albinus
2016-12-08 1:47 ` npostavs
2016-12-08 8:23 ` Michael Albinus
2016-12-08 14:39 ` npostavs
2016-12-08 14:58 ` Michael Albinus
2016-12-08 17:03 ` Michael Albinus
2016-12-08 16:00 ` Eli Zaretskii
2016-12-09 4:56 ` npostavs
2016-12-09 8:05 ` Michael Albinus
2016-12-12 2:57 ` npostavs
2016-12-09 8:19 ` Eli Zaretskii
2016-12-08 15:58 ` Eli Zaretskii
2016-12-08 16:25 ` Michael Albinus
2016-12-08 17:23 ` Eli Zaretskii [this message]
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=837f7aibcd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16984@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=michael.albinus@gmx.de \
--cc=npostavs@users.sourceforge.net \
/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).