From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#46926: Remove the quotes from highlighted/linked symbols when displaying docs Date: Tue, 16 Mar 2021 17:45:16 +0200 Message-ID: References: <83czw3jy72.fsf@gnu.org> <835z1vjvm4.fsf@gnu.org> <83ft0zhuyi.fsf@gnu.org> <838s6rhthh.fsf@gnu.org> <6214567e-7e89-010d-5d0a-de0b69392625@yandex.ru> <831rcgfgpd.fsf@gnu.org> <401c0b82-a6b9-eb74-8de8-84fc956f8813@yandex.ru> <83r1kfeptr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12580"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 Cc: laszlomail@protonmail.com, larsi@gnus.org, stefan@marxist.se, rms@gnu.org, 46926@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Mar 16 16:47:22 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1lMBuj-0003Ad-OM for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Mar 2021 16:47:21 +0100 Original-Received: from localhost ([::1]:38292 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lMBui-000622-Ny for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Mar 2021 11:47:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60458) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lMBtS-0005Nh-LN for bug-gnu-emacs@gnu.org; Tue, 16 Mar 2021 11:46:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57492) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lMBtS-0000Qy-Bt for bug-gnu-emacs@gnu.org; Tue, 16 Mar 2021 11:46:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lMBtS-00028o-AB for bug-gnu-emacs@gnu.org; Tue, 16 Mar 2021 11:46:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 16 Mar 2021 15:46:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46926 X-GNU-PR-Package: emacs Original-Received: via spool by 46926-submit@debbugs.gnu.org id=B46926.16159095298175 (code B ref 46926); Tue, 16 Mar 2021 15:46:02 +0000 Original-Received: (at 46926) by debbugs.gnu.org; 16 Mar 2021 15:45:29 +0000 Original-Received: from localhost ([127.0.0.1]:40805 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lMBsr-00027f-Aq for submit@debbugs.gnu.org; Tue, 16 Mar 2021 11:45:29 -0400 Original-Received: from mail-wr1-f42.google.com ([209.85.221.42]:40855) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lMBsp-00027T-V8 for 46926@debbugs.gnu.org; Tue, 16 Mar 2021 11:45:24 -0400 Original-Received: by mail-wr1-f42.google.com with SMTP id v11so7684840wro.7 for <46926@debbugs.gnu.org>; Tue, 16 Mar 2021 08:45:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UOgRP556OIyR0ZB9Sw3cL5XsjJh1oE5ayCjVtm9RReI=; b=l2EoKbceOFjcS5KQWGV8YIpszeeoa1fnxm5fc91TsT6OYq/FPGIHUBtECdxP/KnLXI rKfGA90al2w3nGqjLVyF8jI/jMgj0wfO7GFRtzbDXKhK+uEH2btGxsUvkxxShQuEchCe V5KZzxspRzZtMga5F/Pcz2XIrhADjowqCsST8TbHDZOn+T6EnNL5ytwR9MgawGmMEzhZ OblMen4RQhwKjzFrXhRAXxtrweMTMkYB/Hu6xvFrz9vlDUj+GXscGnetMB1FCbW24J85 nRE5tSIahsP65ys4OjLzC2vp2+x3Fx9FMsRMTj907Z+VB3jk+8wfBUYuUI6JtF8odd26 0GHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UOgRP556OIyR0ZB9Sw3cL5XsjJh1oE5ayCjVtm9RReI=; b=M8e5V/TjjD7tcAMaX3wLN09FedyWoL+50a5T6F9GXm0r6WTA4OjQdfbKxlGOzb+uDE 1yReDbwGaF3SUftzYSVuld927rIz2vvOmA0iJGe0kOzkfRDTL7Df7hwC5MJzv34GSl3X RZXKJ3iCWdfAZhkMwEbfqIEvC/npl9pDYkMo/91p+VcNCBSbMBzq7MwEN72R1xasxroM oaCtVkgmlQ7zhZ10myd2FmpOfkF1OJMY4TwtfEONolrKQfueWIcQ+yMV+zF7RifUH5nd w2/vZJNkNNRLOUJkUpkLk1evr6n79MHYIPtQNpahNaSHuxBfMUQq91dxuGdqd8D+sQjz 00Og== X-Gm-Message-State: AOAM533zrXPrdJ1XDNMXRpBu7UFdoc2JqZNPDY4WTUnKCS9L+LTUl87x leRbRb+9mF0BchJH+2WJrmdyImSvYug= X-Google-Smtp-Source: ABdhPJzI8YJof4A/ZTEeAoPWQhP42zJmn324hM4a37W47dDD/G1wzFbBRZ3m/WyzB79Wl0U4RvZ6Ew== X-Received: by 2002:adf:b355:: with SMTP id k21mr5642241wrd.156.1615909518377; Tue, 16 Mar 2021 08:45:18 -0700 (PDT) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id u4sm23925057wrm.24.2021.03.16.08.45.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Mar 2021 08:45:17 -0700 (PDT) In-Reply-To: <83r1kfeptr.fsf@gnu.org> Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:202464 Archived-At: On 16.03.2021 05:32, Eli Zaretskii wrote: >> Cc: laszlomail@protonmail.com, 46926@debbugs.gnu.org, larsi@gnus.org, >> stefan@marxist.se, rms@gnu.org >> From: Dmitry Gutov >> Date: Tue, 16 Mar 2021 01:20:27 +0200 >> >> On 15.03.2021 19:51, Eli Zaretskii wrote: >>>>>> Until the project has such an expert consultant, wouldn't asking the >>>>>> emacs community be a better way to decide such issues? E.g. running >>>>>> a vote on /r/emacs. >>>>> No, because offering an opt-in behavior is a better way of letting >>>>> users to try the feature. >>>> Perhaps these two actions can be combined? >>> How would you propose to combine them? >> >> We add the option, announce it, and in 2-4 weeks ask people for their >> opinion based on their experience with the changed UI. > > I don't see how this is different from offering an opt-in behavior, so > I'm okay with this. Simply saying "let's make it opt-in" closes the door on the discussion of the subsequent change of the default, which is often what reporters care about in discussions like this. But if we say "let's make it opt-in then discuss the change later", that has a higher chance of making both sides happier. And helps us gather feedback backed by some usage experience.