unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Running Emacs in an MSYS2 shell (or terminal?)
Date: Wed, 26 Jan 2022 19:36:23 +0100	[thread overview]
Message-ID: <xm46czke8hug.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <83sftaflnt.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Jan 2022 19:32:06 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
>> Date: Wed, 26 Jan 2022 17:55:32 +0100
>> Cc: help-gnu-emacs@gnu.org
>> 
>> Unfortunately, for the more important use case, "emacsclient.exe -nw
>> test.txt", or the like, a new frame - outside of the "defterm" window -
>> is always opening up.
>
> It is not clear to me what did you expect to happen with emacsclient
> invocation with the -nw switch.  Emacs on MS-Windows cannot create a
> new console window, nor can it "attach" to an existing console
> window.  Moreover, it cannot have both TTY and GUI frames in the same
> session.

I'm sorry for the ambiguity.  I wanted to emualate emacsclient -nw under
Gnu-Linux, namely, to operate it in a text console (TTY?) when Emacs is
running as a GUI application.

> With these limitations, does anything look out of order in the
> behavior that you see?

No, I just didn't know these limitations of Windows, only the
capabilites under Linux.  In fact, since this year I can do so much more
with Emacs (and MSYS2) under Windows than I previously expected! :-)

Compiling Emacs (Magit)
Compling LaTeX documents
PDF-tools is working
Running R with graphics output
Spellchecking with Hunspell
Encrypting .authinfo
Running Gnus
Using Tramp to connect to Linux servers

You helped me with most parts, thank you very much.

    Dieter



  reply	other threads:[~2022-01-26 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 16:37 Running Emacs in an MSYS2 shell (or terminal?) H. Dieter Wilhelm
2022-01-25 17:02 ` Eli Zaretskii
2022-01-25 19:20   ` H. Dieter Wilhelm
2022-01-25 17:51 ` Óscar Fuentes
2022-01-25 19:31   ` H. Dieter Wilhelm
2022-01-26  9:24 ` Arash Esbati
2022-01-26 16:55   ` H. Dieter Wilhelm
2022-01-26 17:32     ` Eli Zaretskii
2022-01-26 18:36       ` H. Dieter Wilhelm [this message]
2022-01-26 18:31     ` Arash Esbati

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=xm46czke8hug.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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.
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).