emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Editing comments or strings in Org mode
Date: Thu, 24 Jan 2013 23:54:53 -0700	[thread overview]
Message-ID: <CAJcAo8v4-avUfJd=kmvX35JVn+GHF6fgeGUgKCJJA3K8b3BMAw@mail.gmail.com> (raw)
In-Reply-To: <86fw1qjxvt.fsf@iro.umontreal.ca>

Hi Francois,

On 1/24/13, François Pinard <pinard@iro.umontreal.ca> wrote:
> I'm not sure I understand the use case

Your Org in elisp solution allows limited Org functionality in Elisp
and other files.  You cannot put those files in the agenda, or do many
other things that you can do with agenda files.  The entries are not
in an Org context.  They are in an external file.

What I am suggesting as a possible alternative in some cases, is to
have all of your notes about the elisp file in your ordinary Org
agenda files.  However, this is not Babel.

Instead, it is a bidirectional Org<->non-Org link.  A command in the
external file will find the nearest bidirectional link, then take you
to its dual entry in your Org files.  And a command in Org will take
you to the place in elisp that points to that entry.

So in elisp you will have:

;;; $[bidir da39a3ee5e6b4b0d3255bfef95601890afd80709]

And in your Org file you will have:

* my notes on that part of elisp
:PROPERTIES:
:ID: da39a3ee5e6b4b0d3255bfef95601890afd80709
:END:

Here are my notes.

===

This will allow you to use the full power of Org without tangling.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY
can get it.  There is no hope without action.

      reply	other threads:[~2013-01-25  6:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 20:46 François Pinard
2013-01-24 11:46 ` Bastien
2013-01-24 16:55 ` Samuel Wales
2013-01-24 17:26   ` François Pinard
2013-01-25  6:54     ` Samuel Wales [this message]

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='CAJcAo8v4-avUfJd=kmvX35JVn+GHF6fgeGUgKCJJA3K8b3BMAw@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    --subject='Re: Editing comments or strings in Org mode' \
    /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

Code repositories for project(s) associated with this 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).