unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31274@debbugs.gnu.org, monnier@IRO.UMontreal.CA
Subject: bug#31274: 27.0.50; xdisp.c:7575: Emacs fatal error: assertion failed: IT_BYTEPOS (*it) == CHAR_TO_BYTE (IT_CHARPOS (*it))
Date: Fri, 04 May 2018 15:50:29 +0300	[thread overview]
Message-ID: <83d0ybtwiy.fsf@gnu.org> (raw)
In-Reply-To: <87o9hvn1xx.fsf@gmail.com> (message from Noam Postavsky on Fri, 04 May 2018 06:35:22 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Date: Fri, 04 May 2018 06:35:22 -0400
> Cc: 31274@debbugs.gnu.org
> 
> >     % src/emacs -Q /usr/bin/perl -l .../elpa/packages/nhexl-mode/nhexl-mode.el -f nhexl-mode --eval '(setq word-wrap t)'
> >     y
> >     M->
> >
> > The `y` is because nhexl-mode prompts the user to convert the buffer
> > to unibyte and is not directly relevant: you can use find-file-literally
> > instead and the result is the same.
> 
> I couldn't reproduce the assert failure, and I didn't get the unibyte
> prompt either.

I think the unibyte prompt may or may not be seen, it depends on
whether Emacs succeeds to decide the file is a binary file, and uses
unibyte to begin with.  And whether it decides that depends on the
contents of the file, so it could well be that you don't see it
(neither did I, FWIW).

Or maybe this is the sign of something special that happens on
Stefan's system, like local changes perhaps?

In any case, we need either a reproducer or a detailed backtrace to
make any progress with this bug.

Thanks.





  reply	other threads:[~2018-05-04 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 19:54 bug#31274: 27.0.50; xdisp.c:7575: Emacs fatal error: assertion failed: IT_BYTEPOS (*it) == CHAR_TO_BYTE (IT_CHARPOS (*it)) Stefan Monnier
2018-04-28  9:29 ` Eli Zaretskii
2018-04-28  9:47   ` Eli Zaretskii
2018-05-04 10:35 ` Noam Postavsky
2018-05-04 12:50   ` Eli Zaretskii [this message]
2019-09-26 19:29     ` 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=83d0ybtwiy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31274@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=npostavs@gmail.com \
    /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).