From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22096@debbugs.gnu.org
Subject: bug#22096: 25.0.50; reading from fifo breaks display
Date: Sat, 5 Dec 2015 12:09:08 -0500 [thread overview]
Message-ID: <20151205170908.GA6375@holos> (raw)
In-Reply-To: <83a8pog7z8.fsf@gnu.org>
On 05/12/15 at 06:45pm, Eli Zaretskii wrote:
> > From: Mark Oteiza <mvoteiza@udel.edu>
> > Date: Sat, 05 Dec 2015 10:58:38 -0500
> >
> > > Anyway, you are reading a binary byte stream from an audio daemon, so
> > > I think you cannot expect it to be displayed in any human-readable
> > > way, let alone hope that the major mode in effect in *scratch will be
> > > able to fontify it in some reasonable way. You should use
> > > insert-file-contents-literally instead, I think. (And I very much
> > > doubt that "visiting" a non-regular file makes sense, but maybe I'm
> > > missing something.)
> >
> > Right, I didn't expect VISIT=t to make sense, but the resulting breakage
> > is unexpected.
>
> Emacs tries to decode the binary stream (unless you use the -literally
> variant), and the result could look (to Emacs) like some text that
> fits some font-locking or paren-matching pattern.
The same display oddity does still happen with
(insert-file-contents-literally "/tmp/mpd.fifo" t 0 10 nil)
and nothing appears to be inserted
next prev parent reply other threads:[~2015-12-05 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 17:40 bug#22096: 25.0.50; reading from fifo breaks display Mark Oteiza
2015-12-05 8:19 ` Eli Zaretskii
2015-12-05 8:59 ` Eli Zaretskii
2015-12-05 16:06 ` Mark Oteiza
2015-12-05 16:49 ` Eli Zaretskii
2015-12-05 15:58 ` Mark Oteiza
2015-12-05 16:45 ` Eli Zaretskii
2015-12-05 17:09 ` Mark Oteiza [this message]
2015-12-05 17:18 ` Eli Zaretskii
2015-12-05 17:35 ` Mark Oteiza
2015-12-05 18:29 ` Mark Oteiza
2015-12-05 19:38 ` Eli Zaretskii
2015-12-05 20:58 ` Mark Oteiza
2020-08-31 2:11 ` Stefan Kangas
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=20151205170908.GA6375@holos \
--to=mvoteiza@udel.edu \
--cc=22096@debbugs.gnu.org \
--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).