From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.help Subject: Re: Exploring a code base? Date: Sat, 07 Nov 2020 09:24:54 -0800 Message-ID: <87ft5l3wrd.fsf@ericabrahamsen.net> References: <57dcdf06-3bf4-4281-88d9-0e9c46adc757@yandex.ru> <83d00p6zj1.fsf@gnu.org> <837dqx6x65.fsf@gnu.org> <83361l6twf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22435"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 07 18:25:50 2020 Return-path: Envelope-to: geh-help-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 1kbRyH-0005jP-Tj for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 07 Nov 2020 18:25:49 +0100 Original-Received: from localhost ([::1]:42518 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kbRyG-00088b-Vf for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 07 Nov 2020 12:25:48 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39788) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbRxX-00087f-GI for help-gnu-emacs@gnu.org; Sat, 07 Nov 2020 12:25:03 -0500 Original-Received: from ericabrahamsen.net ([52.70.2.18]:55870 helo=mail.ericabrahamsen.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbRxT-0002Qs-1T; Sat, 07 Nov 2020 12:25:03 -0500 Original-Received: from localhost (24-113-150-48.wavecable.com [24.113.150.48]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 45DF1FA0B0; Sat, 7 Nov 2020 17:24:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1604769896; bh=mcEmaOVVWD5z2VTF9hJQ8p6V4ljGiWJcSApoTQfSS2E=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=YyPHn20tKWeP1/TTJ/hIdIAuG9p5+M9bgLBuEnJj/NlytiDxWjqo4YC6hWiA359Tr DQHRT96Kr7sDjWu76bivru7dsTYBBpHfq07351yugqAez9ICedqQnqmD0XbNtw1olk WHXysg/51J4Eic1T64xMh2Jsv3dJkLWFNcCWUwUY= In-Reply-To: <83361l6twf.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Nov 2020 17:58:24 +0200") Received-SPF: pass client-ip=52.70.2.18; envelope-from=eric@ericabrahamsen.net; helo=mail.ericabrahamsen.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/07 12:24:57 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:125095 Archived-At: Eli Zaretskii writes: >> From: Stefan Monnier >> Date: Sat, 07 Nov 2020 10:52:01 -0500 >> >> Most likely, all it takes is a command which adds an entry to some >> "central" Org file (probably a TODO entry) and another to quickly >> display that Org file. > > FWIW, when I need such facilities, I basically have the Org file where > I keep my notes visible in some window (or even in a separate frame) > at all times. So a "command to quickly display that Org file" boils > down to raising a frame at most, if the window is obscured. I use custom Org link types when editing novels or completing my own novel translations, linking to various editing "issues", and displaying them in a variety of ways. As Stefan notes, the need to handle multiple interconnected changes isn't specific to code. Perhaps there could be custom org link types that perform xref searches, or perform more complex semantic searches like "all instances of function `foo' that still use the old calling convention" and display using occur.