From: Mike Kupfer <mkupfer@alum.berkeley.edu>
To: 58279@debbugs.gnu.org
Subject: bug#58279: 29.0.50; image-dired and background processing
Date: Mon, 03 Oct 2022 17:12:00 -0700 [thread overview]
Message-ID: <158019.1664842320@alto> (raw)
After updating to master 0df73dabc1, I noticed what looks like
contradictory text in etc/NEWS.
On the one hand, we have text saying that image-dired creates thumbnails
in the background:
-----8<-----8<-----
*** 'image-dired-show-all-from-dir-max-files' has been increased to 500.
This option controls asking for confirmation when starting Image-Dired
in a directory with many files. However, Image-Dired creates
thumbnails in the background these days, so this is not as important
as it used to be, back when entering a large directory could lock up
Emacs for tens of seconds. In addition, you can now customize this
option to nil to disable this confirmation completely.
----->8----->8-----
On the other hand, we have text that seems to say that background
processing does not happen:
-----8<-----8<-----
*** Some commands and user options are now obsolete.
Since Image-Dired no longer converts images in the background before
displaying them, some commands and user options that are no longer
needed are now obsolete:
'image-dired-cmd-create-temp-image-options',
'image-dired-cmd-create-temp-image-program',
'image-dired-display-current-image-full',
'image-dired-display-current-image-sized',
'image-dired-display-window-height-correction',
'image-dired-display-window-width-correction',
'image-dired-temp-image-file'.
----->8----->8-----
Is this just a matter of confusing wording, or is one of these text
excerpts flat-out wrong?
(I did go to savannah just now to see if the latest etc/NEWS has
different text, and it does, but the apparent conflict remains.)
mike
next reply other threads:[~2022-10-04 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 0:12 Mike Kupfer [this message]
2022-10-04 5:43 ` bug#58279: 29.0.50; image-dired and background processing Stefan Kangas
2022-10-04 14:35 ` Mike Kupfer
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=158019.1664842320@alto \
--to=mkupfer@alum.berkeley.edu \
--cc=58279@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).