emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Sven Bretfeld <sven.bretfeld@gmx.ch>
Cc: Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Using non-org files as agenda files?
Date: Wed, 23 Jan 2013 17:02:52 +1030	[thread overview]
Message-ID: <87y5fk8l9s.fsf@ucl.ac.uk> (raw)
In-Reply-To: <874ni8iyn5.fsf@gmx.ch> (Sven Bretfeld's message of "Wed, 23 Jan 2013 00:30:38 +0100")

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

Sven Bretfeld <sven.bretfeld@gmx.ch> writes:

> Dear all 
>
> Is it anyhow possible to use a .tex file as an org-agenda-file? 
>
> This might seem a silly question. The reason is that I stick to auctex
> for writing my documents. But it would be nice to be able to insert a
> todo item directly at an appropriate place within a tex-file and have it
> integrated in org-agenda-view. 

One approach could be to use babel.  That is, have an org file in which
all your latex sits as code segments.  You can then edit each individual
code segment (C-c ') using auctex but keep org as an outliner and task
manager.  You do lose some capabilities of auctex, specifically to do
with cross-referencing support, I would imagine.  But you gain all the
power of org and continue to be able to use auctex's keybindings when
desired.

I've attached a simple example.  Tangling the file (C-c C-v t) will
create l.tex which you can then process as desired.

> Maybe this can be done by a workaround using ipa.el (in-place
> annotations) and setting an orgmode file as ipa-file? Any experiences? 

Thanks for reminding me of this.  I had meant to try it out and forgot!
(forgot to create an org todo item... have done so now ;-)

HTH,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-837-ge37613

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: l.org --]
[-- Type: text/org, Size: 646 bytes --]

#+TITLE:     Testing tangling etc. for latex
#+AUTHOR:    Eric S Fraga
#+EMAIL:     e.fraga@ucl.ac.uk
#+DATE:      2013-01-23 Wed

#+PROPERTY: tangle yes
  
* Cover material
  #+begin_src latex
    \documentclass{scrartcl}
    \title{The document}
    \author{ESF}
    \begin{document}
    \maketitle
  #+end_src

* Introduction
  In the introduction, we talk about the problem and why it is important.

  #+begin_src latex
    \section{Introduction}
    \label{sec:intro}
    
    Yes, here I talk about the problem.
  #+end_src
* End matter
  #+begin_src latex
    % could put the bibliography here, for instance
    \end{document}
  #+end_src

  reply	other threads:[~2013-01-23  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 23:30 Using non-org files as agenda files? Sven Bretfeld
2013-01-23  6:32 ` Eric S Fraga [this message]
2013-01-23  7:00 ` Samuel Wales
2013-01-25 12:55   ` Sven Bretfeld

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=87y5fk8l9s.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=sven.bretfeld@gmx.ch \
    /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).