unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs development <emacs-devel@gnu.org>
Subject: Re: terminal getting garbled running 'emacs -nw'
Date: Sat, 9 Aug 2014 14:14:14 -0700	[thread overview]
Message-ID: <CAKOHPAnMgSi++YtBP7f_pXaLi6-PEDi8scM86GfhqBsfPqb12w@mail.gmail.com> (raw)
In-Reply-To: <83a97dlbxw.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

I agree. Once you reproduce the problem with the first approach, the second
flow reproduces it again. I am suspecting if we are somehow corrupting the
tty.

I am happy that you could reproduce it. Give me some pointers and I will
debug. By the way, it has been a long (almost 5 years) since I started
following emacs-devel closely.
Nice to see the same familiar hackers hacking away on emacs.

with best regards,
dhruva


On Sat, Aug 9, 2014 at 12:06 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Sat, 9 Aug 2014 10:03:17 -0700
> > From: dhruva <dhruvakm@gmail.com>
> >
> > I found an easier way to reproduce the problem.
> >
> > - Run emacs in terminal (-nw) mode: emacs -q -nw
> > - M-x to enger minibuffer prompt
> > - Type 'ho' and hit TAB
> > - CTRL-g will quit the command but the menubar is gone and the minibuffer
> > frame is multiple lines high
>
> This doesn't reproduce the problem for me (your previous recipe did).
>

[-- Attachment #2: Type: text/html, Size: 1441 bytes --]

  reply	other threads:[~2014-08-09 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 16:47 terminal getting garbled running 'emacs -nw' dhruva
2014-08-09 17:03 ` dhruva
2014-08-09 19:06   ` Eli Zaretskii
2014-08-09 21:14     ` dhruva [this message]
2014-08-09 22:15       ` dhruva
2014-08-10  2:46       ` Eli Zaretskii
2014-08-10 17:55         ` dhruva

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=CAKOHPAnMgSi++YtBP7f_pXaLi6-PEDi8scM86GfhqBsfPqb12w@mail.gmail.com \
    --to=dhruvakm@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.
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).