emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Samuel Wales <samologist@gmail.com>
Cc: "ZHUO QL (KDr2)" <zhuoql@yahoo.com>,
	Eric S Fraga <esflists@gmail.com>,
	Emacs-org List <emacs-orgmode@gnu.org>
Subject: Re: Proposal: references from code to text.
Date: Wed, 16 May 2018 19:29:22 -0700	[thread overview]
Message-ID: <CAJ51ETpWhDyEM676zLgJwLEgD0no0iGcUQFSAZdrGF0TJUNzmQ@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8vTHOhhUZ=c-wGpsJOt7B5NH=bO4kf1OockX81A0UZkpg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]

You might want to check out linkd: https://www.emacswiki.org/emacs/linkd.el

It does a lot of what you describe independently of org-mode.

John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Wed, May 16, 2018 at 12:37 PM, Samuel Wales <samologist@gmail.com> wrote:

> i'm not sure if i understand the goal.  is it babel-only?
>
> this email might be off-topic.
>
> what i want is links, using something like org-id,
>
>   - from non-org [for example, a link in file.el in a comment]
>   - to non-org [for example, a named or id'ed location in the same file]
>   - or to org [e.g. an org-id'ed org entry, or a named or id'ed
> location in a babel block]
>
> that can be, if needed, effectively, bidirectional.  thus, you could
> document a function in file.el using a subtree in main.org and bounce
> between the function and the documentation because there is a link for
> each.
>
> non-org [e.g. file.el] can be an original file [i.e. no babel
> anywhere] or the result of tangling from babel.
>
> i find that org-link-minor-mode is /highly/ useful for the non-org
> part of this, but it doesn't support all of the above functionality
> automatically.
>
> i'd want a general package that is like org-link-minor-mode, but takes
> care of supporting the user by creating good ids and links as needed.
>
> --
> The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>
>
> The disease DOES progress. MANY people have died from it. And ANYBODY
> can get it at any time.
>

[-- Attachment #2: Type: text/html, Size: 2639 bytes --]

  reply	other threads:[~2018-05-17  2:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <800808596.465327.1526131788117.ref@mail.yahoo.com>
2018-05-12 13:29 ` Proposal: references from code to text ZHUO QL (KDr2)
2018-05-14  5:48   ` Eric S Fraga
2018-05-14 15:05     ` John Kitchin
2018-05-14 17:06       ` Eric S Fraga
2018-05-14 17:11       ` Eric S Fraga
2018-05-15  4:49       ` ZHUO QL (KDr2)
2018-05-15 10:04         ` Eric S Fraga
2018-05-16  7:04           ` ZHUO QL (KDr2)
2018-05-16 14:25             ` John Kitchin
2018-05-16 19:37               ` Samuel Wales
2018-05-17  2:29                 ` John Kitchin [this message]
2018-05-17  2:40                   ` Samuel Wales
2018-05-17  2:58               ` ZHUO QL (KDr2)
2018-05-17  3:10                 ` John Kitchin
2018-05-17  9:33                   ` ZHUO QL (KDr2)
2018-06-15 21:44                     ` John Kitchin
2018-06-15 18:07               ` Grant Rettke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ51ETpWhDyEM676zLgJwLEgD0no0iGcUQFSAZdrGF0TJUNzmQ@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=esflists@gmail.com \
    --cc=samologist@gmail.com \
    --cc=zhuoql@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).