From: Eli Zaretskii <eliz@gnu.org>
To: Rahguzar <rahguzar@zohomail.eu>
Cc: look@strawberrytea.xyz, emacs-devel@gnu.org
Subject: Re: improving debug output of get-buffer
Date: Sat, 04 Nov 2023 10:45:39 +0200 [thread overview]
Message-ID: <838r7d6h58.fsf@gnu.org> (raw)
In-Reply-To: <87lebghy6k.fsf@zohomail.eu> (message from Rahguzar on Thu, 02 Nov 2023 17:57:03 +0100)
> From: Rahguzar <rahguzar@zohomail.eu>
> Cc: look@strawberrytea.xyz, emacs-devel@gnu.org
> Date: Thu, 02 Nov 2023 17:57:03 +0100
>
> > We could improve the diagnostics of set-buffer. But I'm still at a
> > loss how that would have helped you here when "stringp nil" did not.
>
> As a clumsy programmer I cause quite a lot of errors, a sizable of them
> of `stringp nil` variety and mostly they are caused by wrong
> manipulation of strings. So when I see it I tend to hunt for strings I
> in the code. I think `buffer-or-string-p` will narrow down the places
> where I need to look quite substantially.
Patches to improve the error messages from set-buffer will be welcome.
I think we should use something similar to nsberror there.
next prev parent reply other threads:[~2023-11-04 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 15:11 improving debug output of get-buffer Rahguzar
2023-11-02 16:44 ` Eli Zaretskii
2023-11-02 16:57 ` Rahguzar
2023-11-04 8:45 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 18:06 StrawberryTea
2023-11-01 19:38 ` Eli Zaretskii
2023-11-01 20:02 ` StrawberryTea
2023-11-02 6:00 ` 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=838r7d6h58.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=look@strawberrytea.xyz \
--cc=rahguzar@zohomail.eu \
/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).