From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id mKWKKI+Wu1/ocQAA0tVLHw (envelope-from ) for ; Mon, 23 Nov 2020 11:01:35 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id CCp8JI+Wu18iOgAAB5/wlQ (envelope-from ) for ; Mon, 23 Nov 2020 11:01:35 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3E40F9404E5 for ; Mon, 23 Nov 2020 11:01:35 +0000 (UTC) Received: from localhost ([::1]:47298 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kh9bB-000513-Mb for larch@yhetil.org; Mon, 23 Nov 2020 06:01:33 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:45432) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kh9Zf-00050t-Kc for emacs-orgmode@gnu.org; Mon, 23 Nov 2020 05:59:59 -0500 Received: from static.rcdrun.com ([95.85.24.50]:43915) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kh9Zd-0003YW-JB for emacs-orgmode@gnu.org; Mon, 23 Nov 2020 05:59:59 -0500 Received: from localhost ([::ffff:41.202.241.56]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C000B.000000005FBB962A.00004AC0; Mon, 23 Nov 2020 10:59:54 +0000 Date: Mon, 23 Nov 2020 12:14:19 +0300 From: Jean Louis To: Ihor Radchenko Subject: Re: Bring up a screen giving option to open a series of orgmode files Message-ID: References: <169441F9-83D6-4D0F-8A23-1923B44F7C0A@health.ucsd.edu> <87eekkcwzs.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <87eekkcwzs.fsf@localhost> User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Berry, Charles" , Gerardo Moro , emacs-orgmode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -0.51 X-TUID: cqiWmW4vHP8x * Ihor Radchenko [2020-11-23 11:14]: > > Org provides hyperlinks and that useful feature may be used as > > on-the-fly information visualizer for many groups of smaller pieces of > > information which could be obtained from some structure or found in > > real time. > > Also, one could quickly select one of multiple links under heading by > invoking C-c C-o with point at heading. I did not know that. That is useful feature for Org. Side note: there shall be feature in Org that quickly captures the full link to the heading. Maybe it already exists. Instead of constructing links by hand like entering the file name, entering the heading for the link, there shall by some automated feature: Useful Feature A: ================= - watching 2 windows with 2 Org files - position cursor in first Org file to accept the hyperlink - move to 2nd Org file any heading - press key, and hyperlink is sent to 1st Org file properly formatted for specific heading in second Org file. And then there shall be also collection of hyperlinks: Useful feature B to collect hyperlinks similar to above: ======================================================== - user browses one Org file and thinks of collecting various multiple hyperlinks as such need to be referenced in other Org file and I refer to headings only for now. - user would just invoke the key in any heading and message would be "Heading `** TODO Things' captured in the ring" - user would be able to browse various Org files and collect hyperlinks in memory collection. - After several collections user could then go to other Org files and invoke key or command to insert the whole collection of hyperlinks. Do you find that useful? Who does? That is how I am implementing information in the personal program HyperScope, it will get published when polished and ripe. Collections are similar to Dired marking, user can mark the file and later decide what to do with it. Org headings can be or could be marked with later action on the whole collection of headings: - re-filing all of them at once - sending them all by email to other person (I do with Org) - sending hyperlinks in other Org file (I do in HyperScope) - creating new Org file with the collection of headings - assigning properties to collection of headings, tasks, todo or similar. I am often assigning tasks to people, collection would help me re-assign tasks instead of doing it one by one. > In the following example, C-c C-o would raise a buffer listing all > the links. Then, the links can be selected by pressing 1/2/3 (to > open first/second/third link): That is new to me and fine feature, thank you for reference. But this here, this chunk of various properties shows how Org users wish Org to be way more structured, that Org wants to become more than just plain text, it wants to become database. *** NEXT Commit all the changes SCHEDULED: <2020-11-24 Tue .+1d> :PROPERTIES: :CREATED: [2019-04-18 Thu 09:40] :STYLE: habit :REPEAT_TO_STATE: NEXT :LOGGING: DONE(!) :ARCHIVE: %S_archive_%y.org::* Habits :ORG-TIME-BONUS: 0 :LAST_REPEAT: [2020-11-23 Mon 14:10] :SHOWFROMDATE: 2020-11-09 :RESET_CHECK_BOXES: t :END: