> 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 (<bugs@gnu.support>) escribió:

> * 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 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 <!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:
>
>