From: Eli Zaretskii <eliz@gnu.org>
To: Joel Reicher <joel.reicher@gmail.com>
Cc: 13850@debbugs.gnu.org, help-emacs-windows@gnu.org, larsi@gnus.org
Subject: bug#13850: Emacs for Windows: Launch better from a command prompt
Date: Sun, 01 May 2022 13:09:31 +0300 [thread overview]
Message-ID: <83bkwh7eec.fsf__30745.7118806028$1651399840$gmane$org@gnu.org> (raw)
In-Reply-To: <86zgk1lgm8.fsf@gmail.com> (message from Joel Reicher on Sun, 01 May 2022 19:57:51 +1000)
> From: Joel Reicher <joel.reicher@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 13850@debbugs.gnu.org,
> help-emacs-windows@gnu.org, Andrew Pennebaker
> <andrew.pennebaker@gmail.com>
> Date: Sun, 01 May 2022 19:57:51 +1000
>
> > "Use runemacs" seems like it's the correct answer here, so I'm closing
> > this bug report.
>
> It is the right answer, but I can't help thinking that there is an issue of ignorance amongst Window users.
>
> Does anyone know why the OP had this `wrong'?
Most probably because (a) he comes from Unix, and (b) he didn't read
the README.W32 file that comes with Emacs for Windows.
next prev parent reply other threads:[~2022-05-01 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 20:49 bug#13850: Emacs for Windows: Launch better from a command prompt Andrew Pennebaker
2013-03-01 22:54 ` K. Frank
2013-03-02 7:27 ` bug#13850: " Eli Zaretskii
[not found] ` <83k3pquuqy.fsf@gnu.org>
[not found] ` <CAHXt_SXakTei9TZFvjEmuggaGNHCQMq4xYfJ0Qtq1NwvOy_82g@mail.gmail.com>
2013-03-02 14:59 ` Eli Zaretskii
[not found] ` <CAHXt_SV+VVnj2yw189cNq15sKNqMonWZm2zH_FN3nOS5_PSa3w@mail.gmail.com>
2013-03-02 15:33 ` Eli Zaretskii
[not found] ` <CAHXt_SUFhkL64WPzOqTKq0Qq6FYFafC_t4m04qUnreB1Fd2MsQ@mail.gmail.com>
2013-03-02 16:22 ` Eli Zaretskii
2013-03-02 16:25 ` Lennart Borgman
2022-05-01 9:12 ` Lars Ingebrigtsen
2022-05-01 9:57 ` Joel Reicher
[not found] ` <86zgk1lgm8.fsf@gmail.com>
2022-05-01 10:09 ` Eli Zaretskii [this message]
[not found] ` <83bkwh7eec.fsf@gnu.org>
2022-05-01 10:35 ` Joel Reicher
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='83bkwh7eec.fsf__30745.7118806028$1651399840$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=13850@debbugs.gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=joel.reicher@gmail.com \
--cc=larsi@gnus.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.savannah.gnu.org/cgit/emacs.git
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).