From: K Richard Pixley <pixleyr@google.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: K Richard Pixley <rich@noir.com>, 31032@debbugs.gnu.org
Subject: bug#31032: can't read emacs - unusable
Date: Mon, 2 Apr 2018 17:01:30 -0700 [thread overview]
Message-ID: <45724bdf-4ee9-a49b-8a53-ac0a09f9f389@google.com> (raw)
In-Reply-To: <87vad9nq2z.fsf@gmail.com>
Thank you.
Looks like I needed: emacs -Q -nw --color=never.
I can chase it down from there.
next prev parent reply other threads:[~2018-04-03 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 21:07 bug#31032: can't read emacs - unusable K Richard Pixley
2018-04-02 22:40 ` Noam Postavsky
2018-04-02 23:01 ` K Richard Pixley
2018-04-02 23:31 ` Noam Postavsky
2018-04-03 0:01 ` K Richard Pixley [this message]
2018-04-07 1:53 ` Noam Postavsky
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=45724bdf-4ee9-a49b-8a53-ac0a09f9f389@google.com \
--to=pixleyr@google.com \
--cc=31032@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=rich@noir.com \
/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).