unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 13691@debbugs.gnu.org
Subject: bug#13691: 24.3.50; Problem with glyphs in unibyte buffers
Date: Mon, 31 Aug 2020 21:23:35 +0000	[thread overview]
Message-ID: <CADwFkmndU6rzCc4DUMBDAeXgNscmDvQRuAv82+tSPrQhXki33Q@mail.gmail.com> (raw)
In-Reply-To: <CADs++6hgQwW0vAqMTXnDrf4ZNvCKgjXrkU-EyC400FVKtuKbDg@mail.gmail.com>

Eduardo Ochs <eduardoochs@gmail.com> writes:

> It seems that the bug is solved in Emacs26. I don't have Emacs27
> or git Emacs in this machine, but I will compile them tomorrow
> and check.
>
> The shell script that I used to do the test is below (for the sake of
> completeness). It creates two very similar files that only differ in
> their "coding:" lines and then opens them with "emacs26 -Q". After
> opening each of them you will have to run `M-x eval-buffer' and then
> do a `C-x C-e' after the `(insert ...)' line close to the end.

Thanks, please report back with your findings.  (Chances are the bug is
fixed if it works on Emacs 26, but it's always good to know for sure.)

> Just a curiosity... is there a standard(-ish) way to send a
> script like this to a shell buffer? I use eev all the time and in
> eev this is trivial - see:
>
>   http://angg.twu.net/eev-intros/find-eepitch-intro.html#1
>
> but sometimes I need to send scripts and tests like this to
> people that don't use eev...

I'm not aware of anything like that, sorry.





  reply	other threads:[~2020-08-31 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12  1:37 bug#13691: 24.3.50; Problem with glyphs in unibyte buffers Eduardo Ochs
2013-02-12  9:02 ` Andreas Schwab
2013-02-12 22:13   ` Eduardo Ochs
2020-08-31  2:32     ` Stefan Kangas
2020-08-31  4:49       ` Eduardo Ochs
2020-08-31 21:23         ` Stefan Kangas [this message]
2020-11-25 10:03           ` Stefan Kangas
2021-01-01 18:45             ` 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=CADwFkmndU6rzCc4DUMBDAeXgNscmDvQRuAv82+tSPrQhXki33Q@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=13691@debbugs.gnu.org \
    --cc=eduardoochs@gmail.com \
    --cc=schwab@linux-m68k.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).