zsh-workers
 help / color / mirror / code / Atom feed
From: "Jérémie Roquet" <jroquet@arkanosis.net>
To: Simon Dahl <Macsimon98@hotmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Does the zsh shell impact the terminal of cs:go on macOS
Date: Tue, 16 Feb 2021 22:19:41 +0100	[thread overview]
Message-ID: <CAFOazAMyj3_rZfM3cwh+ri4kK2jPhRz9-pKyDHQx7p62yv=dBQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZULhCu27bTntOP_5QmPOJBy4+66ivuG+MzjUeUi4DCog@mail.gmail.com>

Hi Simon, hi Bart,

The CS:GO player on the list uses Linux, not macOS; that won't help ;)

Le mar. 16 févr. 2021 à 20:24, Bart Schaefer
<schaefer@brasslantern.com> a écrit :
> I suspect the launcher is making an assumption that the /bin/sh implementation
> is Bash, and therefore using a feature that isn't equivalent in zsh,

Another possibility is that at the same time macOS switched from bash
to zsh, it dropped 32 bits compatibility, which is known to have
broken quite a few things including Steam. Uninstalling Steam and
reinstalling its 64 bits version might be enough to fix the problem
with CS:GO (and other games that have full 64 bits support):

  https://support.steampowered.com/kb_article.php?ref=1055-ISJM-8568

> You'll probably have to take this up with Steam support.

I do agree with that. It seems that zsh is mentioned at the very
beginning of most Steam log files because Apple wanted people to know
about the change; it doesn't mean it has anything to do with problems
that may arise later in the logs. The 64 bits version of Steam is
supported under macOS Catalina, so the Steam support team should be in
the best position to help.

Best regards,

-- 
Jérémie


      reply	other threads:[~2021-02-16 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 19:17 Simon Dahl
2021-02-16 19:24 ` Bart Schaefer
2021-02-16 21:19   ` Jérémie Roquet [this message]

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='CAFOazAMyj3_rZfM3cwh+ri4kK2jPhRz9-pKyDHQx7p62yv=dBQ@mail.gmail.com' \
    --to=jroquet@arkanosis.net \
    --cc=Macsimon98@hotmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).