From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 35495@debbugs.gnu.org, ueno@unixuser.org, federicotedin@gmail.com
Subject: bug#35495: 27.0.50; Untarring an archive with a keyring.gpg inside
Date: Sun, 12 May 2019 07:20:47 +0300 [thread overview]
Message-ID: <8336lkcnhc.fsf@gnu.org> (raw)
In-Reply-To: <jwvwoiw6acj.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 11 May 2019 15:55:01 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: federicotedin@gmail.com, 35495@debbugs.gnu.org, ueno@unixuser.org
> Date: Sat, 11 May 2019 15:55:01 -0400
>
> >> So this FIXME suggests maybe we should introduce a new file operation
> >> `write-region-literally`?
> > Probably. But the question of what should that do (since you rejected
> > tweaking inhibit-file-name-operation for that) still stands, I think.
>
> In the absence of a file-name-handler, it should just defer to write-region.
I'm confused: I thought we were talking about features implemented via
file-name handlers. jka-compr is, for example.
Or are you saying write-region-literally shouldn't even try file-name
handlers? That'd be different from what
insert-file-contents-literally does.
> > And I'm not sure we will always want to disable encoding and EOL
> > conversion, so that should be an add-on for "truly" literal I/O.
>
> I am.
For the present use case, sure. But we are discussing a more general
solution, right? The question is, will all of them want to disable
those conversions?
next prev parent reply other threads:[~2019-05-12 4:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 20:02 bug#35495: 27.0.50; Untarring an archive with a keyring.gpg inside Stefan Monnier
2019-05-08 22:26 ` Federico Tedin
2019-05-09 0:53 ` Stefan Monnier
2019-05-09 23:00 ` Federico Tedin
2019-05-10 0:24 ` Stefan Monnier
2019-05-11 0:26 ` Federico Tedin
2019-05-11 0:37 ` Stefan Monnier
2019-05-11 1:43 ` Federico Tedin
2019-05-11 1:54 ` Stefan Monnier
2019-05-11 2:20 ` Federico Tedin
2019-05-11 12:54 ` Stefan Monnier
2019-05-11 16:24 ` Federico Tedin
2019-05-11 6:48 ` Eli Zaretskii
2019-05-11 12:55 ` Stefan Monnier
2019-05-11 13:06 ` Eli Zaretskii
2019-05-11 14:10 ` Stefan Monnier
2019-05-11 14:22 ` Eli Zaretskii
2019-05-11 19:55 ` Stefan Monnier
2019-05-12 4:20 ` Eli Zaretskii [this message]
2019-05-12 15:23 ` Stefan Monnier
2019-05-12 15:57 ` Eli Zaretskii
2022-04-22 13:13 ` Lars Ingebrigtsen
2022-04-22 13:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-22 14:18 ` Lars Ingebrigtsen
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=8336lkcnhc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35495@debbugs.gnu.org \
--cc=federicotedin@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=ueno@unixuser.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).