all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rameiko87@posteo.net
Cc: 69738@debbugs.gnu.org
Subject: bug#69738: Followup
Date: Sun, 14 Apr 2024 21:50:28 +0300	[thread overview]
Message-ID: <865xwjn5hn.fsf@gnu.org> (raw)
In-Reply-To: <06b44e7b07fcb2d06c7a7f56e4934014@posteo.net> (rameiko87@posteo.net)

> Date: Sun, 14 Apr 2024 17:55:55 +0000
> From: rameiko87@posteo.net
> Cc: 69738@debbugs.gnu.org
> 
> Actually the neat solution is probably to treat frames as a ring, so 
> that C-x 5 o would go back to the previous frame. Is there any reason 
> why frames were not conceived as a ring, but ``rigidly''?

Thanks, but it's a non-starter to change how frames are managed, just
to solve this minor issue.  The solution cannot be too complicated,
certainly not with TTY frames, where even the window manager isn't
involved.





  reply	other threads:[~2024-04-14 18:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 22:49 bug#69738: [BUG] rmail-mail-new-frame doesn't delete the new frame after composing the message on Emacs 29.2 rameiko87
2024-03-12 13:54 ` Eli Zaretskii
2024-03-21  8:57   ` Eli Zaretskii
2024-04-13 17:44 ` bug#69738: Followup rameiko87
2024-04-14  9:44   ` Eli Zaretskii
2024-04-14 16:14     ` rameiko87
2024-04-14 16:30       ` Eli Zaretskii
2024-04-14 17:47         ` rameiko87
2024-04-14 17:55           ` rameiko87
2024-04-14 18:50             ` Eli Zaretskii [this message]
2024-04-14 18:49           ` Eli Zaretskii
2024-04-15 10:15             ` rameiko87
2024-04-20 11:11               ` Eli Zaretskii
2024-05-04  9:37                 ` Eli Zaretskii
2024-05-06 19:12                   ` rameiko87
2024-05-12 22:42                   ` rameiko87
2024-05-13 10:53                     ` Eli Zaretskii
2024-05-28 13:28                       ` rameiko87
2024-06-20  9:58                         ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=865xwjn5hn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69738@debbugs.gnu.org \
    --cc=rameiko87@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.