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 MPf3KiyHvF9ieAAA0tVLHw (envelope-from ) for ; Tue, 24 Nov 2020 04:08:12 +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 4HubJiyHvF9MEgAA1q6Kng (envelope-from ) for ; Tue, 24 Nov 2020 04:08:12 +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 CB72C9402C8 for ; Tue, 24 Nov 2020 04:08:11 +0000 (UTC) Received: from localhost ([::1]:34700 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1khPcf-0001KX-Lf for larch@yhetil.org; Mon, 23 Nov 2020 23:08:09 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57130) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1khPbt-0001IH-NZ for emacs-orgmode@gnu.org; Mon, 23 Nov 2020 23:07:21 -0500 Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]:36643) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1khPbr-0002NV-Ey for emacs-orgmode@gnu.org; Mon, 23 Nov 2020 23:07:21 -0500 Received: by mail-lf1-x135.google.com with SMTP id v14so4759483lfo.3 for ; Mon, 23 Nov 2020 20:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ru7AnOQ6L0hrULS8apGLws7GFr3p1ScJN1caobrvOjg=; b=GlMPVshVFisw/+UwvNH6RVh/hBtZylOInFZrPWWI0AdNitDW7GZkR/ORkPg68ONNZD gzq1DedoBhdzgkSBDoP3fmAfY4PQy2gxhofXpfzp+tVOVzlxzZJEC8N5QZgVyKuHqfRM CwMwo3NNDJ1VFqlq2Gr7aky7x/GB66NHRC8mLEdXGcFGU/QTYF0KdAmiU2IyWGPyRRgZ ft3B7RZpMS/5l7kwVwcRrz/Y+F08Cvac5Cdnr5lwc+YaUc7/VUM/YyyxCJzPbOeWYa1N M64YJxJPq0ssKGOSWRZl7Pab66ZrGhyQWSdiaWdn++D2VIOM+8L+SY58GsLgVRjxagCj eblQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ru7AnOQ6L0hrULS8apGLws7GFr3p1ScJN1caobrvOjg=; b=aIPTPAkIbkiRb5M7HBnS/GJb67uMiLCVgzSoeRPtqZ6zo+hEHzI0VO+JIGakY8eI/Q 206JjXxY0g9mdLOn4hupVMSoplCoBDwGKXUfci9B+ILngonyeZOkKlih86DEvYOlF2Wm ctYYw+UC6XH8AnD4o9uBNLMP3gWe2gwtBL0QCg8Tps9gw/sewerjL09xqqwj3X3N1D+B cDEcXrMGGvQXKtVHUCLSYjVnwuD1NY+UXzWan5u+YGzKScVYdZ2hoy+FOJzkUPo/QCi+ Q39OAlEfLqyhW0YJse6BUSF/5rSxLMDApHai3I6c0yTDEWJDxNjuJ1hLMQYFsyIn+Ckw Bkww== X-Gm-Message-State: AOAM530XrSrQ2ErRsz/LL6DcQ0u7ZzIIegRLzb/yFc0fsI31Eg1Bfljf L8UVM4T5kEo/2Mhrt0bAbr4pZIpvjpQjcEB5UFeSNACfANuj4g== X-Google-Smtp-Source: ABdhPJxbYYkY35ACjm3o+ncVL4FaIsTJcHe6xFOdUMo9TTYajyYr71i8k6WQRDwwOjiYWjCxsfbWUdMsR8QmA5qWjds= X-Received: by 2002:ac2:490d:: with SMTP id n13mr1048218lfi.108.1606190837391; Mon, 23 Nov 2020 20:07:17 -0800 (PST) MIME-Version: 1.0 References: <169441F9-83D6-4D0F-8A23-1923B44F7C0A@health.ucsd.edu> <87eekkcwzs.fsf@localhost> In-Reply-To: From: Gerardo Moro Date: Tue, 24 Nov 2020 06:07:05 +0200 Message-ID: Subject: Re: Bring up a screen giving option to open a series of orgmode files To: Jean Louis Content-Type: multipart/alternative; boundary="0000000000004de6a005b4d272e1" Received-SPF: pass client-ip=2a00:1450:4864:20::135; envelope-from=gerardomoro37@gmail.com; helo=mail-lf1-x135.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, HTML_MESSAGE=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" , emacs-orgmode , Ihor Radchenko 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=GlMPVshV; 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.09 X-TUID: Q0UmlOiwQLBY --0000000000004de6a005b4d272e1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > Do you find that useful? Who does? I definitely think it's very, very useful! I constantly leave tabs open or use bookmarks, but it'd be great to add them to ORG with a timestamp to watch later. This way I wouldn't forget about them and they wouldn't take memory on the browser if I don't bookmark them. El lun, 23 nov 2020 a las 12:59, Jean Louis () escribi=C3= =B3: > * 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 o= f > > > 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: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > - 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: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > > - 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: > > --0000000000004de6a005b4d272e1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=C2=A0> Do you find that useful? Who does?
I defini= tely think it's very, very useful!
I constantly leave tabs op= en or use bookmarks, but it'd be great to add them to ORG with a timest= amp to watch later.
This way I wouldn't forget about them and= they wouldn't take memory on the browser if I don't bookmark them.=


El lun, 23 nov 2020 a las 12:59, Jean Louis (<bugs@= gnu.support>) escribi=C3=B3:
* Ihor Radchenko <yantar92@gmail.com> [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 piec= es 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<= br> > 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:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- 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
=C2=A0 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:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

- 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
=C2=A0 would be "Heading `** TODO Things' captured in the ring&quo= t;

- user would be able to browse various Org files and collect
=C2=A0 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 <!point!> 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:

--0000000000004de6a005b4d272e1--