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.bugs Subject: bug#6965: 23.2; tags search/replace order no longer sensitive to starting file Date: Tue, 4 Aug 2020 08:53:18 -0700 Message-ID: References: <4C7E6A71.8080503@smart.net> <87bln53j6r.fsf@stefankangas.se> 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="1424"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 6965-done@debbugs.gnu.org To: "Daniel B." Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 04 17:54:20 2020 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 1k2zGe-0000Eg-AV for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 04 Aug 2020 17:54:20 +0200 Original-Received: from localhost ([::1]:39258 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k2zGd-0000sI-Cy for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 04 Aug 2020 11:54:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40538) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k2zGN-0000kr-EL for bug-gnu-emacs@gnu.org; Tue, 04 Aug 2020 11:54:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37365) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k2zGN-0002UD-5A for bug-gnu-emacs@gnu.org; Tue, 04 Aug 2020 11:54:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1k2zGN-0000BI-4k for bug-gnu-emacs@gnu.org; Tue, 04 Aug 2020 11:54:03 -0400 Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Tue, 04 Aug 2020 15:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 6965 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo unreproducible Mail-Followup-To: 6965@debbugs.gnu.org, stefan@marxist.se, dsb@smart.net Original-Received: via spool by 6965-done@debbugs.gnu.org id=D6965.1596556406609 (code D ref 6965); Tue, 04 Aug 2020 15:54:02 +0000 Original-Received: (at 6965-done) by debbugs.gnu.org; 4 Aug 2020 15:53:26 +0000 Original-Received: from localhost ([127.0.0.1]:48902 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2zFm-00009k-9n for submit@debbugs.gnu.org; Tue, 04 Aug 2020 11:53:26 -0400 Original-Received: from mail-yb1-f194.google.com ([209.85.219.194]:40832) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2zFk-00009Y-Vq for 6965-done@debbugs.gnu.org; Tue, 04 Aug 2020 11:53:25 -0400 Original-Received: by mail-yb1-f194.google.com with SMTP id q3so2715557ybp.7 for <6965-done@debbugs.gnu.org>; Tue, 04 Aug 2020 08:53:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:user-agent :mime-version:date:message-id:subject:to:cc; bh=QL7z7kEZLk3ECbJMGaCBnFo0UGIb899Sb+NoerJpxbs=; b=ST6TtusasuLw3LFNallKcK9SfkzGUmTnIwOJsE5ZQARUQqPxncp0+Ap9Odk1W4Fo7I 3htum/6mrX3/k+ErXsBWZg3phyJ9UI4tmAg+jETzvH4SS/xxdrej81ztqx4Q6bjjQsb8 AtEVBI8m/Xpt8ogoCAPABIeUkyCkv5LC0cgWCq6RhzbdtJaaMMdGJMZIrpHnnYwhhdj9 GXW9ZSd6pRCiABK6AHdjK0g8a0WN5DdmdVkZlcuSKkOwQxnS0QruyvcaQKJbltIRuZ2g Ec9KbvmDAVssq3RAUQIIXLP4csUCNhP3vilvib0ZGkpug8yL2Bs1IW7DkCIDhVmqsFyZ 5c6A== X-Gm-Message-State: AOAM530cZoIxB91AQHXCHhjPBHzPtQCm90bUEPK2SMQIgPLIPWr9dqu7 wIlQpPOO5g591F/hcVxNtIGtsRQxiXxUNMqRSYE= X-Google-Smtp-Source: ABdhPJzwOXdvEUbCfKyRZKt3KQYMP4ZS9wy2QHra5Rnr6DkLdm6l/LjRiTr0kVayTtFJQ21mpNV4cyDfdqiAgwuRm1g= X-Received: by 2002:a25:7007:: with SMTP id l7mr30960590ybc.85.1596556399370; Tue, 04 Aug 2020 08:53:19 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Tue, 4 Aug 2020 08:53:18 -0700 In-Reply-To: <87bln53j6r.fsf@stefankangas.se> (Stefan Kangas's message of "Sun, 03 May 2020 03:23:40 +0200") 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:184021 Archived-At: Stefan Kangas writes: >> The order in which tags tables files are searched is broken (relative >> to previous versions of Emacs and the current documentation): >> >> It no longer is sensitive to the starting file, as specified in the >> info documentation (32.2.6): >> >> These commands scan the list of tags tables starting with the first >> tags table (if any) that describes the current file, proceed from there >> to the end of the list, and then scan from the beginning of the list >> until they have covered all the tables in the list." >> >> That is, if you have a tags file for dir1/... and a tags file for >> dir2/... and load both using visit-tags-table and choose to add to the >> current list (rather than replacing), then starting a tags-search from >> a file dir2/f should start searching per the tags table file for >> dir2/..., and starting from a file dir1/f should start searching per the >> tags file for dir1/.... >> >> However, Emacs 23.2 seems to always start with the same tags table file, >> regardless of which file is the current file. > > (This old bug unfortunately never got a reply at the time.) > > Are you still seeing this on a modern version of Emacs? We have a > message to the bug from 2016 saying that one user was unable to > reproduce this on Emacs 26.1. More information was requested, but none was given within 13 weeks, so I'm closing this bug. If this is still an issue, please reply to this email (use "Reply to all" in your email client) and we can reopen the bug report. Best regards, Stefan Kangas