emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>, emacs-orgmode@gnu.org
Subject: Re: Buffer local alias?
Date: Wed, 15 Jan 2014 08:51:49 +0000	[thread overview]
Message-ID: <87r489tyoq.fsf@ucl.ac.uk> (raw)
In-Reply-To: <m1lhyigld9.fsf@poto.westell.com> (Thomas S. Dye's message of "Tue, 14 Jan 2014 14:05:38 -1000")

> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

[...]

>> I know that this problem is a problem of balancing backward
>> compatibility with new features, better design, etc and cannot be
>> solved.  And I see the win in (most of) the breaking changes.

I agree wholeheartedly with the sentiment expressed here.  Despite the
difficulties I have had resurrecting some LP org documents recently, the
benefits of the continual developments to org + babel are clear.

[...]

"Thomas S. Dye" <tsd@tsdye.com> writes:

> Perhaps one way to deal with this is to have the Org mode literate
> programming (reproducible research) file choose which version of
> Org-mode to use.  Something like the following?
>
>   #+name: org-mode-version
>   #+begin_src sh
>   cd path/to/org-mode-git-repo
>   git checkout rev
>   #+end_src
>
>   # Local Variables:
>   # eval: (and (fboundp 'org-sbe) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))
>   # eval: (sbe "org-mode-version")
>   # eval: (org-reload t)
>   # End:
>
> I haven't the faintest idea if this is a "good idea" or a snake pit of
> potential problems. Is the idea worth experimenting with?

Very much so.  One of my recent fights with org was due to finally
getting back reviewers' comments on a paper I had submitted almost a
year ago.  If I had had an automatic link to the correct version of org,
the one that matched my document, it would have made things much
easier.  Obviously, I could have done this manually and probably should
have.

However, I think it may be quite difficult to automate what you are
proposing...

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.4-322-gece429

  parent reply	other threads:[~2014-01-15  9:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 19:00 Buffer local alias? Thomas S. Dye
2014-01-14 19:39 ` Nick Dokos
2014-01-14 19:44   ` Bastien
2014-01-14 20:12     ` Thomas S. Dye
2014-01-14 21:49       ` Andreas Leha
2014-01-15  0:05         ` Thomas S. Dye
2014-01-15  8:41           ` Andreas Leha
2014-01-15  8:51           ` Eric S Fraga [this message]
2014-01-15  9:33         ` Sebastien Vauban
2014-01-15  9:50           ` Andreas Leha
2014-01-15 19:59         ` Achim Gratz
2014-01-15 20:40           ` Andreas Leha
2014-01-16 16:44             ` Achim Gratz
2014-01-16 16:54               ` Rick Frankel
2014-01-16 17:51               ` Thomas S. Dye
2014-01-15  9:30   ` Sebastien Vauban

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=87r489tyoq.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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).