all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 18649@debbugs.gnu.org
Subject: bug#18649: 25.0.50; Closing TTY menus on MS-Windows
Date: Wed, 08 Oct 2014 13:29:52 +0300	[thread overview]
Message-ID: <83lhoqkg67.fsf@gnu.org> (raw)
In-Reply-To: <543504AF.9050300@gmx.at>

> Date: Wed, 08 Oct 2014 11:32:31 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 18649@debbugs.gnu.org
> 
>  > IOW, we throw to top level too early
>  > or too radically.
> 
> Do you see any way to debug this?

If no other idea presents itself, the hard way: by stepping through
the code in keyboard.c that processes keyboard input.

>  > Update: the problem is definitely caused by r117587; reverting it
>  > fixes the problem.  I reviewed the diffs, more than once, and I cannot
>  > see what could be the reason.  Martin, your help will be appreciated.
> 
> I'm just as lost as you are.  I tried to partially revert changes that
> could have affected this on w32 but with no luck.

Sigh.  I guess that commit just exposed some other bug, then.

Thanks for trying.

> BTW: Is there a way to turn `blink-cursor-mode' off on a TTY?

No, it blinks "in hardware" (i.e., the terminal software does it).
And there's no reason to disable it, because it should never do
anything on a TTY.  Or do you have evidence to the contrary?





  reply	other threads:[~2014-10-08 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07  6:50 bug#18649: 25.0.50; Closing TTY menus on MS-Windows Dani Moncayo
2014-10-07 15:46 ` Eli Zaretskii
2014-10-07 19:58   ` Eli Zaretskii
2014-10-08  9:32   ` martin rudalics
2014-10-08 10:29     ` Eli Zaretskii [this message]
2014-10-08 12:49       ` Eli Zaretskii
2014-10-08 13:13         ` Dani Moncayo
2014-10-08 13:35         ` martin rudalics
2014-10-08 13:57           ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lhoqkg67.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18649@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.