emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Thomas Alexander Gerds <tagteam@sund.ku.dk>
Cc: emacs-orgmode@gnu.org, Jason Dunsmore <jasondunsmore@gmail.com>
Subject: Re: worg access source
Date: Thu, 09 Feb 2012 10:01:28 -1000	[thread overview]
Message-ID: <m1ty2z6ajr.fsf@tsdye.com> (raw)
In-Reply-To: <grb615wr7viy0w.fsf@sund.ku.dk> (Thomas Alexander Gerds's message of "Thu, 9 Feb 2012 20:53:35 +0100")

Thomas Alexander Gerds <tagteam@sund.ku.dk> writes:

> excellent. so, why not put a link to the org page in the footer of each
> worg page? there is already a canonical place:
> ,----
> | 
> | Documentation from the http://orgmode.org/worg/ website (either in its
> | HTML format or in its [[xxx.org.html][Org format]])
> `----
> cheers
> tomy
> Jason Dunsmore <jasondunsmore@gmail.com> writes:
>> On Thu, Feb 09 2012, Thomas Alexander Gerds wrote:
>>> in worg it would be great if (as in emacs muse) there was a link to
>> the
>>> underlying .org file which was used to generate the page. my naiive
>>> attempt to catch a glimpse of the source of
>>> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
>>> was to browse-url
>>> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.org
>> Almost.  The URL containing the formatted Org source is:
>> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.org.html

+1, if this isn't too much work.  It saves Worg authors having to
remember this detail, which the reader finds useful.


Thomas S. Dye

  reply	other threads:[~2012-02-09 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 10:09 worg access source Thomas Alexander Gerds
2012-02-09 10:14 ` suvayu ali
2012-02-09 19:30 ` Jason Dunsmore
2012-02-09 19:53   ` Thomas Alexander Gerds
2012-02-09 20:01     ` Thomas S. Dye [this message]
2012-02-27 23:46   ` Thomas S. Dye
2012-02-27 23:57     ` Thorsten
2012-02-28  2:15       ` Thomas S. Dye
2012-02-28 11:44     ` Bastien

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:

  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=m1ty2z6ajr.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jasondunsmore@gmail.com \
    --cc=tagteam@sund.ku.dk \


* 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


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).