all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Titus von der Malsburg <malsburg@posteo.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18722@debbugs.gnu.org
Subject: bug#18722: Correction
Date: Thu, 16 Oct 2014 07:46:45 -0700	[thread overview]
Message-ID: <87tx345ay2.fsf@posteo.de> (raw)
In-Reply-To: <83fveo49fb.fsf@gnu.org>

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


On 2014-10-16 Thu 03:04, Eli Zaretskii wrote:
> I'm not sure I understand this part:
>
>  > Also it seems that Emacs is responding to my input.  It just
>  > doesn't render changes in the windows and the minibuffer.
>
> If Emacs doesn't redisplay the changes, then what does "is responding
> to changes" mean?  How do you even kn ow Emacs responds to changes, if
> it doesn't redisplay?

As I said in the original post, correct rendering is resumed when I
click on a menu and I see that Emacs has in fact updated the buffers
according to my inputs.  Even before clicking on a menu item I see that
Emacs processes my input when for example menus change in response to
inputs: e.g., when I switch buffers, I see different menus at the top
according to the modes that are active in the respective buffers but the
windows are not updated.  So it seems that the problem really is
updating of the window displays.

I'm fairly sure that the problem was introduced by a recent change in
Emacs because I didn't change anything else at the time when the problem
first occurred.  Specifically, I did not change the window manager or
its configuration.

  Titus


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  parent reply	other threads:[~2014-10-16 14:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 20:24 bug#18722: 25.0.50; UI partly unresponsive after re-focus of Emacs' window Titus von der Malsburg
2014-10-15 21:41 ` bug#18722: Correction Titus von der Malsburg
2014-10-16  8:52   ` martin rudalics
2014-10-16 10:04     ` Eli Zaretskii
2014-10-16 11:41       ` martin rudalics
2014-10-16 12:04         ` Eli Zaretskii
2014-10-16 15:16         ` Titus von der Malsburg
2014-10-16 14:46       ` Titus von der Malsburg [this message]
2014-10-16 14:54         ` Eli Zaretskii
2014-10-16 15:10           ` Titus von der Malsburg
2014-10-16 15:34             ` Eli Zaretskii
2014-10-16 15:55               ` Titus von der Malsburg
2014-10-16 21:17               ` Titus von der Malsburg
2014-10-16 22:31                 ` Titus von der Malsburg
2014-10-17  0:53                   ` Stefan Monnier
2014-10-17  4:02                     ` Titus von der Malsburg
2014-10-17 17:48                       ` Jan Djärv
2014-10-17 18:14                         ` Titus von der Malsburg
2014-10-18 12:31                           ` Jan Djärv
2014-10-19 17:09                             ` Jan Djärv
2014-10-19 18:05                               ` Titus von der Malsburg
2014-10-19 20:33                                 ` Jan Djärv
2014-10-17  9:23                   ` martin rudalics
2014-10-17 12:55                     ` Stefan Monnier
2014-10-17 16:44                     ` Titus von der Malsburg
2014-10-16 16:07         ` Stefan Monnier
2014-10-16 19:36           ` Titus von der Malsburg

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=87tx345ay2.fsf@posteo.de \
    --to=malsburg@posteo.de \
    --cc=18722@debbugs.gnu.org \
    --cc=eliz@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 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.