unofficial mirror of bug-gnu-emacs@gnu.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 08:10:37 -0700	[thread overview]
Message-ID: <87r3y859ua.fsf@posteo.de> (raw)
In-Reply-To: <83wq802hfz.fsf@gnu.org>

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


On 2014-10-16 Thu 07:54, Eli Zaretskii wrote:
> I'm not sure.  What you see is the result of Emacs updating the
> display, but you cannot know whether the changes to buffers according
> to your inputs happened while the display was outdated, or immediately
> prior to updating the display as result of your clicking.
>
> IOW, it could be that all your inputs are processed in one go when you
> click, and the display updated right after that.
>
> Or do you have evidence that the scenario I described did not in fact
> happen?

I can enter text and save the buffer before clicking menu items.  When I
inspect the content of the file with another editor, I see that it
contains the text that I entered before saving.

>> 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.
>
> It would be helpful if you could quantify "recent" to the best of your
> knowledge and records, if not bisect the trunk.  Thanks in advance.

Given on how rarely I update to the latest development version of Emacs,
I can't say anything more precise than that the problem was introduced
during this summer.  I know, not very helpful.

What do you mean with bisect?  Checkout earlier versions and test them
until I find the bad commit?  Given the high volume of commits in Emacs
this would take quite a while even when using an efficient
search strategy.

  Titus



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

  reply	other threads:[~2014-10-16 15:10 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
2014-10-16 14:54         ` Eli Zaretskii
2014-10-16 15:10           ` Titus von der Malsburg [this message]
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

  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=87r3y859ua.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 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).