all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: branch master segfault (2019-02-05)
Date: Wed, 06 Feb 2019 17:44:25 +0200	[thread overview]
Message-ID: <83y36ssyzq.fsf@gnu.org> (raw)
In-Reply-To: <CAGK7Mr7RRuLQuop4114L-Oh-PoaRiqYtPt1pf-x56RG7LhWZ=A@mail.gmail.com> (message from Philippe Vaucher on Wed, 6 Feb 2019 10:30:06 +0100)

> From: Philippe Vaucher <philippe.vaucher@gmail.com>
> Date: Wed, 6 Feb 2019 10:30:06 +0100
> 
> Okay, Emacs works if I in term.c:753 if I use this:
> 
> ```
> coding = FRAME_TERMINAL_CODING (f);
> ```
> 
> instead of:
> 
> ```
> coding = (FRAME_TERMINAL_CODING (f)->common_flags & CODING_REQUIRE_ENCODING_MASK ?
> FRAME_TERMINAL_CODING (f) : &safe_terminal_coding);
> ```
> 
> I know docker allocates a "pseudo TTY", so probably that there's a misdetection happening here.

No, it isn't misdetection.  The problem is that safe_terminal_coding
is not set up.



  parent reply	other threads:[~2019-02-06 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 14:48 branch master segfault (2019-02-05) Philippe Vaucher
2019-02-05 16:50 ` Eli Zaretskii
2019-02-06  9:00   ` Philippe Vaucher
     [not found]     ` <CAGK7Mr5KL6HPuemBXEHNQ_g6+KqhCoQPAOtQZ+zQ0mMsjQ8--A@mail.gmail.com>
2019-02-06  9:30       ` Philippe Vaucher
2019-02-06 10:33         ` Philippe Vaucher
2019-02-06 15:33           ` Eli Zaretskii
2019-02-06 15:44         ` Eli Zaretskii [this message]
2019-02-06 16:23           ` Philippe Vaucher
2019-02-06 16:45             ` Eli Zaretskii
2019-02-06 19:00               ` Philippe Vaucher
2019-02-06 19:46                 ` Eli Zaretskii
2019-02-09 17:15                   ` Philippe Vaucher

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y36ssyzq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philippe.vaucher@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.