From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: bug with `apropos-value' in Emacs 29.0?
Date: Sun, 22 May 2022 02:05:17 +0200 [thread overview]
Message-ID: <875ylyl9du.fsf@dataswamp.org> (raw)
In-Reply-To: 874k1itozr.fsf@web.de
Michael Heerdegen wrote:
>> $ emacs -Q --batch --eval "(progn (require 'tramp-sh) (apropos-value
>> \"70\"))"
>
> I'm sorry, that succeeds without error here.
On Emacs 29.0? Weird!
> Nevertheless, could you please check the value of
> `debug-on-signal'? I don't say you did something, I just
> don't understand the behavior you see. When I turn
> debug-on-signal on, then I do get a similar backtrace.
`debug-on-signal' is nil.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-05-22 0:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 18:34 bug with `apropos-value' in Emacs 29.0? Emanuel Berg
2022-05-21 18:41 ` Marcin Borkowski
2022-05-21 19:10 ` Emanuel Berg
2022-05-21 19:13 ` Emanuel Berg
2022-05-21 22:45 ` Emanuel Berg
2022-05-21 22:52 ` Emanuel Berg
2022-05-21 23:29 ` Michael Heerdegen
2022-05-21 23:33 ` Emanuel Berg
2022-05-21 23:51 ` Michael Heerdegen
2022-05-21 23:36 ` Emanuel Berg
2022-05-22 0:00 ` Michael Heerdegen
2022-05-22 0:05 ` Emanuel Berg [this message]
2022-05-22 0:32 ` Michael Heerdegen
2022-05-22 0:38 ` Emanuel Berg
2022-05-22 1:07 ` Michael Heerdegen
2022-05-22 4:51 ` Emanuel Berg
2022-05-22 5:27 ` Michael Heerdegen
2022-05-22 13:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-05-22 17:43 ` Emanuel Berg
2022-05-23 5:19 ` Marcin Borkowski
2022-05-23 21:07 ` get Emacs soruce (was: Re: bug with `apropos-value' in Emacs 29.0?) Emanuel Berg
2022-05-22 7:09 ` bug with `apropos-value' in Emacs 29.0? Marcin Borkowski
2022-05-23 21:22 ` output Emacs version (was: Re: bug with `apropos-value' in Emacs 29.0?) Emanuel Berg
2022-05-22 7:37 ` bug with `apropos-value' in Emacs 29.0? Kévin Le Gouguec
2022-05-21 18:49 ` 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
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=875ylyl9du.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@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.
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).