From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs -nw display bug?
Date: Mon, 30 Jun 2014 20:04:50 +0300 [thread overview]
Message-ID: <83oaxa49cd.fsf@gnu.org> (raw)
In-Reply-To: <83pphq49mh.fsf@gnu.org>
> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD
> autolearn=disabled version=3.3.2
> Date: Mon, 30 Jun 2014 19:58:46 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> Just say no.
On second thought, go ahead and submit a bug report. Who knows, it
could be easy to fix. Or there might be a rainy day soon. Or
something.
next prev parent reply other threads:[~2014-06-30 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 15:57 emacs -nw display bug? Joost Kremers
2014-06-30 16:10 ` Eli Zaretskii
[not found] ` <mailman.4590.1404144667.1147.help-gnu-emacs@gnu.org>
2014-06-30 16:22 ` Joost Kremers
2014-06-30 16:58 ` Eli Zaretskii
2014-06-30 17:04 ` Eli Zaretskii [this message]
2014-06-30 21:06 ` Stefan Monnier
2014-07-01 8:53 ` Joost Kremers
2014-07-01 14:32 ` Stefan Monnier
2014-07-01 17:21 ` Eli Zaretskii
[not found] ` <mailman.4669.1404235282.1147.help-gnu-emacs@gnu.org>
2014-07-03 13:42 ` Joost Kremers
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=83oaxa49cd.fsf@gnu.org \
--to=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).