From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#38044: 27.0.50; There should be an easier way to look at a specific vc commit Date: Sun, 17 Nov 2019 23:20:17 +0200 Organization: LINKOV.NET Message-ID: <87r226xl8m.fsf@mail.linkov.net> References: <87ftj5at1q.fsf@gnus.org> <87r22phsoj.fsf@gmx.net> <87bltslnpo.fsf@mail.linkov.net> <87d0dvmqu8.fsf@mail.linkov.net> <590e595e-8220-1c7e-bd4a-b2eb0968e289@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="221839"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: Lars Ingebrigtsen , Stephen Berman , 38044@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Nov 17 22:33:11 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iWSAQ-000vY9-Bc for geb-bug-gnu-emacs@m.gmane.org; Sun, 17 Nov 2019 22:33:10 +0100 Original-Received: from localhost ([::1]:56488 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iWSAP-0005xP-8z for geb-bug-gnu-emacs@m.gmane.org; Sun, 17 Nov 2019 16:33:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38638) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iWS9L-0004mv-IL for bug-gnu-emacs@gnu.org; Sun, 17 Nov 2019 16:32:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iWS9K-0003yC-60 for bug-gnu-emacs@gnu.org; Sun, 17 Nov 2019 16:32:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33993) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iWS9K-0003xw-30 for bug-gnu-emacs@gnu.org; Sun, 17 Nov 2019 16:32:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iWS9J-0002PZ-V0 for bug-gnu-emacs@gnu.org; Sun, 17 Nov 2019 16:32:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 17 Nov 2019 21:32:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38044 X-GNU-PR-Package: emacs Original-Received: via spool by 38044-submit@debbugs.gnu.org id=B38044.15740263129241 (code B ref 38044); Sun, 17 Nov 2019 21:32:01 +0000 Original-Received: (at 38044) by debbugs.gnu.org; 17 Nov 2019 21:31:52 +0000 Original-Received: from localhost ([127.0.0.1]:42811 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iWS99-0002Oy-WF for submit@debbugs.gnu.org; Sun, 17 Nov 2019 16:31:52 -0500 Original-Received: from aye.elm.relay.mailchannels.net ([23.83.212.6]:40520) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iWS97-0002Op-Gb for 38044@debbugs.gnu.org; Sun, 17 Nov 2019 16:31:50 -0500 X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 2A9045A071C; Sun, 17 Nov 2019 21:31:48 +0000 (UTC) Original-Received: from pdx1-sub0-mail-a42.g.dreamhost.com (100-96-6-199.trex.outbound.svc.cluster.local [100.96.6.199]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id B2BBB5A0767; Sun, 17 Nov 2019 21:31:47 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from pdx1-sub0-mail-a42.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Sun, 17 Nov 2019 21:31:48 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jurta@jurta.org X-MailChannels-Auth-Id: dreamhost X-Wipe-Plucky: 43938f3a2ce87068_1574026307967_3230883832 X-MC-Loop-Signature: 1574026307967:3284610698 X-MC-Ingress-Time: 1574026307967 Original-Received: from pdx1-sub0-mail-a42.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a42.g.dreamhost.com (Postfix) with ESMTP id 5971E8014F; Sun, 17 Nov 2019 13:31:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=linkov.net; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=linkov.net; bh=5ZavlnHdN7FFng3oUt60ILqmbRY=; b= C3jMLNl5fzgdH9vsHymXshr1X97T3VpIa/a8wJygOxHCz5lhd/+GM/Hi13Zr5OWP HFRytPkkzEG0OVdrMSpOYs81W4SwN3k7WmfJzJx7pXm6Tt5ppzq60e4nTCJC4Ax9 qSGX5sepfBjKE0B8rhJoKA8QZJ7VXgpN2g4CQQmYsM4= Original-Received: from mail.jurta.org (m91-129-102-1.cust.tele2.ee [91.129.102.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by pdx1-sub0-mail-a42.g.dreamhost.com (Postfix) with ESMTPSA id BD7CE8015C; Sun, 17 Nov 2019 13:31:39 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a42 In-Reply-To: <590e595e-8220-1c7e-bd4a-b2eb0968e289@yandex.ru> (Dmitry Gutov's message of "Sun, 17 Nov 2019 13:53:07 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:171868 Archived-At: > But I don't think it's a good idea to mix the results of two different > searches. I think there should be two of them. But there could be an > extra -dwim- command I agree than dwim would be better. But what a hint to use for deciding on showing a commit by sha instead of matching it in the commit messages? > that makes the choice based on the word under point > (and whether it's hexinumeric). Making the choice whether the word is hexinumeric doesn't look too unambiguous. What if the user wants to search a hexinumeric word in the text of commit messages? For example, searching for "5761a1a393" to find messages that contain "Revert commit 5761a1a393 ..."