From: No Wayman <iarchivedmywholelife@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 69312@debbugs.gnu.org
Subject: bug#69312: 30.0.50; [WISHLIST] dicitionary buffer should retain search information
Date: Sun, 03 Mar 2024 12:16:42 -0500 [thread overview]
Message-ID: <87jzmjtev9.fsf@gmail.com> (raw)
In-Reply-To: <86r0grntey.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 03 Mar 2024 18:59:01 +0200")
Juri Linkov <juri@linkov.net> writes:
> close 69312 30.0.50
> thanks
>
>>>> This won't work. The buffer is in read-only mode, but even if
>>>> that is
>>>> inhibited,
>>>> the string is overwritten by the call to the display function
>>>> at the end:
>>>
>>>> (funcall function reply)
>>>
>>> With it installed, the dictionary-do-matching command is
>>> broken.
>>> It results in:
>>>
>>> dictionary-do-matching: Buffer is read-only: #<buffer
>>> *Dictionary*>
>>
>> Please provide a test case to reproduce the issue that you see.
>
> Never mind, I see now what is missing. So this is fixed now.
> Thanks for the bug report.
To clarify the issue:
(defun dictionary-do-matching (word dictionary strategy function)
"Search for WORD with STRATEGY in DICTIONARY and display them
with FUNCTION."
;;This insertion is thrown away...
(insert (format-message "Lookup matching words for `%s' in `%s'
using `%s'\n"
word dictionary strategy))
;; [OMITTED FUNCTION BODY]
;; ...when this display function is called
(funcall function reply)))
next prev parent reply other threads:[~2024-03-03 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 18:39 bug#69312: 30.0.50; [WISHLIST] dicitionary buffer should retain search information No Wayman
2024-02-23 7:12 ` Juri Linkov
2024-02-23 15:29 ` No Wayman
2024-02-24 17:39 ` Juri Linkov
2024-02-25 4:06 ` No Wayman
2024-02-25 7:19 ` Juri Linkov
2024-03-02 17:31 ` Juri Linkov
2024-03-03 1:46 ` No Wayman
2024-03-03 7:50 ` Juri Linkov
2024-03-03 16:59 ` Juri Linkov
2024-03-03 17:16 ` No Wayman [this message]
2024-03-03 17:49 ` Juri Linkov
2024-03-03 20:59 ` No Wayman
2024-03-05 16:43 ` 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=87jzmjtev9.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=69312@debbugs.gnu.org \
--cc=juri@linkov.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 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).