unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Neil Okamoto <neil.okamoto@gmail.com>
To: 41156@debbugs.gnu.org
Subject: bug#41156: Updated description
Date: Mon, 11 May 2020 10:14:45 -0700	[thread overview]
Message-ID: <BD02FFE2-9237-468F-9156-88F2AC888DD5@gmail.com> (raw)
In-Reply-To: <2E809CFD-2C79-4529-BB68-4510A0F7C4D9@gmail.com>

After further testing, I wanted to clarify that this occurs even without linum-mode.  It occurs whenever there are window margins to either side of the vertical divider.

So, e.g. 

$ emacs -nw -q
    M-x xterm-mouse-mode
    C-x b *scratch*
    C-x 3

    Use the mouse to drag the vertical divider right and left? Succeeds.

Now set a right margin on the left window:

    (set-window-margins (selected-window) 0 2)

    Use the mouse to drag the vertical divider to the left?
    Fails with the message “<right-margin> <mouse-movement> is undefined”

    (set-window-margins (selected-window) 0 0)

    And mouse-movement is permitted again.

Similarly, setting a left margin on the right window:

    (set-window-margins (selected-window) 2 0)

    Use the mouse to drag the vertical divider to the right?
    Fails with the message “<left-margin> <mouse-movement> is undefined”

    (set-window-margins (selected-window) 0 0)

    And mouse-movement is permitted again.







  reply	other threads:[~2020-05-11 17:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 18:21 bug#41156: 26.3; 27.0.91; linum-mode interferes with xterm-mouse-mode Neil Okamoto
2020-05-11 17:14 ` Neil Okamoto [this message]
2021-06-13 12:10   ` bug#41156: margins interfere " Lars Ingebrigtsen
2021-06-13 14:52     ` martin rudalics
2021-06-14 12:46       ` Lars Ingebrigtsen
2021-06-14 12:56         ` Eli Zaretskii
2021-06-15  3:51           ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-15  5:29             ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-15  7:50               ` martin rudalics
2021-06-15 11:19               ` Eli Zaretskii
2021-06-15 13:54               ` Lars Ingebrigtsen

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=BD02FFE2-9237-468F-9156-88F2AC888DD5@gmail.com \
    --to=neil.okamoto@gmail.com \
    --cc=41156@debbugs.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).