From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id KCcEG/W1vF9+cgAA0tVLHw (envelope-from ) for ; Tue, 24 Nov 2020 07:27:49 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id +BPiFvW1vF+3HAAA1q6Kng (envelope-from ) for ; Tue, 24 Nov 2020 07:27:49 +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 97D54940111 for ; Tue, 24 Nov 2020 07:27:47 +0000 (UTC) Received: from localhost ([::1]:48336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1khSjq-00031c-Ah for larch@yhetil.org; Tue, 24 Nov 2020 02:27:46 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:43930) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1khShJ-0002DV-Mm for emacs-orgmode@gnu.org; Tue, 24 Nov 2020 02:25:09 -0500 Received: from mail-pg1-x530.google.com ([2607:f8b0:4864:20::530]:44487) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1khShH-00058D-IL for emacs-orgmode@gnu.org; Tue, 24 Nov 2020 02:25:09 -0500 Received: by mail-pg1-x530.google.com with SMTP id t3so2825943pgi.11 for ; Mon, 23 Nov 2020 23:25:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=lAAFMTomWgDP4Q4CWx/f4WPxLauR0oAGmPHeMeLSXs8=; b=Oy1t87vRY7y2C1ELePFRRpkNSBfln0DVOa+HXGz8vZXVNvWYUtyEtrUF0OR0NVXX9U v3RsNPxwPv9qiJ7bjnux8b0ryoB+5130KjHkYfNYukG736xkwdZ6X90Nmg50bj8Hn0E3 mkIGPAkL+6Eqw4LEsNJbPbxKyZcMOOol4FPM+HR4yM/A0SD+M0hyvxuTEnkZlFnAdV+V NIJDguO7bnArW4z7Edv31PcZGFMkmvlWlTnqud4tzDhhBDmkCx7E/9yyt34lF6ZYy2za XBuJRfaFWbimH9hoxMaLWH/CU/6ZPO3otpWAb3Dew81DKgXKI7hqhy1OuUO+O1uDvhST c5bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=lAAFMTomWgDP4Q4CWx/f4WPxLauR0oAGmPHeMeLSXs8=; b=A3zLUGRNB7lfWp6B2R856odNPJXYGT/K1PzI5wIz2H0pFgrbnLjqbUPSM08j5bySgd mnMI05jnUaSLbLLKnjx7LrPAZbWEIbBagrzjHSx9G3r0tHUv7QMd0tYZcrsusVpnYLGQ jZHdbsvkNs984jr8syBfe4tAS288vS9DnHZjmbB3BWmfvzgtJ+1rg2uZbBfTUI3kaFUQ tOC3C3GMNXx8KS1W0ijet2Z/p5NOk/KmRfP3gfZ8C22LPJdVjZlIOpG9V5V9EAzc8jwL v+Yq3d9pqAd2ArTFWjtJtVCaPbc+2T7DsHWL0rRpHZ8vbthY5rgt/Tk2VZEVWrMm+OPO txDQ== X-Gm-Message-State: AOAM533WuIt1n4wLwzDNpfBN6k6R9OB+D8z9sJpXXQ7uSObh1K/jGKip HwO6pxQWnrsG751hs9+ZUrs= X-Google-Smtp-Source: ABdhPJwdUkz42hqZjYRM4V0Hlfh2s2Yzpk3/PJsYDfDvsxM/LCYASBiDrG0YDa7PxhegjgYp/vNmWw== X-Received: by 2002:a17:90a:e2cd:: with SMTP id fr13mr3334814pjb.97.1606202705512; Mon, 23 Nov 2020 23:25:05 -0800 (PST) Received: from localhost ([111.20.225.136]) by smtp.gmail.com with ESMTPSA id i16sm13773301pfr.183.2020.11.23.23.25.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 Nov 2020 23:25:04 -0800 (PST) From: Ihor Radchenko To: Jean Louis Subject: Re: Bring up a screen giving option to open a series of orgmode files In-Reply-To: References: <169441F9-83D6-4D0F-8A23-1923B44F7C0A@health.ucsd.edu> <87eekkcwzs.fsf@localhost> Date: Tue, 24 Nov 2020 15:23:51 +0800 Message-ID: <874klfcj5k.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::530; envelope-from=yantar92@gmail.com; helo=mail-pg1-x530.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=fail (headers rsa verify failed) header.d=gmail.com header.s=20161025 header.b=Oy1t87vR; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=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.59 X-TUID: MRWQqFCctJPh > 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: See org-store-link and org-insert-link. org-store-link stores link in a link ring and the link/links can be later inserted using org-insert-link. > Org headings can be or could be marked with later action on > the whole collection of headings: See bulk commands in agenda (Bulk remote editing selected entries): https://orgmode.org/manual/Agenda-Commands.html Manually picking headlines to put into agenda is not currently possible in org-mode, but one can volunteer to do it. It is not too hard to implement. Patches are welcome. > - re-filing all of them at once built-in > - 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 not implemented, but see org-agenda-bulk-custom-functions for extending the built-in functionality > - 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. build-in bulk commands provide a way to assign todo keywords or tags. > 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. As usual, it's user's choice how to use Org. There are built-in tools that require storing metadata and org-mode devs chose to store everything as plain text. If user does not want to use this feature, the user is free to not use it or use alternative ways to store metadata (as it is done in org-roam, for example). Best, Ihor Jean Louis writes: > * 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: