From: joakim@verona.se
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 68486@debbugs.gnu.org
Subject: bug#68486: 29.1; Confusing window layout changes in image-dired
Date: Tue, 16 Jan 2024 10:53:36 +0100 [thread overview]
Message-ID: <87cyu1hae7.fsf@tanaka.verona.se> (raw)
In-Reply-To: <874jfdwspy.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Tue, 16 Jan 2024 10:08:41 +0100")
Manuel Giraud <manuel@ledu-giraud.fr> writes:
> joakim@verona.se writes:
>
>> I have a question about image dired. I find it very confusing the way
>> window layout changes in image-dired happen.
>>
>> Basically I want a window layout like depicted here:
>> https://www.emacswiki.org/emacs/ImageDired
>>
>> In words: a 3 window layout, dired to the left, image dired top right, larger
>> view of current image bottom right.
>>
>> +----+----+
>> | | |
>> | +----+
>> | | |
>> +----+----+
>>
>> Whenever I try to set this layout up by hand the main image view jumps between
>> windows, ruining my layout.
>
> Hi Joakim,
>
> I have tried your layout and you're right that this is annoying: for me
> the dired buffer and image view buffer are switching windows each time I
> go to the next image.
>
> Maybe we should try to fix this but, as usual, with Emacs display layout
> it could not be to everybody's taste.
Agreed, but I think it wouldnt be controversial to keep an existing
user created layout, and you seem to agree with this sentiment.
>
>> Theres a function image-dired-display-image that displays the image
>> you select for display in the thumb view window. the call to
>> kill-buffer and then pop-to-buffer would seem to indicate that this is
>> the intended behaviour, or is it? Shouldnt the code try to preserve
>> the users window configuration if possible?
>>
>> The function, notice kill-buffer then pop-to-buffer.
>
> Thanks for this hint. You're right that the kill/pop-to/rename dance
> may be the cause of this issue.
I tried just removing the kill-buffer, but that didnt work, I guess the
call is there for a reason. I thought that if the buffer isnt killed,
and the content just replaced everything should work, but aparently not.
If you come up with a patch I will try it!
--
Joakim Verona
joakim@verona.se
prev parent reply other threads:[~2024-01-16 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 20:16 bug#68486: 29.1; Confusing window layout changes in image-dired joakim
2024-01-16 9:08 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 9:52 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 11:51 ` joakim
2024-01-16 14:36 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 14:46 ` Eli Zaretskii
2024-01-16 15:32 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 9:53 ` joakim [this message]
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=87cyu1hae7.fsf@tanaka.verona.se \
--to=joakim@verona.se \
--cc=68486@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).