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 15:58:55 -0500 [thread overview]
Message-ID: <20151205205855.GA18049@holos> (raw)
In-Reply-To: <83zixoele8.fsf@gnu.org>
On 05/12/15 at 09:38pm, Eli Zaretskii wrote:
> > From: Mark Oteiza <mvoteiza@udel.edu>
> > Date: Sat, 05 Dec 2015 13:29:14 -0500
> >
> > Simpler recipe:
> >
> > 1. mkfifo foo
> > 2. echo "bar" > foo
> >
> > In emacs -Q:
> >
> > 3. Evaluate (insert-file-contents-literally "foo" t)
> >
> > The buffer display is now broken.
>
> Thanks. My Emacs is configured with --enable-checking, so it aborted
> due to assertion violation. The patch below fixes that for me; please
> see if it fixes the display problem for you.
>
> diff --git a/src/fileio.c b/src/fileio.c
> index 6cda1e3..8e44eb0 100644
> --- a/src/fileio.c
> +++ b/src/fileio.c
> @@ -4265,7 +4265,7 @@ by calling `format-decode', which see. */)
> && NILP (replace))
> /* Visiting a file with these coding system makes the buffer
> unibyte. */
> - bset_enable_multibyte_characters (current_buffer, Qnil);
> + Fset_buffer_multibyte (Qnil);
> }
>
> coding.dst_multibyte = ! NILP (BVAR (current_buffer, enable_multibyte_charac\
> ters));
>
The patch does indeed fix the display problem. Thank you.
next prev parent reply other threads:[~2015-12-05 20:58 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
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 [this message]
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=20151205205855.GA18049@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).