unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: casouri@gmail.com, stefankangas@gmail.com, 60511@debbugs.gnu.org
Subject: bug#60511: 29.0.50; treesit-ready-p should not emit warning by default
Date: Sun, 08 Jan 2023 13:03:09 +0200	[thread overview]
Message-ID: <837cxxqoeq.fsf@gnu.org> (raw)
In-Reply-To: <86358lwhbr.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 08 Jan 2023 10:39:36 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: Yuan Fu <casouri@gmail.com>,  stefankangas@gmail.com,
>   60511@debbugs.gnu.org
> Date: Sun, 08 Jan 2023 10:39:36 +0200
> 
> >> I can make treesit-ready-p not emit any warning by default, and change
> >> the quiet parameter to WARN, and accept either 'warn or ‘message.
> >> 
> >> Basically:
> >> 
> >> (treesit-ready-p lang) => t/nil
> >> (treesit-ready-p lang 'warn) => t/emit warning
> >> (treesit-ready-p lang 'message) => t/message
> >> 
> >> Eli, WDYT?
> >
> > I think the default should be to emit a warning, like we do now.
> 
> Then how users could change this default?

In what situation?

If they invoke the mode, they aren't supposed to disable the warning,
and they cannot.





  reply	other threads:[~2023-01-08 11:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 11:19 bug#60511: 29.0.50; treesit-ready-p should not emit warning by default Stefan Kangas
2023-01-03 17:44 ` Juri Linkov
2023-01-04  7:02 ` Yuan Fu
2023-01-04  7:47   ` Juri Linkov
2023-01-08  1:31 ` Yuan Fu
2023-01-08  5:53   ` Eli Zaretskii
2023-01-08  8:39     ` Juri Linkov
2023-01-08 11:03       ` Eli Zaretskii [this message]
2023-01-08 17:35         ` Juri Linkov
2023-01-08 17:57           ` Eli Zaretskii
2023-01-08 18:11             ` Juri Linkov
2023-01-08 18:48               ` Eli Zaretskii
2023-01-08 18:14     ` Stefan Kangas
2023-01-08 18:28       ` Juri Linkov
2023-01-08 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=837cxxqoeq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60511@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=juri@linkov.net \
    --cc=stefankangas@gmail.com \
    /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).