From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: master 977f3f27c5 2/2: Don't issue warnings for Unicode quotes for now Date: Sat, 4 Jun 2022 23:04:41 +0200 Message-ID: References: <165425457951.24295.4901777157797017566@vcs2.savannah.gnu.org> <20220603110939.F1B93C06564@vcs2.savannah.gnu.org> <87ilpgacuf.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22418"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs developers To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 04 23:07:17 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nxazN-0005ZJ-8M for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Jun 2022 23:07:17 +0200 Original-Received: from localhost ([::1]:37274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nxazL-0006bZ-EB for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Jun 2022 17:07:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40210) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nxax4-0005nG-SD for emacs-devel@gnu.org; Sat, 04 Jun 2022 17:04:54 -0400 Original-Received: from mail-il1-f170.google.com ([209.85.166.170]:35708) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nxax3-0005kh-92 for emacs-devel@gnu.org; Sat, 04 Jun 2022 17:04:54 -0400 Original-Received: by mail-il1-f170.google.com with SMTP id u2so8709319iln.2 for ; Sat, 04 Jun 2022 14:04:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ibv7T11xE2sg4qtXxMe3znyYBJycTzDH0+5DBfVlUsY=; b=dQ5P0Qz5IE2y1/obYEtauEyF+wEyvDYFNf15AFXWuUosaF0ST24RAluyRRsEMJMnQi Erm/QgzWX6lcxO4a5ox9CMO9VrrAhkq91cT/HA9FfW40dbwk5CNSUQWJaaBD242TM6VW o6k0EBUQ4LP+G7Hoigid1xw0TnyO3x83zG1O0UJCJ0+x766o80/PXl532eglZ38CtKY9 Z2G8feW6lFqKsXGcVZsVlNH7JrjH4tRCBos2R9SVBqkxpo8u0k/mnyHSvK3/H76DuRIz i3y6idiHhvedqDxJ7zFV3VK9/1J/LBx4pHMcbua8hoiMWIu8hqXOOu8VsHj5fOgnmkXz hR2Q== X-Gm-Message-State: AOAM531/MgVmksanAHO79t2nSyAQtFhgcq/DM5gWJCsrrPnc8dV1vpYe j11GTpnUD25peh4t1Q2WIHjKB1DA8J87eoWNALQ= X-Google-Smtp-Source: ABdhPJyTo2EFYAdeHM1cYcbO0Z4wgsdLrmfWEaLsAT79OBVkj/9f9wa+bQwPuyu5egQdNSjPpi1UfS/RNFziNOdGLqk= X-Received: by 2002:a92:2c11:0:b0:2d0:e874:636 with SMTP id t17-20020a922c11000000b002d0e8740636mr9587092ile.318.1654376692051; Sat, 04 Jun 2022 14:04:52 -0700 (PDT) In-Reply-To: <87ilpgacuf.fsf@gnus.org> Received-SPF: pass client-ip=209.85.166.170; envelope-from=stefankangas@gmail.com; helo=mail-il1-f170.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290674 Archived-At: Lars Ingebrigtsen writes: > > How about keeping the warning but making it optional instead? That > > way, we could still use it in emacs.git. > > Hm... With a separate build target or something? For a warning like > this to be useful, it has to actually trigger for most people when > building Emacs. > > Or I guess the Makefile could just switch the warning on? I was thinking of making it depend on a separate variable or user option that we would set as a directory local variable. Could such an approach work?