From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.bugs Subject: bug#38367: 26.3; Cannot start Emacs with -nw option, starting with Emacs 26.1 Date: Tue, 26 Nov 2019 03:45:05 +0100 Message-ID: References: <55beb437-0b0f-4fb7-8ae5-1a6d6b15d4eb@default> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004a4cb8059836e075" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="81991"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 38367@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 26 03:46:11 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iZQrj-000LD4-HU for geb-bug-gnu-emacs@m.gmane.org; Tue, 26 Nov 2019 03:46:11 +0100 Original-Received: from localhost ([::1]:49746 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZQrh-0005Mn-UI for geb-bug-gnu-emacs@m.gmane.org; Mon, 25 Nov 2019 21:46:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38058) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZQrc-0005Mh-0Y for bug-gnu-emacs@gnu.org; Mon, 25 Nov 2019 21:46:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZQra-0004O5-Ng for bug-gnu-emacs@gnu.org; Mon, 25 Nov 2019 21:46:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44098) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iZQra-0004Nt-Gd for bug-gnu-emacs@gnu.org; Mon, 25 Nov 2019 21:46:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iZQra-0007aJ-Dx for bug-gnu-emacs@gnu.org; Mon, 25 Nov 2019 21:46:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juanma Barranquero Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 26 Nov 2019 02:46:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38367 X-GNU-PR-Package: emacs Original-Received: via spool by 38367-submit@debbugs.gnu.org id=B38367.157473634929128 (code B ref 38367); Tue, 26 Nov 2019 02:46:02 +0000 Original-Received: (at 38367) by debbugs.gnu.org; 26 Nov 2019 02:45:49 +0000 Original-Received: from localhost ([127.0.0.1]:50071 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iZQrN-0007Zk-H6 for submit@debbugs.gnu.org; Mon, 25 Nov 2019 21:45:49 -0500 Original-Received: from mail-qt1-f171.google.com ([209.85.160.171]:34751) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iZQrL-0007ZV-So for 38367@debbugs.gnu.org; Mon, 25 Nov 2019 21:45:48 -0500 Original-Received: by mail-qt1-f171.google.com with SMTP id i17so19786065qtq.1 for <38367@debbugs.gnu.org>; Mon, 25 Nov 2019 18:45:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kdPJuQMkgedfkf+6lxQmQeFCIp8mr2VlKivbfcDtaD0=; b=qKZtnPEAswv8p8WgRO4rM6Ivn15hZ4EDX2Ydi0LnyuCmY3mEf4gI5QecHiKYIHClEY RFfkVFOF9TONKt1y3Si1RD7sE6k9Y07aaC9YXSGoddCWhjmSeRzcNpWPsdFPMjlUtPp1 LYWYQjDMeKw6cY3AKOoQiJjDwKni8SxAnq7pwIxg5OOouWasHYZHFf/xeN5EwdJymY27 vNLMUMcuMrCHFwYUI1beOiX2VsdWFHc4xAi5/G+Jbhe1Q2F68rrxdeKpSZB61mnv+WXZ vfc9zV7qy9IVPiLyHdMuTwd5HyMXqmYEHWYBZefx9jbSW2fZZScZ1ER0Hct1vfbzXz3S RcQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kdPJuQMkgedfkf+6lxQmQeFCIp8mr2VlKivbfcDtaD0=; b=A1CFjwDYMQA4Fr2ry2hyjsC9QWvoEPFVwG5kFRHxCzFSn63EuHVOgpEm5sVVzxPRRv lgvAM26osBD5H5FnRguNlwMdyTg6EvOMcs1rFolzCTFbJbhollyirRfJh6QTpiHK3gUm E3I/9/8wcU95QtJ4E+Zbfroly+QbNIabVhGlBti6exWCxNak2TBrqD6eopYDlML7FFo4 1Pk9arEs7GGGoo0vQI6tFzA0IYRf6ze2iAZ8r76jaZBpNZkaKn9WycO7uNj5tDugAIqB P2zkqu3M+Tngo/LI50+ixYu6fWdOlUDpGxIx0ph87Dmt6oAGhIHVK2l79XT9/3LsgmeR ebTQ== X-Gm-Message-State: APjAAAWppNqVJ9KMPTOoFfn86kmjkD/kcWQry92oKIsKYy9E0z73FFs4 kHF+fyE/Z3R/DMOw7UEOjcmieW7k0n7cZ22K12Y= X-Google-Smtp-Source: APXvYqyZtFJEXLIOYW2YKV8gRcdzTUHPAbFoXFIxAUzyeItCDwfKrjAPFOgxhJttNAPvYoQtpDvMmB7HuLu9QBYTyxY= X-Received: by 2002:ac8:3a64:: with SMTP id w91mr32945824qte.242.1574736342145; Mon, 25 Nov 2019 18:45:42 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:172416 Archived-At: --0000000000004a4cb8059836e075 Content-Type: text/plain; charset="UTF-8" On Tue, Nov 26, 2019 at 1:56 AM Drew Adams wrote: > 24.5 works fine for me with -nw. Do you mean that if you create a desktop shortcut to 24.5's runemacs.exe that runs it with -Q -nw, and click on it, you get Emacs running in a console? Because I get an Emacs running with a hidden console (no visible frame). > That's what I've used for -nw in the past. > But I just tried plain `emacs' for -nw, and > that works too. (I use plain `emacs' for GUI.) I'm confused now. What do you mean with "That's what I've used for -nw in the past"? From a shortcut, or from CMD? > Does Emacs 26 on Windows 10 work for you > with -nw? 26.3 works as expected: 1) "emacs.exe -Q -nw" from CMD: starts a console Emacs inside CMD 2) "emacs.exe -Q" from CMD: starts a windows Emacs, but it's attached to the original CMD. 3) "runemacs.exe -Q -nw" from CMD: starts a detached console Emacs (i.e., I see nothing because there's no window) 4) "runemacs.exe -Q" from CMD: starts a detached windows Emacs (CMD is available to use). 5) "emacs.exe -Q -nw" from a shortcut: stars a console Emacs. 6) "emacs.exe -Q" from a shortcut: Stars a windows Emacs, but there's a visible console. 7) "runemacs.exe -Q -nw" from a shortcut: starts a console Emacs, but the console is hidden, so nothing is visible. 8) "runemacs.exe -Q" from a shortcut: starts a windows Emacs. Basically, runemacs.exe exists *specifically* to help with 2) and 6), because windows Emacs *always* creates a console, but when you're running a windows Emacs, you don't want to see it (it's just a nuisance). But if you're trying to run a console Emacs, "emacs.exe -Q -nw" is what you want, either in a shortcut or from the command line. So, what you see is not a bug, and I think it's always been so. I just tried with 20.7.3 and I get the very same behavior. --0000000000004a4cb8059836e075 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Tue, Nov 26, 2019 at 1:56 AM Drew Adams <drew.adams@oracle.com> wrote:
<= br>
> 24.5 works fine for me with -nw.

Do you mean= that if you create a desktop shortcut to 24.5's runemacs.exe that runs= it with -Q -nw, and click on it, you get Emacs running in a console?
=

Because I get an Emacs running with a hidden console (n= o visible frame).

> That's what I've us= ed for -nw in the past.
> But I just tried plain `emacs' f= or -nw, and
> that works too. =C2=A0(I use plain `emacs= 9; for GUI.)

I'm confused now.=C2=A0

What do you mean with "That's what I've used for -nw = in the past"? From a shortcut, or from CMD?

&= gt; Does Emacs 26 on Windows 10 work for you
> with -nw?

26.3 = works as expected:

1) "emacs.exe -Q -nw"= from CMD: starts a console Emacs inside CMD
2) "emacs.exe -= Q" from CMD: starts a windows Emacs, but it's attached to the orig= inal CMD.
3) "runemacs.exe -Q -nw" from CMD: starts= a detached console Emacs (i.e., I see nothing because there's no windo= w)
4) "runemacs.exe -Q" from CMD: starts a detached win= dows Emacs (CMD is available to use).

5) "ema= cs.exe -Q -nw" from a shortcut: stars a console Emacs.
6) &q= uot;emacs.exe -Q" from a shortcut: Stars a windows Emacs, but there= 9;s a visible console.
7) "runemacs.exe -Q -nw" from a = shortcut: starts a console Emacs, but the console is hidden, so nothing is = visible.
8) "runemacs.exe -Q" from a shortcut: starts a= windows Emacs.

Basically, runemacs.exe exists *sp= ecifically* to help with 2) and 6), because windows Emacs *always* creates = a console, but when you're running a windows Emacs, you don't want = to see it (it's just a nuisance).

But if you&#= 39;re trying to run a console Emacs, "emacs.exe -Q -nw" is what y= ou want, either in a shortcut or from the command line.

So, what you see is not a bug, and I think it's always been so. I= just tried with 20.7.3 and I get the very same behavior.


--0000000000004a4cb8059836e075--