From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 47300@debbugs.gnu.org
Subject: bug#47300: delete-window to select window with same position
Date: Mon, 7 Jun 2021 09:35:07 +0200 [thread overview]
Message-ID: <52edd629-faee-9c91-525d-51a34d8a0a15@gmx.at> (raw)
In-Reply-To: <87zgw2lnyb.fsf@mail.linkov.net>
> The customization interface could use only functions that could be
> first called before deletion, then the customized function returns
> a lambda that will be called after deletion.
Only specialized users would be able to write such a function. And they
can use the 'delete-window' parameter for that purpose.
> Then for example
> all 'pos' logic could be moved to a separate function:
>
> (defun delete-window-pos ()
> (let ((frame-selected-window-edges (window-edges frame-selected-window nil nil t))
> (frame-selected-window-pos (nth 2 (posn-at-point nil frame-selected-window))))
> (lambda ()
> (let ((new-frame-selected-window
> (window-at-pos
> (+ (nth 0 frame-selected-window-edges)
> (car frame-selected-window-pos))
> (+ (nth 1 frame-selected-window-edges)
> (cdr frame-selected-window-pos))
> frame t)))
> (and new-frame-selected-window
> ;; Select window at WINDOW's position at point.
> (set-frame-selected-window
> frame new-frame-selected-window))))))
I'm completely lost with the scoping of that first `let'. So at least
for a poor soul like me such a solution would not be feasible at all.
martin
next prev parent reply other threads:[~2021-06-07 7:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 20:31 bug#47300: delete-window to select window with same position Juri Linkov
2021-05-18 14:49 ` Lars Ingebrigtsen
2021-05-18 16:00 ` martin rudalics
2021-05-18 20:17 ` Juri Linkov
2021-05-19 7:42 ` martin rudalics
2021-05-19 16:07 ` Juri Linkov
2021-05-19 17:41 ` martin rudalics
2021-05-22 8:05 ` martin rudalics
2021-05-22 21:25 ` Juri Linkov
2021-05-23 8:43 ` martin rudalics
2021-05-25 6:50 ` martin rudalics
2021-05-26 21:29 ` Juri Linkov
2021-05-27 15:20 ` martin rudalics
2021-05-31 20:46 ` Juri Linkov
2021-06-02 9:08 ` martin rudalics
2021-06-03 21:20 ` Juri Linkov
2021-06-04 9:19 ` martin rudalics
2021-06-04 16:29 ` Juri Linkov
2021-06-06 7:43 ` martin rudalics
2021-06-06 20:47 ` Juri Linkov
2021-06-07 7:35 ` martin rudalics [this message]
2021-06-07 21:00 ` Juri Linkov
2021-06-10 7:44 ` martin rudalics
2021-06-11 17:06 ` Juri Linkov
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=52edd629-faee-9c91-525d-51a34d8a0a15@gmx.at \
--to=rudalics@gmx.at \
--cc=47300@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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).