emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Multi-file and master files
Date: Wed, 01 Oct 2014 14:01:07 +0100	[thread overview]
Message-ID: <87h9zodjvw.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <877g0kx9fi.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 1 Oct 2014 14:26:41 +0200")


Hmmm. I seem to have trashed by org install by loading from ELPA;
currently, interactively, I can't export at all.


debugger entered--Lisp error: (invalid-function org-with-silent-modifications)
  org-with-silent-modifications(nil)
  org-refresh-category-properties()
  org-get-category()

It's still working through by batch process which is using cask and
probably has a different version of org.

Is there a stable org-mode package repo? At the moment, both ELPA and
the org-mode repo appear to be bleeding egde...

Phil


Rasmus <rasmus@gmx.us> writes:

> phillip.lord@newcastle.ac.uk (Phillip Lord) writes:
>
>> Rasmus <rasmus@gmx.us> writes:
>>
>>> Hi Phillip,
>>>
>>> phillip.lord@newcastle.ac.uk (Phillip Lord) writes:
>>>
>>> I might be misunderstanding your question here, so bear(?) with me.
>>>
>>> I think #+INCLUDE: "$FILE" should take care of what you want.
>>> Basically, at export time, INCLUDE is expanded to the content of $FILE
>>> in the buffer.  Footnotes should work.
>>
>> So
>>
>> master.org
>>   include  file1.org
>>   include  file2.org
>>
>> Now, in file1.org add a footnote gets --
>>
>>  [fn:1]
>>
>>
>> * Footnote
>>
>> [fn:1] Footnote one
>>
>>
>> In file2.org add a footnote gets
>>
>>  [fn:1]
>>
>> * Foonote
>>  [fn:1] Footnote two
>>
>> And footnote two gets lost.
>
>
> Here's a complete example that works as expected (footnotes and
> hyperlinks).  Perhaps one needs to specify :minlevel to get the
> desired output.  I don't know if this is desired behavior.  If not you
> can make another bug report.
>
>
>>$ for f in $(ls -A /tmp/include); do echo ""; echo "→ $f ←"; echo
>> "~~~~~~~~~~~~~~~"; echo ""; cat /tmp/include/$f; done
>
>
> → c1.org ←
> ~~~~~~~~~~~~~~~
>
> * chapter 1
> txt1[fn:1]
>
> * Footnotes
>
> [fn:1] fn1
>
>
> → c2.org ←
> ~~~~~~~~~~~~~~~
>
> * chapter 2
> txt2[fn:1]
>
> * Footnotes
>
> [fn:1] fn2 
>
>
>
> → m.org ←
> ~~~~~~~~~~~~~~~
>
>
> #+OPTIONS: toc:nil
> #+TITLE: Overall title
>
> #+INCLUDE: "/tmp/include/c1.org" :minlevel 1 
> #+INCLUDE: "/tmp/include/c2.org" :minlevel 1
>
> * chapter 3
>   Everything was said in [[*chapter 1]] and [[*chapter 2]]...
>
> → m.txt ←
> ~~~~~~~~~~~~~~~
>
> 			    ━━━━━━━━━━━━━━━
> 			     OVERALL TITLE
> 			    ━━━━━━━━━━━━━━━
>
>
> 1 chapter 1
> ═══════════
>
>   txt1[1]
>
>
> 2 chapter 2
> ═══════════
>
>   txt2[2]
>
>
> 3 chapter 3
> ═══════════
>
>   Everything was said in 1 and 2…
>
>
>
> Footnotes
> ─────────
>
> [1] fn1
>
> [2] fn2
>
>
>
>> I have a similar problem with hyperlinks. The normal store link
>> remembers the input.org file that the link is too. So, if in the
>> example, above I like between file2.org and file1.org using the Store
>> Link menu item, the HTML is wrong (since there is no file2.html
>> generated).
>
> I was not able to reproduce.  But please make a receipt to get this
> behavior and it can be looked into.
>
> —Rasmus

-- 
Phillip Lord,                           Phone: +44 (0) 191 222 7827
Lecturer in Bioinformatics,             Email: phillip.lord@newcastle.ac.uk
School of Computing Science,            http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower,               skype: russet_apples
Newcastle University,                   twitter: phillord
NE1 7RU                                 

  reply	other threads:[~2014-10-01 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  8:54 Multi-file and master files Phillip Lord
2014-10-01  9:03 ` Rasmus
2014-10-01 11:57   ` Phillip Lord
2014-10-01 12:26     ` Rasmus
2014-10-01 13:01       ` Phillip Lord [this message]
2014-10-01 13:27         ` Rasmus
2014-10-01 14:40           ` Phillip Lord
2014-10-01 14:56             ` Nicolas Goaziou
2014-10-01 15:44               ` Phillip Lord

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=87h9zodjvw.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).