unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 56198@debbugs.gnu.org, carlmarcos@tutanota.com, eliz@gnu.org
Subject: bug#56198: Request to delete window with mouse event
Date: Sun, 26 Jun 2022 17:01:02 +0200	[thread overview]
Message-ID: <87letjeafl.fsf@gnus.org> (raw)
In-Reply-To: <87k0943k5u.fsf@gmail.com> (Visuwesh's message of "Sat, 25 Jun 2022 19:44:05 +0530")

Visuwesh <visuweshm@gmail.com> writes:

> Ah indeed, that would be nice.  The following patch does the job for me
> but maybe there's a cleaner way to do this?

[...]

> -    (delete-window (posn-window (event-start click)))))
> +    (when (eq (posn-window (event-end click))
> +              (posn-window (event-start click)))
> +      (delete-window (posn-window (event-start click))))))

I think it makes sense to change the behaviour here, but this doesn't
seem to do the trick for me?  I.e., <mouse-3> on the mode line, and then
moving the pointer out of the mode line, and then releasing it still
deletes the window.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-26 15:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 15:27 bug#56198: Request to delete window with mouse event carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 17:05 ` Juri Linkov
2022-06-24 17:10 ` Visuwesh
     [not found] ` <878rpmasxd.fsf@gmail.com-N5LgcGT----2>
2022-06-25  7:35   ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-25  8:14     ` Visuwesh
2022-06-25  8:24     ` Eli Zaretskii
2022-06-25 12:34       ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-25 14:14         ` Visuwesh
2022-06-26 15:01           ` Lars Ingebrigtsen [this message]
2022-06-26 15:26             ` Visuwesh
2022-06-26 15:31               ` Lars Ingebrigtsen
2022-06-26 15:40                 ` Visuwesh
2022-06-26 15:46                   ` Lars Ingebrigtsen
     [not found]           ` <87letjeafl.fsf@gnus.org-N5VXCNa--7-2>
2022-06-26 15:15             ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-26 15:20               ` Eli Zaretskii
2022-06-29  0:07 ` Tak Kunihiro
     [not found] ` <m1v8skib7p.fsf@misasa.okayama-u.ac.jp-N5gmMGf--N-2>
2022-06-29  0:15   ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-29  9:16     ` Tak Kunihiro
     [not found]     ` <m1k08zhlt0.fsf@misasa.okayama-u.ac.jp-N5io4Li----2>
2022-06-29 10:37       ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87letjeafl.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56198@debbugs.gnu.org \
    --cc=carlmarcos@tutanota.com \
    --cc=eliz@gnu.org \
    --cc=visuweshm@gmail.com \
    /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).