From: Eli Zaretskii <eliz@gnu.org>
To: Mohammed Sadiq <sadiq@sadiqpk.org>
Cc: 60490@debbugs.gnu.org
Subject: bug#60490: 29.0.60; sqlite-mode-open-file fails to work over tramp
Date: Sun, 15 Jan 2023 12:10:08 +0200 [thread overview]
Message-ID: <83r0vw5csf.fsf@gnu.org> (raw)
In-Reply-To: <18d046cdad634772ab0fff852bcf53a0@sadiqpk.org> (message from Mohammed Sadiq on Sun, 15 Jan 2023 13:49:49 +0530)
> Date: Sun, 15 Jan 2023 13:49:49 +0530
> From: Mohammed Sadiq <sadiq@sadiqpk.org>
> Cc: 60490@debbugs.gnu.org
>
> >> In that case, it would be better to show a warning message that
> >> it's not supported instead of failing with errors that gives no
> >> hint to the user.
> >
> > I disagree that we should show a warning in such cases. The user
> > asked Emacs to do something, and Emacs couldn't; the appropriate
> > response is to signal an error, not to show a warning. Showing a
> > warning would mean we don't abort whatever Lisp program that was
> > trying to do something we cannot do.
> >
> > I agree that a more targeted error message would be beneficial;
> > patches for that are welcome as well.
>
> An error message was what I meant.
I've now added a more meaningful error message to sqlite-mode.el.
> >> Also, Emacs may also show the related bug number regarding such
> >> issues so that interested users can subscribe to know updates.
> >
> > We don't have any infrastructure in Emacs for doing stuff like that.
> > It would be a useful feature, I think (although not easy to
> > implement), but please submit a separate feature request for it.
>
> I was suggesting to show an error message like:
> "sqlite-xxx is not supported over tramp, see bug#xxx"
Sorry, no: I don't think it's right for us to have references to bug
reports in our sources, let alone in error messages. It's a long-term
maintenance problem, especially when we change the issue tracker.
prev parent reply other threads:[~2023-01-15 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 11:26 bug#60490: 29.0.60; sqlite-mode-open-file fails to work over tramp Mohammed Sadiq
2023-01-02 12:43 ` Eli Zaretskii
2023-01-15 5:41 ` Mohammed Sadiq
2023-01-15 7:27 ` Eli Zaretskii
2023-01-15 8:19 ` Mohammed Sadiq
2023-01-15 10:10 ` Eli Zaretskii [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=83r0vw5csf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60490@debbugs.gnu.org \
--cc=sadiq@sadiqpk.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).