unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 41245@debbugs.gnu.org, Trevor Spiteri <tspiteri@ieee.org>
Subject: bug#41245: 27.0.91; Error clicking on a button in custom-mode in another window
Date: Thu, 14 May 2020 17:28:37 +0200	[thread overview]
Message-ID: <m2k11ezgbe.fsf@gmail.com> (raw)
In-Reply-To: <CABczVwcjGpJuLenBHXFM64DT=V9sYosdpj=X=v8msvk-PD8EnA@mail.gmail.com> (Mauro Aranda's message of "Thu, 14 May 2020 10:53:36 -0300")

>>>>> On Thu, 14 May 2020 10:53:36 -0300, Mauro Aranda <maurooaranda@gmail.com> said:

    Mauro> Trevor Spiteri <tspiteri@ieee.org> writes:
    >> 1. Run emacs -Q
    >> 2. Fill the *scratch* buffer with some text (350 characters is enough).
    >> 3. M-x customize-option-other-window abbrev-all-caps
    >> 4. C-x o (to switch back to *scratch* buffer window)
    >> 5. Click on "Toggle" button right next to "Abbrev All Caps"
    >> 
    >> The text " [ State ]: EDITED, shown value does not take effect until
    >> you set or save it.\n" (81 characters including new line) is inserted at
    >> point 298 in the scratch buffer, overwriting 29 characters in the
    >> process. 298 is also the point at which the State button is drawn in the
    >> custom buffer. The custom-mode window is also broken: the State button
    >> now appears as regular text.
    >> 

    Mauro> I think the proposed patches in Bug#40788 would solve this problem as
    Mauro> well.

Did I not commit the fix? .... No, I didnʼt, Iʼll get to it soon I
hope.

If the patch from Bug#40788 works Iʼll merge the two reports.

Robert





  reply	other threads:[~2020-05-14 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 21:58 bug#41245: 27.0.91; Error clicking on a button in custom-mode in another window Trevor Spiteri
2020-05-14 13:53 ` Mauro Aranda
2020-05-14 15:28   ` Robert Pluim [this message]
2020-05-14 18:54     ` Trevor Spiteri

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=m2k11ezgbe.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=41245@debbugs.gnu.org \
    --cc=maurooaranda@gmail.com \
    --cc=tspiteri@ieee.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).