Emacs (local and remote) does not open file or directory in command line

[RuijieYu]

Hello, I have encountered two possibly-related issues regarding the use of emacs on m1 mac: when running in terminal, emacs does not open the file or directory passed in as argument. Both emacs and tabby are installed using homebrew. I tried to revert tabby configuration to default and the behavior does not change. I don't know if this generalizes to hosts other platforms. However, I tried to ssh into different OSes (details below) and the behavior described below is consistent.

• When I run emacs using one of emacs file-or-dir and emacs -Q file-or-dir, tabby occasionally hangs. Other times, tabby opens emacs gui as intended, opening the file or directory passed in as command line arguments.
• When I run emacs using one of emacs -nw file-or-dir and emacs -Q -nw file-or-dir, emacs does not open the passed-in file. Instead, emacs opens the scratch buffer and I notice a "Quit" in the lower-left corner of the window. I suspect that tabby inserts characters which emacs does not expect. (Maybe Ctrl + G ?)
• When I ssh into a remote server and run emacs there in any aforementioned fashion, emacs also does not open the file or directory. Here, I tried both using a separate ssh profile and to ssh from my shell and both show the same behavior.
• I tried to run vim on both local and remote sessions, and the program opens up and loads the file or directory as intended.
• When using builtin terminal app on mac, both emacs and vim operate as expected.

Versions:

• OS
  • local os: macOS 12.0.1, uname -srm = Darwin 21.1.0 arm64
  • remote 1 (Arch Linux): uname -srm = Linux 5.15.10-hardened1-1-hardened x86_64
  • remote 2 (BSD jail): uname -srm = FreeBSD 12.2-RELEASE-p9 amd64
• programs
  • tabby: /Applications/Tabby.app/Contents/MacOS/Tabby --version = 1.0.169
  • local & remote emacs: emacs --version = GNU Emacs 27.2
  • local & remote vim: vim --version = VIM - Vi IMproved 8.2

I hope this is enough information for debugging. I won't be very responsive but will attach additional information if necessary.

[jzuhone]

I'm seeing the same issue.

[mathslimin]

login to wsl, ssh to remote, emacs can work

[Alex4386]

I also can reproduce this issue on Tabby 1.0.170 on Windows with a SSH-ed remote Ubuntu 20.04.3 LTS.

Running Emacs 26.3.

[Alex4386]

login to wsl, ssh to remote, emacs can work

This workaround is unavailable for the creator of the issue since local os of its is macOS. Plus, WSL is not a viable option if you are using in VM which does not support nested virtualization or running Hyper-V (WSL2 and Hyper-V (or any virtualization sw) can not co-exist).

[cburkins]

Just tried emacs for the first time within tabby, feels like I'm experiencing the same issue. Feels like emacs is (very) quickly closing the buffer with the specified file ? I used iterm2 (from a mac) to ssh into the same machine, and emacs (with same file) works just fine.